create-skill
by dotnetcreate-skill is a scaffold generator for new agent skills in the dotnet/skills style. Use it to create a valid skill folder, generate SKILL.md with frontmatter, and follow repository conventions for Skill Scaffolding. It is best for new skills, not editing existing ones.
This skill scores 68/100, which means it is listable and useful for directory users, but not a fully polished, high-confidence install. The repository provides a real scaffold workflow for creating new agent skills, so users can understand when to use it and what it will do, though they should expect some missing adoption aids and a few gaps in executable guidance.
- Clear triggerability for creating new skills, generating SKILL.md files, and setting up skill directory structure.
- Substantive workflow content with explicit inputs, validation rules, and step-by-step scaffold instructions.
- Good install-decision value: frontmatter is valid, the body is substantial, and there are no placeholder markers or experimental signals.
- No install command or support files, so users must manually interpret and apply the scaffold workflow.
- The excerpt shows useful structure, but some guidance is truncated and there is little evidence of examples or validation tooling beyond the written instructions.
Overview of create-skill skill
What create-skill does
create-skill is a scaffold generator for new agent skills in the dotnet/skills style. It helps you create a valid skill folder, write SKILL.md with frontmatter, and follow the expected structure for Skill Scaffolding.
Who it is best for
Use the create-skill skill when you are starting a new skill from scratch, need a clean SKILL.md template, or want a repeatable way to set up a new skill directory instead of hand-assembling files.
What makes it useful
The main value is reducing setup mistakes: naming issues, missing frontmatter, and inconsistent folder layout. It is more useful than a generic prompt when you want the output to conform to repository conventions and agent skill expectations.
When it is not a fit
Do not use create-skill for editing an existing skill in place or for building a custom agent outside the .agents/skills pattern. In those cases, direct editing is faster and less likely to introduce unnecessary scaffolding.
How to Use create-skill skill
Install create-skill
Install the create-skill skill in your skills environment with:
npx skills add dotnet/skills --skill create-skill
If your setup uses a different skills manager, keep the same target concept: add the create-skill skill before asking it to scaffold a new skill.
Give it the right input
The create-skill skill works best when you provide the four inputs it expects: skill name, description, purpose, and workflow steps. Strong input looks like this:
- name:
ci-triage - description: “Triage failing CI jobs and suggest the most likely fix.”
- purpose: one paragraph on the desired outcome
- workflow: numbered steps, not a vague goal
Weak input like “make a skill for debugging” forces the skill to guess the scope, output structure, and wording.
Start with the source files
Read SKILL.md first, then inspect any linked repository conventions that affect your output. In this repository, the practical starting point is the skill file itself, because it contains the actual rules for create-skill usage, validation, and layout.
Use a prompt that asks for scaffolding
A good create-skill guide prompt should say what you want created and what constraints matter. For example: “Use create-skill to scaffold a new skill named doc-review, generate the SKILL.md frontmatter, and include a workflow for reviewing Markdown docs under skills/.”
That gives the skill enough context to produce something installable rather than a generic draft.
create-skill skill FAQ
Is create-skill only for new skills?
Yes, that is its primary use. The repository explicitly says not to use create-skill for modifying existing skills; edit those directly instead.
Do I need to know the full Agent Skills spec first?
No, that is one reason to install create-skill. It helps you produce scaffolding that aligns with the expected structure and naming rules without memorizing the spec first.
How is this different from an ordinary prompt?
A normal prompt can draft a skill, but create-skill is aimed at making the result consistent with the repository’s conventions. That matters when you care about folder layout, frontmatter completeness, and naming validation.
Is create-skill beginner-friendly?
Yes, if your goal is to create a standard skill and you can provide a clear purpose. It is less helpful if you already have a custom structure in mind that does not match the Skill Scaffolding pattern.
How to Improve create-skill skill
Be precise about the skill name and purpose
The biggest quality jump comes from a specific, valid name and a purpose that states the real outcome. For example, “review pull requests for release risk” is stronger than “help with PRs.”
Give workflow steps that reflect real use
The create-skill skill can only scaffold what you describe. If you want high-quality output, include steps that match the actual task flow, such as discovery, validation, drafting, and final review.
Check the generated structure against your repo
After the first pass, compare the scaffold to your repository conventions. If your repo uses extra folders, naming rules, or metadata fields, add those constraints to the next prompt so the skill can adapt.
Watch for common failure modes
The most common problems are vague descriptions, overly broad purposes, and workflow steps that are too generic to be useful. Tighten the input, then rerun create-skill to improve specificity and reduce cleanup.