example-command
An example user-invoked skill that demonstrates frontmatter options and the skills/<name>/SKILL.md layout
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 4.7w
- Forks
- 4.9k
01 前言 Front Matter
- name
- example-command
- description
- An example user-invoked skill that demonstrates frontmatter options and the skills/<name>/SKILL.md layout
- allowed-tools
- [ "Read", "Glob", "Grep", "Bash" ]
- argument-hint
- <required-arg> [optional-arg]
03 SKILL.md 正文
Example Command (Skill Format)
This demonstrates the skills/<name>/SKILL.md layout for user-invoked slash commands. It is functionally identical to the legacy commands/example-command.md format — both are loaded the same way; only the file layout differs.
Arguments
The user invoked this with: $ARGUMENTS
Instructions
When this skill is invoked:
- Parse the arguments provided by the user
- Perform the requested action using allowed tools
- Report results back to the user
Frontmatter Options Reference
Skills in this layout support these frontmatter fields:
- name: Skill identifier (matches directory name)
- description: Short description shown in /help
- argument-hint: Hints for command arguments shown to user
- allowed-tools: Pre-approved tools for this skill (reduces permission prompts)
- model: Override the model (e.g., "haiku", "sonnet", "opus")
Example Usage
/example-command my-argument
/example-command arg1 arg2
04 同仓库更多 Skills
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
session-report
Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts.
receipts
Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receipts`.
project-artifact
Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live state, redeploys the same URL, and reports only the delta. For software projects whose workstreams are PRs, also read swe.md (the X.Y PR-numbering convention; pulling PR state with gh/git; a per-PR detail block). Needs the built-in Artifact tool (claude.ai login). Not for single-PR changes or public docs.
skill-development
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
plugin-structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.