graph-auditor
Chain-of-reasoning (spoken, ends in a decision) — an orphan node has no reason to exist, an ambiguous arrow is a lie, and invisible feedback is a hidden loop — find them and repair the graph.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- kind
- chain-of-reasoning
- name
- graph-auditor
- description
- Chain-of-reasoning (spoken, ends in a decision) — an orphan node has no reason to exist, an ambiguous arrow is a lie, and invisible feedback is a hidden loop — find them and repair the graph.
03 SKILL.md 正文
This is a chain of reasoning (CoR) — a SPOKEN, paragraphical reasoning chain that ends in a DECISION. Say it as a paragraph; keep the moves in order.
CoR (custom syntax)
[Graph] ⇒ [OrphanNodes] ⇒ [AmbiguousEdges] ⇒ [AbstractionCollisions] ⇒ [MissingTransitions] ⇒ [FeedbackVisibility] ⇒ |RepairedGraph|
Say it as a paragraph, in order
State your reasoning as ONE paragraph that performs, in order, 7 moves: Graph, OrphanNodes, AmbiguousEdges, AbstractionCollisions, MissingTransitions, FeedbackVisibility, and finally converges on RepairedGraph. [Graph: …the constructed graph…] → [OrphanNodes: …nodes nothing reaches…] → [AmbiguousEdges: …an ambiguous arrow is a lie…] → [AbstractionCollisions: …incompatible levels in one chain…] → [MissingTransitions: …the step the diagram skips…] → [FeedbackVisibility: …feedback as a loop, never an implied return…] → [RepairedGraph: …every defect repaired or the distinction kept…]
Inner attention chain (use silently to generate the above)
Attention chain — Graph-Auditor
Attend, in order:
- Graph
- OrphanNodes
- AmbiguousEdges
- AbstractionCollisions
- MissingTransitions
- FeedbackVisibility Hold: RepairedGraph ← converge attention here, then act
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).