跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

comic-author

Phase 1 ORCHESTRATOR of a movie/comic — turn a fuzzy story idea into the Authored Source of Truth (a schema-valid comic.json + its locked asset library) by driving the detailed author skills in order (intent → style → outline → storyboard → assets → blueprints → prompts → comic.json), each gated by comic-cross-layer-gate, so comic-director (Phase 2/3) can bake + cross-model-verify it. You don't hand-write comic.json; this is the workflow your agent runs to author it. Use when the user says "做个漫画/电影", "from this idea make a comic", "author the comic.json", "run the comic pipeline".

wanshuiyin · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add wanshuiyin/ARIS-Movie-Director --skill comic-author

技能说明


name: comic-author description: Phase 1 ORCHESTRATOR of a movie/comic — turn a fuzzy story idea into the Authored Source of Truth (a schema-valid comic.json + its locked asset library) by driving the detailed author skills in order (intent → style → outline → storyboard → assets → blueprints → prompts → comic.json), each gated by comic-cross-layer-gate, so comic-director (Phase 2/3) can bake + cross-model-verify it. You don't hand-write comic.json; this is the workflow your agent runs to author it. Use when the user says "做个漫画/电影", "from this idea make a comic", "author the comic.json", "run the comic pipeline".

comic-author — the Pipeline-A Orchestrator (Phase 1)

The left third of Figure 1, as an agent-run workflow: a fuzzy idea → a comic.json + its locked asset library, so comic-director (Phase 2/3) bakes + adversarially verifies it. This skill is thin — it owns the ORDER, the BARRIERS, and the HAND-OFF; each step's real procedure lives in its own detailed skill.

End-to-end in one slash-command? movie-pipeline is the single entry that drives THIS skill (Phase 1) → the p0_proof gate → comic-director (Phase 2/3 bake) → viewer. comic-author is the Phase-1 half it calls; use it directly when you only want to author + lock the comic.json. The contract boundary to Phase 2/3 is comic.json + the assets it references (content-SVG blueprints, identity refs, ART_BIBLE.md).

How you "run" this — it is an AGENT workflow, not a shell CLI. You point your coding agent (Claude, Codex, …) at this skill; the agent FOLLOWS the steps below — authoring the wiki nodes and calling the few deterministic helper scripts that ARE real CLIs: comic-director/scripts/run_comic.py, cli/validate_wiki.py, comic-panel-prompt-builder/scripts/build_prompt.py. The --gate <kind> notations below are the agent PROCEDURE in comic-cross-layer-gate (fan out the cross-model reviewers → fuse → flip status) — not a binary you exec. This mirrors every ARIS skill: the SOP is the product, a coding agent is the runtime.

Two hard human gates (never auto-proceed): the intent and the outline are story decisions — the user must approve each before the next layer starts (the story-first rule; the gate is acceptance-gate). Everything downstream is agent-driven + cross-model gated.

The pipeline (run in order) — the N1 two-stage DAG (each step = a detailed skill + its gate)

Dependencies are the node_schema source_* fields, not invented — each step consumes the prior locked node. The two-stage shape is the deadlock fix: the outline gate demands every referenced asset_id be DECLARED with a complete, generatable request (never locked — assets don't exist yet on a fresh project); the storyboard runs a provisional structural pass first; the ONE hard locked-asset barrier sits before blueprint authoring (step 7), reached via two cheap gate re-passes (6a/6b).

#Step → skillProducesGate (via comic-cross-layer-gate)
1comic-intent-parserintent_specUSER approves → --gate intent
2comic-style-bible-lockstyle_anchor×N + ART_BIBLE.mdstyle lock (design-aware)
3comic-outline-creatoroutline_spec (3-lens → synth)OUTLINE_DRAFT_VALID (--gate outline: narrative+continuity+safety; asset_ids DECLARED, not locked) → USER approves → locked
4comic-storyboard-creatorPROVISIONAL storyboard_spec + panel_spec×N + motif_ledger + consolidated asset_requests--gate storyboard structural pass (may reference draft assets)
5comic-asset-ref-generatorasset×N (single-source, from the requests)—
6comic-asset-review-loopeach asset → status: locked (准×3)--gate asset · assets LOCKED
6aOUTLINE_FINAL_LOCK (gate re-pass, no new skill)outline re-check decision nodecheap re-check: the locked assets still match the approved outline (identity/scene_lock_feasibility scored HERE)
6bstoryboard FINAL validation (gate re-pass)storyboard_spec → lockedre-run --gate storyboard: panel_assets_referenceable (resolves AND locked) now satisfiable · ASSET-LOCK BARRIER ↓
7comic-blueprint-authorblueprint×N (content-SVG, no baked bubbles)--gate blueprint (the locked-asset HARD barrier lives here)
8comic-panel-prompt-builderprompt_bundle×N (搬运工原則)build asserts: literal / zero-text / ref-count
9comic-json-compilercomic.json (authored fields only)--gate compile (run_comic --dry-run + validate_wiki)

Entry/exit contract per step (what each consumes → hands off):

#EntryExit
1the user's fuzzy idealocked intent_spec
2intent_speclocked ART_BIBLE.md + style_anchor×N
3intent_spec (+ its skeleton)locked, user-approved outline_spec (motif arcs + declared asset_ids)
4locked outline_specprovisional storyboard_spec / panel_spec×N / motif_ledger + consolidated asset_requests
5consolidated asset_requests + ART_BIBLE.mddraft asset×N (files + nodes)
6draft asset×Nlocked asset×N
6a/6bapproved outline + provisional storyboard + locked assetsoutline re-check `d
阅读完整来源 ↗