Skill Skill
Write, upgrade or audit a Claude skill so it actually changes what gets generated, not a pile of notes. Use whenever the user wants to create a skill, turn a conversation, workflow or methodology into a skill, rename it, add research or lessons, asks why a skill isn't taking effect, or wants to publish a skill and get it listed in awesome lists and plugin marketplaces. Covers distilling from real work (corrections, rejections, accepted outputs), forcing functions (required artifacts, gates, checklists, scripts), descriptions that trigger, naming, a static audit with a health score, a with/with
Install
npx skills add jack-reson8/skill-skill --skill skill-skillgit clone --depth 1 https://github.com/jack-reson8/skill-skill.git /tmp/skill-skill
mkdir -p ~/.claude/skills
cp -r /tmp/skill-skill/plugins/skill-skill/skills/skill-skill ~/.claude/skills/skill-skillPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill · skill
A skill is worth its tokens only if, when it runs, the output is different: a decision is made that wouldn't have been, an artifact exists that wouldn't have, a mistake is caught. Length is not the problem; lines that change nothing are. For every paragraph ask: **what will the model do differently because of this?** If nothing, it belongs in a reference that a step explicitly uses, or nowhere.
For heavy benchmarking (many evals, variance, description optimisation loops) use Anthropic's `skill-creator`; this skill is the fast path for turning real work into a skill that bites.
## 1 · Distil from the real work
Mine the conversation (or the user's notes) before writing anything:
- **Across many sessions:** `python3 <this skill's base directory>/scripts/mine_corrections.py --days 30` ranks the user's repeated corrections by how many sessions they recur in, with dated quotes. A recurring theme no skill covers is a candidate skill.
- **Corrections and rejections** in the user's own words ("太 PPT", "越改越不好", "too EDM"). Each becomes a rule with its reason, or a check.
- **Accepted outputs**: what finally worked and *why* (the mechanism, not the adjectives).
- **Repeated work**: anything done by hand twice (a conversion, a check, a render) becomes a script in `scripts/`.
- **Facts from research**: keep only those that change a decision; mark what was verified (✓) and what wasn't (u). Never let an unverified number become a rule.Details
- Skill name
skill-skill- Repository
- jack-reson8/skill-skill
- Path
plugins/skill-skill/skills/skill-skill/SKILL.md- License
- MIT
- Repo updated
- 25 October 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Skill Skill skill do?
Write, upgrade or audit a Claude skill so it actually changes what gets generated, not a pile of notes. Use whenever the user wants to create a skill, turn a conversation, workflow or methodology into a skill, rename it, add research or lessons, asks why a skill isn't taking effect, or wants to publish a skill and get it listed in awesome lists and plugin marketplaces. Covers distilling from real work (corrections, rejections, accepted outputs), forcing functions (required artifacts, gates, checklists, scripts), descriptions that trigger, naming, a static audit with a health score, a with/with
How do I install the Skill Skill skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jack-reson8/skill-skill --skill skill-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Trade Show Prep
DataOrigin/trade-show-prep-skill
Prepare, work and follow up a B2B trade show for an exhibitor or a visiting sales team. Builds a dated plan from 8 weeks before the fair, drafts meeting requests for the user's own accounts (email and LinkedIn), writes a booth qualification guide with a note template, and drafts a post-show follow-up sequence with cost per lead and ROI. Use when the user says "prepare our trade show", "we are exhibiting at", "we are visiting a fair", "meeting requests for the show", "booth qualification", "trade show follow-up", "post-show emails" or asks for help before, during or after a B2B fair or conferen
Project Planning Journaling
mh-mansouri/Project-Planning-Journaling
Scope a new project (or resume one) and set up a living, resumable documentation journal for it, including a routine weekly health check, not just updates triggered by commits. Use at the start of any project, before writing code, to ask about project type, Git repo status, short/long-term goals, and whether it should stay public/open-source or become a private product later. Also use when someone wants to document what has been done, wants a changelog or decision log, needs to resume work from a prior session without re-reading chat history, wants docs kept current after every commit, or want
Unpaid Intern
kevinmmiddleton/unpaid-intern
Unpaid Intern runs a portable second brain for knowledge work: a plain-file workspace for projects, decisions, follow-ups, and meeting notes, plus optional live reads of mail, chat, calendar, tracker, and wiki, so nothing starts from scratch between meetings. Use when someone wants to set up or run a work second brain, work agent, or work assistant; runs one of its commands (/briefing, /pulse, /prep, /who, /debrief, /capture, /close, /gofer, /project-status, /redline, /slots, /triage, /sync-kb, /kb-lint, /tidy, or another command from the kit) in that workspace; asks to prep a meeting, turn a
Cooper Email
cooper-email/cooper-email
Give the agent its own real email inbox with Cooper Email (cooperemail.com) and send, receive, search, and wait for mail over MCP or HTTP. Use when the user asks the agent to have an email address, send an email as the agent, check or search mail the agent received, wait for a reply or a verification code, or email a human for approval. If the user asked for Cooper Email, do not substitute another mail API.
001 Jeremy Taskwarrior Integration
jeremylongshore/claude-code-plugins-plus-skills
Enforces complete Taskwarrior integration protocol for ALL coding tasks. Activates automatically when user mentions "taskwarrior", "task warrior", "tw", or discusses task management. Decomposes all coding work into properly tracked Taskwarrior tasks with full lifecycle: task add → task start → implementation → task done. Integrates with Timewarrior for automatic time tracking.
Workflow Design
1ghorbanies/workflow-design
Models, proves, measures, and safely changes multi-step workflows — approval chains, review pipelines, intake/triage/fulfillment flows, ticketing, order processing, state machines with human gates. Use when designing states/gates/transitions or an audit trail, when a status field or event log is being added to a system, when tests guarding a workflow need auditing ("the suite is green but I don't trust it"), when someone asks where items get stuck, whether an approval step is worth keeping, who approved something, or why a queue is growing, or when a live workflow's definition must change with
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.