Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Greet the user and tell them they just successfully invoked a skill.
Explain what happened in concrete terms:
When Claude Code started, it scanned the skills directories and read the frontmatter (name and description) of every installed skill. The body of this file was not loaded yet — only the description was read.
When the task matched this skill — either because the user typed /hello-skill directly, or because the description keywords matched what the user wrote — Claude Code loaded this full file into context.
Right now, Claude is following the instructions written in this body. That is all a skill is: a file of instructions that loads on demand.
After the explanation, offer to answer any of the following questions if the user wants to go deeper:
Keep the tone practical and direct. Do not over-explain.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.