Menu

Individual skill

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/without effect test, and a publish preflight plus PR triage for listings. Triggers: 写 skill, 改 skill, 沉淀进 skill, 优化 skill, 发布 skill, 提 PR 收录, 仓库机器人报错; スキルを作る, スキル作成; 스킬 만들기, 스킬 개선; tạo skill, viết skill; स्किल बनाना.

plugins/jack-reson8/skill-skill/skills/skill-skill/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.