Skill: new-skill
Adding a skill touches four places — the canonical skills/<name>/SKILL.md, its llmwiki/skills/<loop>/<name>.md mirror, the sync-skills.py LOOP_MAP, the marketplace.json publish list, and a row in the AGENT.md/CLAUDE.md ## Skills table. Miss one and the trees drift (that is how marketplace.json fell ~30 skills behind). This skill drives fdk/tools/new-skill.py, which writes the two mechanical files identically and prints the exact lines for the three curated places — it never edits them itself.
When to use
- The user asks to create / add / scaffold a new skill, or invokes
/new-skill. - You are about to hand-create a
skills/<name>/SKILL.mdand would otherwise forget the mirror or the registry surfaces.
Viết cho đúng nghề — đọc
[[skill-craft]]trước. Bộ từ vựng để một skill đoán được: hai loại phí (context load ↔ cognitive load — skill chỉ-gọi-tay thì khaidisable-model-invocation: true, khỏi tốn context), completion criterion cho mỗi bước, leading word thay ba câu, và năm failure mode phải tránh (duplication/sediment/sprawl/no-op/negation)./lintbước 8b đo các thứ này bằng máy.
Steps
- Settle three inputs: a kebab-case
<name>, a--loop(dev-loop|orchestrate|wiki-loop|utils), and a--descthat is rich with trigger phrases (the description is what the skill router matches on). Skill chỉ-gọi-tay (chỉ user gõ, không skill nào khác gọi) → thêmdisable-model-invocation: true,--descrút thành một dòng người-đọc (xem[[skill-craft]]). - Preview first, then create:
It refuses ifpython3 fdk/tools/new-skill.py <name> --loop <loop> --desc "<description>" --dry-run # preview body + next steps python3 fdk/tools/new-skill.py <name> --loop <loop> --desc "<description>" # write both filesskills/<name>/already exists. - Fill in the generated
skills/<name>/SKILL.md— replace the TODOWhen to use/Steps/Rulesplaceholders with real, verifiable content. - Re-mirror after editing so the llmwiki copy stays byte-identical:
python3 harness/scripts/sync-skills.py - Register on the curated surfaces by pasting the exact lines the tool printed: add the LOOP_MAP entry in
harness/scripts/sync-skills.py, (optionally) the./skills/<name>line in.claude-plugin/marketplace.json, and one row in BOTHllmwiki/AGENT.mdandllmwiki/CLAUDE.md## Skillstables. - Verify every surface agrees — both must pass:
python3 harness/scripts/sync-skills.py --check # mirror parity python3 harness/scripts/skill-registry.py --check # cross-surface drift
Rules
- The tool writes ONLY the two mechanical files (canonical + mirror). It never edits LOOP_MAP, marketplace.json, AGENT.md, or CLAUDE.md — those are user-curated; you add the printed lines by hand.
- After editing the generated skeleton, ALWAYS re-run
sync-skills.py— parity is enforced, and your edits will have made the mirror stale. - A vague
--descis a skill that never fires. Put concrete trigger phrases and/-commands in it. - Never overwrite an existing skill — if the name is taken, edit
skills/<name>/SKILL.mdin place or pick another name.