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.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
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 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.
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.