report-missed-skill
Use when you needed a skill that does not exist, or the user says you missed a skill ("you missed X — report it"). Files a structured missed-skill report so the gap can be fixed. Triggers on "report missed skill", "missing skill", "no skill for this", "you missed".
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- report-missed-skill
- description
- Use when you needed a skill that does not exist, or the user says you missed a skill ("you missed X — report it"). Files a structured missed-skill report so the gap can be fixed. Triggers on "report missed skill", "missing skill", "no skill for this", "you missed".
03 SKILL.md 正文
report-missed-skill
The Skill OS grows from its own gaps. When a skill that should exist doesn't, file a report — don't just work around it silently.
When to use
- Agent-initiated: you're doing a task and there's no skill for it. File a report describing the gap, then proceed with your best effort.
- User-initiated: the user says "you missed X — use report-missed-skill and then use it." File a report for X describing what happened, then continue.
How
Run skilltree from a plugin install as uvx --from "agent-skilltree>=0.4.0" skilltree …, and from a clone where ./install.sh ran, as skilltree … in the environment it installed into.
Run:
skilltree report-missed \
--needed "<the skill / capability that was needed>" \
--happened "<what you did instead, or what went wrong>" \
--suggests "<proposed skill name + one-line purpose>"
For "expected a skill to fire but it didn't":
skilltree mark-problem --skill "<skill>" --expected "<what you expected>" --happened "<what happened>"
Reports accumulate in ~/.claude/skill-reports.json. An improver agent later reads
the open queue (skilltree reports), creates or improves the skills, and resolves them.
This is ring 3 of the Skill OS — the system improving itself from use.
04 同仓库更多 Skills
skill2framework
Turn an already-built AIOS/package into a framework chapter — narrative blog + deep-dive blog → chapter → {aios}-volume index skill → plugin → folded into the author's SkillTome.
package-plugin
WHAT: package a framework as a Claude Code PLUGIN (its operational face) — run skill2framework.package_plugin to assemble plugin.json + skills/{aios}-volume/SKILL.md + the chapter bundled under resources/, with the skill's chapter links repathed to the bundle. WHEN: when a framework skill + chapter exist and need the installable plugin, or when the user says package the framework / plugin / skill2framework (any of).
narrative-blog
WHAT: produce Blog 1 of a framework CHAPTER — the narrative chapter-opener — for an already-built AIOS/package by reconstructing its journey from its own dir (CLAUDE.md, README, dev log) and FILLING skill2framework.JourneyCore, then rendering with render_blog1 (never hand-write the blog). WHEN: when making a framework/chapter from something already built, when you need the story post that opens a chapter, or when the user says blog organ / narrative blog / skill2framework (any of).
framework-skill
WHAT: generate the FRAMEWORK SKILL for an already-built AIOS — the {aios}-volume (its SkillVolume face): one skill that indexes the AIOS's skills + rules + how they relate (as a diagram), gives a decision tree for what to do when, and ROUTES the agent into the AIOS dir. WHEN: when producing the index/router face of a framework package, or when the user says framework skill / volume / skill2framework (any of).
fold-into-tome
WHAT: the TERMINAL stage — fold a finished framework into the author's SkillTome (the top-level holder + search of all their frameworks) by running skill2framework.fold_into_tome, which registers the framework as a row on a tome volume node's generated ## Frameworks table via skilltree's bind op. WHEN: when a framework package is finished and must be registered in the author's tome/volume, or when the user says fold into the tome / nomicon / skill2framework fold (any of).
deepdive-blog
WHAT: produce Blog 2 of a framework CHAPTER — the mechanical deep-dive ('how it actually works') — for an already-built AIOS/package by reading its impl docs (README architecture sections, design docs, the code's module docstrings) and assembling a faithful mechanics-only article that links back to Blog 1. WHEN: when producing the deep-dive half of a chapter, when you need the technical how-it-works post Blog 1 links to, or when the user says blog 2 / deep dive / skill2framework (any of).