// Scaffold new Agent Skills with best-practice structure and frontmatter. Use when the user wants to create a new skill, bootstrap a skill directory, or generate SKILL.md boilerplate following the Agent Skills spec.
Maintain project health by enforcing PR checklists, tracking open issues, verifying release readiness, and ensuring framework phases are up to date. Use when reviewing PRs, creating issues, preparing releases, or auditing project state.
Validate CSV and JSON data files against schemas and quality rules. Use when the user asks to check data quality, validate a dataset, or verify file contents match an expected schema.
Audit project dependencies for known vulnerabilities, outdated packages, and license compliance issues. Use when the user asks to check dependencies, audit packages, review licenses, or assess supply chain security.
Generate friendly greeting messages in multiple languages. Use when the user asks for a hello message, welcome text, or localized greeting.
Maintain project release notes, changelogs, and framework phase updates. Use when the user asks to generate a changelog, draft release notes, update CHANGELOG.md, or track framework phase transitions.
Generate test file stubs and boilerplate from source code analysis. Use when the user asks to create tests, add test coverage, or scaffold test files for existing source code.
| name | skill-template |
| description | Scaffold new Agent Skills with best-practice structure and frontmatter. Use when the user wants to create a new skill, bootstrap a skill directory, or generate SKILL.md boilerplate following the Agent Skills spec. |
| license | MIT |
| compatibility | Node.js 22+ |
| metadata | {"author":"skillscraft","version":"1.0","category":"tooling"} |
| allowed-tools | Bash Read Write |
Activate when the user wants to:
node scripts/scaffold.js --name <skill-name> --desc "<description>" [--dirs scripts,references,assets,tests]
If the user is unsure what they need, ask these questions in order:
description fieldscripts/ with a starter scriptreferences/ with a templateassets/tests/scenarios.jsonallowed-toolscompatibilityAfter scaffolding, always validate:
skill validate <output-dir>/SKILL.md
skill lint <output-dir>/SKILL.md
Fix any issues before the user starts editing.
Skill names must:
^[a-z0-9]([a-z0-9-]*[a-z0-9])?$Valid: code-review, test-gen, my-skill-v2
Invalid: Code-Review, -bad-start, has_underscores, UPPERCASE
<skill-name>/
SKILL.md # Always created
scripts/ # If --dirs includes scripts
run.sh # Starter bash script
references/ # If --dirs includes references
GUIDE.md # Template reference doc
assets/ # If --dirs includes assets
.gitkeep # Placeholder
tests/ # If --dirs includes tests
scenarios.json # Empty test scenarios array
allowed-tools field accepts space-separated tool names (e.g., Bash Read Write)