Skill template

Skill shubham0704/claude-skills/docs/skill-template

Skills that help YOU operate at staff-researcher level. The agent does the grunt work; you stay in the driver's seat. A proper workflow for polishing ideas, expressing them rigorously, and implementing them properly. Works with Claude Code + Codex.

Install

npx -y skills add shubham0704/claude-skills --skill skill-template

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

One-line WHAT this skill does + two to three sentences on WHEN to trigger it. Be specific about contexts and use a pushy tone — skills undertrigger by default. Mention related phrases the user might say even when they don't name the skill explicitly. Replace this with your own description.

SKILL.md

2.4 KB, as published. Nobody here has run it

_template

Replace this with a 1–3 sentence summary of what this skill helps Claude do. Keep it tight — the full reasoning belongs below, not here.

1. Workflow

Start with the end-to-end workflow. Imperative style. Short sections. Give the reader (Claude) enough structure that they can scan for the step they need.

1.1 Setup (if any)

1.2 Main loop

1.3 Hand-off / completion criteria

2. Core content

The bulk of the skill. For review-style skills, this is typically a numbered list of failure modes and canonical fixes. For building- style skills, it's usually a sequence of phases with decision criteria. For writing-style skills, it's sections + patterns.

Use sub-sections freely. Keep any single section short enough to scan.

3. Checklist / decision points

If this skill has a checklist, rubric, or review order, put it here so it's findable. Otherwise delete this section.

4. Bundled resources

references/ — docs loaded on-demand when the body points at them
scripts/ — executable utilities (if any)
assets/ — templates/fixtures used in output

If a section of this skill is long, move it to references/ and point here with a sentence like "See references/snippets.md for copy-paste patterns."

5. Pitfalls

List of things to watch out for. One bullet each, imperative mood.

Notes for skill authors

When creating a skill from this template:

Pick a kebab-case directory name. Rename the directory, not just the frontmatter.
Fill in name: and description: in the frontmatter. Make the description pushy — mention specific trigger contexts beyond the obvious ones, including related phrases the user might say.
Start at version: 0.1.0 (initial draft) or 1.0.0 (first stable release you're willing to recommend to others).
Keep this file under ~500 lines. Push overflow into references/, scripts/, or assets/.
Create a CHANGELOG.md alongside this file (see _template/) and log your first entry.
Delete this "Notes for skill authors" section from your final skill.