Borrowing it
Nothing to install: this file belongs to pleaseai/claude-code-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pleaseai/claude-code-plugins/main/.claude/commands/generate-skill.mdgit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/pleaseai/claude-code-plugins/generate-skill)<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/generate-skill"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/generate-skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/generate-skill"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/generate-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00566 |
| Opus 5.5 | $0.00014 | $0.00226 |
| Sonnet 5.5 | $0.00007 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
generate-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Generate agent skills for the project: $ARGUMENTS
Follow the guidelines in docs/skills-generator.md to generate Type 1 skills.
Steps
- Read
docs/skills-generator.mdfor the full generation guidelines - Check
vendor/antfu-skills/instructions/$ARGUMENTS.mdfor project-specific instructions (if it exists) - Read source docs from
sources/$ARGUMENTS/docs/ - Generate skill files into
skills/$ARGUMENTS/:SKILL.md— index with frontmatter (name,description,metadata) and a table of all referencesGENERATION.md— tracking metadata (source path, git SHA, generation date)references/*.md— one file per concept (prefixed by category, e.g.core-syntax.md,features-plugins.md)
- Copy the generated skills into the plugin directory:
mkdir -p "plugins/$ARGUMENTS/skills/$ARGUMENTS/" && cp -r "skills/$ARGUMENTS/." "plugins/$ARGUMENTS/skills/$ARGUMENTS/"Note:
bun run skills:synconly handles Type 2 (vendor) and Type 3 (manual) skills. Type 1 (generated) skills must be copied manually to the plugin directory. - Commit the generated skills:
git add skills/$ARGUMENTS/ plugins/$ARGUMENTS/skills/$ARGUMENTS/ git commit -m "feat($ARGUMENTS): generate skills from official documentation"
Output Location
- Source docs:
sources/$ARGUMENTS/(submodule, runbun scripts/cli.ts initif missing) - Generated skills:
skills/$ARGUMENTS/(our own skills directory, never modifyvendor/antfu-skills/) - Synced to plugin:
plugins/$ARGUMENTS/skills/$ARGUMENTS/
Writing Guidelines
- Rewrite docs for agents — synthesize, don't copy verbatim
- Focus on practical usage patterns and code examples
- Omit installation guides, introductions, and content agents already know well
- One concept per reference file
- Include working code examples
- Explain when and why to use each feature, not just how
- Keep each reference file concise (under 200 lines)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 45 lines · 35 tokens per session scan A 8a68b1ba67cb
generate-skill is a command published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 566 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.