skill-creator

Create SKILL.md files with correct YAML frontmatter and portable structure.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/SilvrDuck/skills --skill skill-creator-silvrduck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/SilvrDuck/skills/tree/main/skills/skill-creator
Command: npx skills add https://github.com/SilvrDuck/skills --skill skill-creator-silvrduck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The skill-creator skill helps you author or revise Agent Skills so they work reliably across multiple Agent Skill runtimes by producing correct YAML frontmatter, portable descriptions, and standards-compliant body structure.

Core Features & Use Cases

  • Portable skill scaffolding: Creates a minimally valid SKILL.md template with required frontmatter and a TODO body for you to fill in.
  • Cross-tool compatibility guidance: Enforces constraints like name matching the directory, portable field usage, and safe Claude Code-only enhancements that degrade gracefully.
  • Quality and validation workflow: Guides you to write a description that will actually trigger activation and to run the repo validator to catch structural mistakes early.
  • Editing support: Provides rules for extending existing skills without breaking portability or bloating the body.

Quick Start

Use the skill-creator scripts to scaffold your new skill by running ./skills/skill-creator/scripts/new-skill my-new-skill, then edit the generated SKILL.md frontmatter description and validate with ./scripts/validate-skills.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a portable Agent Skill with correct YAML frontmatter?

To scaffold a portable Agent Skill, run the new-skill script to generate a minimally valid SKILL.md template with required YAML frontmatter and a TODO body. You then edit the description fields and validate the structure to ensure cross-tool portability.

What makes an Agent Skill description trigger reliably across different runtimes?

An Agent Skill description triggers reliably when it uses natural-language activation triggers and satisfies required name and description constraints. Writing descriptions that match user intents ensures the skill activates correctly across spec-compliant runtimes.

Does my skill name need to match the directory when creating a SKILL.md file?

Yes, your skill name must match the directory name when creating a SKILL.md file. This constraint is enforced during skill validation to maintain standards compliance and ensure cross-tool portability across different runtimes.

How do I validate structural invariants after editing Agent Skill frontmatter?

You validate structural invariants by running the validate-skills script after editing Agent Skill frontmatter. This checks for required fields, directory-name matching, and portable description usage to catch structural mistakes before deployment.

Can I extend an existing SKILL.md body without breaking cross-tool portability?

You can extend an existing SKILL.md body without breaking cross-tool portability by following editing rules that prevent body bloat and maintain standards-compliant structure. The skill-creator provides specific guidance for safe revisions.