// 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.
| title | hello-skill |
| name | hello-skill |
| description | 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. |
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.
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
Review code against a standard checklist covering security, correctness, performance, and readability. Use when asked to review code, check a PR, or audit changes.