Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/nvidia/elements/troubleshootingnpx skills add NVIDIA/elements --skill troubleshootinggit clone --depth 1 https://github.com/NVIDIA/elementsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00106 | $0.00614 |
| Opus 5 | $0.00053 | $0.00307 |
| Sonnet 5 | $0.00021 | $0.00123 |
| Haiku 4.5 | $0.00011 | $0.00061 |
Grade A, and why
troubleshooting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting
You MUST review the troubleshooting guideline when diagnosing test failures, build errors, or performance issues.
When to Use This Skill
- Debugging unit test failures or timing issues
- Investigating visual regression test differences
- Troubleshooting Lighthouse performance scores
- Resolving build failures or Wireit cache issues
- Fixing Git LFS problems with visual baselines
- Diagnosing CI/CD pipeline failures
- Resolving development environment setup issues
- Investigating performance regressions in tests or builds
Must Read File
Read the troubleshooting guide to get critical context for troubleshooting guidance.
Diagnostic Triage Workflow
-
Identify the symptom category:
- Test failure:unit, axe, visual, SSR, or lighthouse?
- Build failure:Wireit cache, dependency resolution, TypeScript, or circular imports?
- Environment issue:Node version, pnpm version, Git LFS, or port conflict?
- Performance regression:slow tests, slow builds, or large bundles?
-
Run the relevant diagnostic commands:
- Test failures:
pnpm run test -- src/<component>/<component>.test.ts(isolate the failing test) - Build failures:
pnpm run ci:resetthenpnpm run build(clear caches first) - Environment:
node --version && pnpm --version && git lfs env(verify toolchain)
- Test failures:
-
Check the matching section in the troubleshooting guide for the specific symptom/solution pair.
-
If the issue persists, compare against a working reference component (badge, button, or card) to spot structural differences.
Additional References
- Troubleshooting Guide - Common issues and solutions
- Testing Guidelines - Test patterns
- Unit Testing - Unit test details
- Visual Testing - Visual regression details
- Lighthouse Testing - Performance testing
- Build System - Wireit troubleshooting
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 52 lines · 106 tokens per session scan A 0f38c7312e1f
troubleshooting is a skill published in the GitHub repository NVIDIA/elements (83 stars, last pushed 2d ago), licensed Apache-2.0. It adds 106 tokens to every session and 614 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
design-doc-interviewer
Interview the user to turn a proposed product/engineering change into a structured design document. Use when the user asks to be interviewed, wants help clarifying a design, or wants a design doc produced from Q&A. Emphasize numbered questions (few at a time), capture requirements/constraints/UX/data/logic/testing…
ideate
Capture and document a new idea in this repo. Use when the user says things like "help me brainstorm", "I have an idea", or "let's capture this for the future" and wants it recorded in design/ideas/ with a summary, supporting research (repo context + web if useful), and a sketch.
beui
Pick and install beUI (@beui) animated React components from the shadcn registry. Use when building motion UI, agent/chat interfaces, toasts, docks, bottom sheets, drawers, popovers, sliders, loaders, 404 pages, or any beui.dev component. Maps user intent to exact @beui install slugs instead of inventing custom…
beui-pro
Choose, inspect, install, and compose licensed beUI Pro premium React blocks from the authenticated shadcn registry. Use when building or improving landing pages with beUI Pro, installing @beui-pro items, selecting premium heroes, features, pricing, social proof, CTAs, navigation, footers, or other page sections, or…
ui-development
Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs foundry ui pages create or foundry ui run, or needs help with Vite…
vue-application-structure
Establishes or reviews the directory layout, component conventions, composable design, Pinia store structure, and Vue Router configuration for a Vue 3 TypeScript application. Invoked when the user asks to structure a Vue app, set up the project layout, or review Vue architecture.