// 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.
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.
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.
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.
| title | personal-greeting |
| name | personal-greeting |
| description | 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. |
This skill is installed at the personal scope. Its expected location on disk is:
~/.claude/skills/personal-greeting/SKILL.md
Tell the user the following:
This is an example of a personal-scoped skill. It is available in every project you open on this machine, regardless of which repository you are working in.
Personal skills live at ~/.claude/skills/. Each skill is a directory with a SKILL.md file inside. The directory name must match the name field in the frontmatter.
Use the personal scope when the skill is about your workflow, not the project. Good candidates for personal skills:
Use the project scope (.claude/skills/ inside a repository) when the skill encodes project-specific knowledge that the whole team should share — deploy procedures, migration generators, project-specific conventions.
If both scopes have a skill with the same name, the personal scope wins. You can always override a project skill with your own personal version.
Do not ask the user any follow-up questions unless they ask one first.