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).
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- narrative-blog
- description
- 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).
03 SKILL.md 正文
narrative-blog — Blog 1, the narrative opener (stage 1 of skill2framework)
Ported 2026-07-10 from the proven doc-mirror
narrative-blog-from-aiosprompt-skill (score 1.00, FULL_E2E 2026-06-03). DIY adaptation: the journey source is the AIOS's OWN dir (CLAUDE.md + README + any dev log), and the renderer isskill2framework.journey(no external renderer dependency). This port has not itself been E2E-scored yet.
Your ONE job: turn the AIOS's real journey into Blog 1 by FILLING the
JourneyCore model and letting render_blog1 produce the markdown. You do NOT
hand-write the blog — fill the model, run the renderer (deterministic output).
Inputs (given at dispatch)
- AIOS/package name + root dir
- Journey source: the dir's
CLAUDE.md,README.md, changelog/dev-log — read them FULLY - Plugin / code URL
- Output path for the rendered markdown
Step 1 — reconstruct the journey (grounded, never invented)
From the journey source, extract the Hero arc AS ACTUALLY LIVED:
status_quo (the painful before) · obstacle (the blocker + the moment seen) ·
overcome (the shift + what was built) · accomplishment (the after, feeling + proof) ·
the_boon (the ONE transferable reframe) · demo_description · why_this_matters ·
universal_application · hook (AUTHORED — one clean opening sentence you write).
IS vs VISION discipline: narrate only what the source supports. Do not invent capabilities or results. Mark each field GROUNDED (cite where) vs INFERRED in your report.
Step 2 — fill + render (the whole mechanism)
Run its Python from a plugin install with uv run --no-project --with skill2framework==0.3.6 python3 — pipe a block in as python3 - <<'PY' … PY — and from a clone of the public repository where ./install.sh ran, with the clone's python3.
from skill2framework import JourneyCore, render_blog1
core = JourneyCore(journey_name="...", domain="...", hook="...",
status_quo="...", obstacle="...", overcome="...",
accomplishment="...", the_boon="...", demo_description="...",
why_this_matters="...", universal_application="...",
github_url="...", plugin_url="...")
open(OUTPUT, "w").write(render_blog1(core))
If the import fails, REPORT THE EXACT ERROR — never hand-write the blog as a workaround.
Step 3 — report
The path written + the full markdown + the per-field GROUNDED/INFERRED check.
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).
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).
assemble-chapter
WHAT: assemble a framework CHAPTER from the two rendered blog posts — run skill2framework.assemble_chapter to copy Blog 1 + Blog 2 verbatim into a self-contained chapter dir, wire the relative cross-links + plugin/skill links + CTAs, and write the chapter.md manifest. WHEN: when Blog 1 + Blog 2 exist and need combining into the publishable chapter unit, or when the user says assemble a chapter / skill2framework (any of).