skill-creator
Skill Creator
This skill wraps Anthropic's official skill-creator with local context.
Skill Types
User skills (~/.claude/skills/<name>/):
- Portable across all projects
- General-purpose utilities (file-nav, code-search, github, etc.)
- NOT tied to any specific repository
Project skills (.claude/skills/<name>/ in repo root):
- Repository-specific knowledge and workflows
- Codebase conventions, testing patterns, deployment procedures
- Only available within that project
Workflow
1. Determine Skill Type
Before creating a skill, clarify with the user:
- User skill: "Should this skill be available across all your projects?"
- Project skill: "Is this specific to the current repository?"
If unclear, ask using AskUserQuestion.
2. Fetch Upstream Guidance
For skill creation best practices, fetch Anthropic's skill-creator:
WebFetch: https://raw.githubusercontent.com/anthropics/skills/main/skills/skill-creator/SKILL.md
For specific patterns:
- Workflows:
https://raw.githubusercontent.com/anthropics/skills/main/skills/skill-creator/references/workflows.md - Output patterns:
https://raw.githubusercontent.com/anthropics/skills/main/skills/skill-creator/references/output-patterns.md
3. Create the Skill
Apply upstream guidance with these local defaults:
| Skill Type | Path |
|---|---|
| User | ~/.claude/skills/<skill-name>/SKILL.md |
| Project | .claude/skills/<skill-name>/SKILL.md |
4. Key Reminders
From upstream skill-creator (fetch for full details):
- Concise is key: Context window is shared; only add what Claude doesn't know
- Progressive disclosure: SKILL.md body < 500 lines; use
references/for details - Frontmatter description: Must include "when to use" - body loads AFTER triggering
- No extra docs: No README.md, CHANGELOG.md, etc.
Existing User Skills
Reference for patterns:
~/.claude/skills/
├── clj-symbols/ # Clojure symbol navigation
├── code-rename/ # Symbol renaming
├── code-search/ # ripgrep patterns
├── code-symbols/ # ast-grep symbol finding
├── file-nav/ # fd file navigation
├── github/ # gh CLI operations
└── playwright/ # Browser automation
More from brettatoms/agent-skills
alpinejs
AlpineJS best practices and patterns. Use when writing HTML with Alpine.js directives to avoid common mistakes like long inline JavaScript strings.
106janet
Write idiomatic Janet code. Use when writing, refactoring, or reviewing Janet (.janet) code. Covers functional patterns, performance tradeoffs, common gotchas, data structure idioms, PEG parsing, and Janet-specific pitfalls.
10playwright
Browser automation for web testing and interaction. Use for navigating pages, filling forms, clicking elements, taking screenshots, and inspecting page content. Maintains stateful browser session across commands.
9code-symbols
Find and edit symbols in code using ast-grep (tree-sitter based). Use when finding function definitions, class definitions, symbol usages, renaming symbols, or replacing code in JavaScript, TypeScript, Python, Go, Rust, and other languages. NOT for Clojure - use clj-symbols instead.
8browser-tools
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
8github
Work with GitHub using the gh CLI. Use when creating/managing pull requests, reviewing code, managing issues, viewing GitHub Actions runs, creating releases, or making API requests. Triggers on GitHub-related tasks like "create a PR", "list open issues", "check CI status", "merge this PR", or "create a release".
7