Agent skill / nvidia
Use only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities.
Core file
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-card-generatorExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills install nvidia/skills/skill-card-generatorFetches skill-card-generator from nvidia/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate skill-card-generator. Access via /skill-card-generatorin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Copy the command for your terminal
Package manager
npx skills install nvidia/skills/skill-card-generatorWorks with
| name | "skill-card-generator" |
| description | "Use only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities." |
| license | CC-BY-4.0 AND Apache-2.0 |
| compatibility | "Any agent that can run Python scripts and write files" |
| metadata | author: "Trustworthy AI Projects <trustworthyaiprojects@nvidia.com>" tags: - skill-card - governance - documentation - trustworthy-ai domain: documentation |
| permissions | file_read: - "target_skill_directory" - "references/" - "scripts/" file_write: - "target_skill_directory" - "/tmp/" shell: allowed_scripts: - "scripts/discover_assets.py" - "scripts/render_card.py" - "scripts/validate_submission.py" |
Skill directory to analyze: $ARGUMENTS
Create a draft NVIDIA governance skill card for an existing agent skill. The skill gathers source signals, guides the agent to build a grounded JSON context, renders a deterministic markdown card, and checks that human-review markers were removed before submission.
Use this when:
Do NOT use for:
jinja2 is installed before running render_card.py.SKILL.md or skill.md.target_skill_directory plus this skill's references/ and scripts/, writes only to the target skill directory or /tmp/, and shell execution only for the three scripts listed below.SKILL.md completely before running any script.$ARGUMENTS; if omitted, use the current working directory..env, credential files, hidden auth folders, or unrelated repo files; do not write outside the target skill directory or /tmp/.scripts/discover_assets.py against the target. Use the structured signal summary first; if output is truncated, read only targeted files or small excerpts.references/style-guide.md for every context field. Use HUMAN-REQUIRED only when no source supports a truthful value.scripts/render_card.py and fix any schema errors before proceeding.scripts/validate_submission.py.{{ ... }} or {% ... %} template fragments.| Script | Purpose | Arguments |
|---|---|---|
scripts/discover_assets.py | Extracts skill files, repo signals, style guide, and template into one discovery report. | <skill_directory> |
scripts/render_card.py | Validates context JSON and renders the skill card from the Jinja template. | --context <context.json> --template <skill-card.md.j2> --out <output.md> |
scripts/validate_submission.py | Fails if the rendered card still contains VERIFY or SELECT review markers. | <rendered-card.md> |
Discover signals for a target skill:
run_script("scripts/discover_assets.py", args=["/path/to/target-skill"])
Render a card from the completed context:
run_script(
"scripts/render_card.py",
args=[
"--context", "/tmp/target-skill-context.json",
"--template", "references/skill-card.md.j2",
"--out", "/path/to/target-skill/target-skill-card.md"
]
)
Validate the reviewed card before submission:
run_script("scripts/validate_submission.py", args=["/path/to/target-skill/target-skill-card.md"])
| Error | Cause | Solution |
|---|---|---|
directory not found | The target path is wrong or not mounted in the workspace. | Re-run discovery with the absolute path to the skill directory. |
jinja2 not installed | The renderer dependency is missing. | Install jinja2, then re-run render_card.py. |
Context validation failed | Required fields are missing or typed incorrectly. | Fix the context JSON using references/style-guide.md. |
| Unresolved marker failure | VERIFY or SELECT markers remain after review. | Confirm each marked field, prune catalog entries, then re-run validate_submission.py. |
SKILL.md - this file (orchestration)references/style-guide.md - per-context-field guidancereferences/skill-card.md.j2 - exact card layoutreferences/Skill Card Generator License.txt - license text for this skill packagereferences/catalog/limitations.json - canned technical-limitations catalogreferences/catalog/risks.json - canned risk-management catalogscripts/discover_assets.py - discovery and signal extractionscripts/render_card.py - Jinja renderer with context validationscripts/validate_submission.py - pre-submission marker validatorPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
nvidia/skills
skill-card-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: skill-card-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
skill-card-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
skill-card-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend skill-card-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added skill-card-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in skill-card-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
skill-card-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: skill-card-generator is focused, and the summary matches what you get after install.
We added skill-card-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 34