skilling-it
Skilling It
Create effective Claude Code skills following best practices for discovery, progressive disclosure, and maintainability.
Quick Start
Create a skill in 5 steps:
- Create directory:
mkdir -p ~/.claude/skills/my-skill-name - Create SKILL.md with frontmatter (see template below)
- Write description as triggering conditions ("Use when...")
- Add instructions in imperative form
- Validate against the checklist
Minimal template:
More from v1-io/v1tamins
interview-me
Use when the user provides an idea, feature request, Linear ticket, or concept that needs fleshing out. Triggers on "interview me about X", "help me spec out Y", "I have an idea for Z", "flesh out this idea".
12complexity
Use when reducing cognitive complexity, flattening nested code, or simplifying functions. Triggers on "reduce complexity", "simplify", "too nested".
10code-review
Use when reviewing a PR or posting code review feedback to GitHub. Triggers on "review this PR", "code review", "check this pull request".
9write-tests
Use when writing unit tests for code changes or new functionality. Triggers on "write tests", "add tests", "test this code".
9pr-description
Use when writing or updating a PR description on GitHub. Triggers on "write PR description", "update PR body", "describe this PR".
8address-review
Use when addressing PR review comments from Copilot, bots, or humans. Triggers on "fix review comments", "address Copilot feedback", "respond to PR comments".
8