Generate Skill Card
Skill directory to analyze: $ARGUMENTS
Purpose
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:
- A skill directory already exists and needs a new governance card.
- A changed skill needs its existing card refreshed.
- A skill owner is preparing legal/safety review material.
Do NOT use for:
- Explaining, listing, comparing, or discussing skills or skill capabilities.
- Creating or rewriting the source skill itself.
- Generating cards for non-skill assets such as models, datasets, containers, or full systems.
- Signing, publishing, or approving a skill card.
- Replacing required human legal, safety, or owner review.
Prerequisites
- Python 3 is available.
jinja2 is installed before running render_card.py.- The target path is a skill directory containing
SKILL.md or skill.md.
- The agent can write a temporary context JSON file and the rendered card output.
- Runtime permissions allow reads from
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.
Instructions
- First, read this
SKILL.md completely before running any script.
- Resolve the target skill directory from
$ARGUMENTS; if omitted, use the current working directory.
- Stay within the declared permission scope. Do not read
.env, credential files, hidden auth folders, or unrelated repo files; do not write outside the target skill directory or /tmp/.
- Run
scripts/discover_assets.py against the target. Use the structured signal summary first; if output is truncated, read only targeted files or small excerpts.
- Build a context JSON file from the structured signal summary first, then from extracted file contents only when needed.
- Populate
credential_requirements with only two fields: requires_api_key_or_credential and credential_types. Ground the classification in SKILL.md prose documentation — not script inspection alone. For credential_types, use the controlled vocabulary in references/style-guide.md. Never include credential values, assignments, or raw environment variable names.
- Follow
references/style-guide.md for every context field. Use HUMAN-REQUIRED only when no source supports a truthful value.
- Render the card with
scripts/render_card.py and fix any schema errors before proceeding.
- Review the card manually, remove resolved VERIFY and SELECT markers, then run
scripts/validate_submission.py.
- Before finishing, confirm the rendered card has no unrendered
{{ ... }} or {% ... %} template fragments.
Available Scripts
| 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> |
Examples
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"])
Limitations
- The generated card is a draft and must be reviewed by a human owner.
- Discovery is limited to local files and repo metadata visible from the target path.
- The renderer validates required context shape, not the legal or safety correctness of field values.
- Canned limitation and risk catalogs are starting points; remove entries that do not apply.
Troubleshooting
| 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. |
Files in this skill
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 validator
1---2name: skill-card-generator-23description: 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.4license: CC-BY-4.0 AND Apache-2.05---67# Generate Skill Card89**Skill directory to analyze**: $ARGUMENTS1011## Purpose1213Create 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.1415Use this when:16- A skill directory already exists and needs a new governance card.17- A changed skill needs its existing card refreshed.18- A skill owner is preparing legal/safety review material.1920Do NOT use for:21- Explaining, listing, comparing, or discussing skills or skill capabilities.22- Creating or rewriting the source skill itself.23- Generating cards for non-skill assets such as models, datasets, containers, or full systems.24- Signing, publishing, or approving a skill card.25- Replacing required human legal, safety, or owner review.2627## Prerequisites2829- Python 3 is available.30- `jinja2` is installed before running `render_card.py`.31- The target path is a skill directory containing `SKILL.md` or `skill.md`.32- The agent can write a temporary context JSON file and the rendered card output.33- Runtime permissions allow reads from `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.3435## Instructions36371. First, read this `SKILL.md` completely before running any script.382. Resolve the target skill directory from `$ARGUMENTS`; if omitted, use the current working directory.393. Stay within the declared permission scope. Do not read `.env`, credential files, hidden auth folders, or unrelated repo files; do not write outside the target skill directory or `/tmp/`.404. Run `scripts/discover_assets.py` against the target. Use the structured signal summary first; if output is truncated, read only targeted files or small excerpts.415. Build a context JSON file from the structured signal summary first, then from extracted file contents only when needed.426. Populate `credential_requirements` with only two fields: `requires_api_key_or_credential` and `credential_types`. Ground the classification in SKILL.md prose documentation — not script inspection alone. For `credential_types`, use the controlled vocabulary in `references/style-guide.md`. Never include credential values, assignments, or raw environment variable names.437. Follow `references/style-guide.md` for every context field. Use `HUMAN-REQUIRED` only when no source supports a truthful value.448. Render the card with `scripts/render_card.py` and fix any schema errors before proceeding.459. Review the card manually, remove resolved VERIFY and SELECT markers, then run `scripts/validate_submission.py`.4610. Before finishing, confirm the rendered card has no unrendered `{{ ... }}` or `{% ... %}` template fragments.4748## Available Scripts4950| Script | Purpose | Arguments |51| --- | --- | --- |52| `scripts/discover_assets.py` | Extracts skill files, repo signals, style guide, and template into one discovery report. | `<skill_directory>` |53| `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>` |54| `scripts/validate_submission.py` | Fails if the rendered card still contains VERIFY or SELECT review markers. | `<rendered-card.md>` |5556## Examples5758Discover signals for a target skill:5960```text61run_script("scripts/discover_assets.py", args=["/path/to/target-skill"])62```6364Render a card from the completed context:6566```text67run_script(68 "scripts/render_card.py",69 args=[70 "--context", "/tmp/target-skill-context.json",71 "--template", "references/skill-card.md.j2",72 "--out", "/path/to/target-skill/target-skill-card.md"73 ]74)75```7677Validate the reviewed card before submission:7879```text80run_script("scripts/validate_submission.py", args=["/path/to/target-skill/target-skill-card.md"])81```8283## Limitations8485- The generated card is a draft and must be reviewed by a human owner.86- Discovery is limited to local files and repo metadata visible from the target path.87- The renderer validates required context shape, not the legal or safety correctness of field values.88- Canned limitation and risk catalogs are starting points; remove entries that do not apply.8990## Troubleshooting9192| Error | Cause | Solution |93| --- | --- | --- |94| `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. |95| `jinja2 not installed` | The renderer dependency is missing. | Install `jinja2`, then re-run `render_card.py`. |96| `Context validation failed` | Required fields are missing or typed incorrectly. | Fix the context JSON using `references/style-guide.md`. |97| Unresolved marker failure | VERIFY or SELECT markers remain after review. | Confirm each marked field, prune catalog entries, then re-run `validate_submission.py`. |9899## Files in this skill100101- `SKILL.md` - this file (orchestration)102- `references/style-guide.md` - per-context-field guidance103- `references/skill-card.md.j2` - exact card layout104- `references/Skill Card Generator License.txt` - license text for this skill package105- `references/catalog/limitations.json` - canned technical-limitations catalog106- `references/catalog/risks.json` - canned risk-management catalog107- `scripts/discover_assets.py` - discovery and signal extraction108- `scripts/render_card.py` - Jinja renderer with context validation109- `scripts/validate_submission.py` - pre-submission marker validator
NVIDIA