Token导航 LogoToken导航TokenDH.com
前端设计只读github未标认证来源可访问许可证需确认审计通过

crucible-outliner坩埚轮廓线

Agent Skill

crucible-outliner 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

194

周安装

8

GitHub Stars

48

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:crucible-outliner(坩埚轮廓线)
来源仓库:https://github.com/forsonny/the-crucible-writing-system-for-claude
仓库路径:skills/crucible-outliner
安装命令:
npx skills add https://github.com/forsonny/the-crucible-writing-system-for-claude --skill crucible-outliner
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/forsonny/the-crucible-writing-system-for-claude --skill crucible-outliner

简介

crucible-outliner 将 Crucible 规划文档转化为详细的章节级叙事大纲,注重情节连贯性。

  • 适用于史诗奇幻类作品的蓝图展开,融合节拍映射与场景结构设计原则。
  • 严格遵循用户提问交互机制,每次最多四个选项与四次追问,确保控制权归属作者。
  • 输出仅为结构框架,具体内容仍需人工填充,避免 AI 越俎代庖破坏创作主权。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Crucible Outliner

Transform Crucible planning documents into detailed chapter-by-chapter outlines with proper narrative craft.

Before Starting

Read these references based on the outlining phase:

  • references/beat-to-chapter-mapping.md — How 36 beats map to chapters
  • references/narrative-craft.md — Foreshadowing, pacing, scene structure
  • references/outline-templates.md — Chapter and scene outline formats

Questioning Rules

  1. ALWAYS use AskUserQuestion tool for all user questions (provides interactive UI)
  2. Max 4 options per question (tool limit) + "Other" is automatic
  3. Max 4 questions per AskUserQuestion call
  4. Reference user's story elements by name (characters, places, etc.)
  5. Save state after each chapter outline

CRITICAL: Use the AskUserQuestion tool, NOT plain text A/B/C options.

Required Inputs

The user must have completed Crucible planning. Request uploads of:

  1. Crucible Thesis (required first) — Core elements: burden, fire, constellation, theme
  2. Strand Maps (required) — Quest, Fire, Constellation arcs
  3. Forge Point Blueprints (required) — The convergence crises
  4. Constellation Bible (as needed) — Character details
  5. Mercy Ledger (as needed) — Setup/payoff tracking
  6. World Forge (as needed) — Setting details

Workflow

Phase 1: SETUP → Load planning docs, confirm scope, establish parameters
Phase 2: STRUCTURE → Map beats to chapters, identify act breaks
Phase 3: CHAPTERS → Outline each chapter through questions
Phase 4: CRAFT → Add foreshadowing threads, verify payoffs
Phase 5: COMPILE → Generate final outline documents

Phase 1: Setup

Load Planning Documents

Request the Crucible Thesis first:

To begin outlining, I need your Crucible planning documents.

Please upload your **Crucible Thesis** (or paste its contents).
This contains your core elements: burden, fire, constellation, theme, etc.

After receiving, extract and confirm:

  • Theme
  • Burden type
  • Fire nature
  • Core bond
  • Dark mirror connection
  • Surrender moment
  • Blade's purpose

Confirm Scope

Use AskUserQuestion to confirm scope:

{
  "questions": [
    {
      "header": "Book Type",
      "question": "Which book are we outlining?",
      "options": [
        {"label": "Standalone novel", "description": "A single, complete novel"},
        {"label": "Book in series", "description": "Part of a larger series (specify which book)"},
        {"label": "Series overview", "description": "Full series overview first, then individual books"}
      ],
      "multiSelect": false
    },
    {
      "header": "Chapter Count",
      "question": "What is your target chapter count?",
      "options": [
        {"label": "Standard (20-25)", "description": "Typical novel length"},
        {"label": "Compact (15-20)", "description": "Tighter, faster-paced structure"},
        {"label": "Extended (25-35)", "description": "More room for subplot development"},
        {"label": "Story dictates", "description": "Let the narrative determine chapter count"}
      ],
      "multiSelect": false
    }
  ]
}

Initialize Project

python scripts/init_outline.py "./outline-project" "Title" "Book X of Y"

Phase 2: Structure

Map Beats to Chapters

Using references/beat-to-chapter-mapping.md, establish the chapter skeleton:

For standard 20-25 chapter book:

MovementBeatsChapters% of Book
I. Ignition1-61-510%
II. First Tempering7-146-1020%
III. Scattering15-2211-1625%
IV. Brightest Burning23-2817-2125%
V. Final Forging29-3422-2415%
Coda35-36255%

Present the proposed structure:

**Proposed Chapter Structure for [Title]**

MOVEMENT I — IGNITION (Chapters 1-5)
• Ch 1: [Beat 1 - The Unlit Forge]
• Ch 2: [Beats 2-3 - Dual Arrival + First Spark]
• Ch 3: [Beat 4 - The Burden Chosen]
• Ch 4: [Beat 5 - First Constellation]
• Ch 5: [Beat 6 - IGNITION FORGE POINT]

[Continue for all movements...]

Use AskUserQuestion to confirm:

{ "questions": [ { "header": "Structure", "question": "Does this chapter structure work for your story?", "options": [ {"label": "Approve structure", "description": "Proceed with this chapter layout"}, {"label": "Adjust count", "description": "Modify the number of chapters"}, {"label": "Discuss sections", "description": "Talk through specific movements or chapters"} ], "multiSelect": false } ] }


### Request Additional Documents

Based on which movement is being outlined, request relevant docs:

- Movements I-II: Request Forge Point 0 and 1 blueprints
- Movement III: Request Forge Point 2, Mercy Ledger
- Movement IV: Request Forge Point 3, Dark Mirror Profile
- Movement V: Request Forge Point Apex, full Constellation Bible

## Phase 3: Chapter Outlining

### Question Format for Each Chapter

For each chapter, work through:

CHAPTER [X]: [Working Title] Beat(s): [Which Crucible beats this covers] Strand Focus: [Quest/Fire/Constellation] POV: [If dual/multiple POV]

1. OPENING Where does the reader enter this chapter? A) Immediate action/tension B) Character reflection/interiority C) World/setting establishment D) Dialogue/interaction E) Time skip from previous chapter F) Other (describe)

2. CORE SCENES What must happen in this chapter? (Select all that apply) A) [Beat-specific requirement from Crucible] B) [Beat-specific requirement] C) Foreshadowing plant for [future payoff] D) Character development moment E) World-building revelation F) Other (describe)

3. CHAPTER TURN How does this chapter end? A) Cliffhanger — immediate tension B) Revelation — new information changes everything C) Decision point — character commits to action D) Emotional beat — feeling resonates into next chapter E) Question raised — reader needs to know what's next F) Other (describe)


### Scene-Level Detail

For each scene within a chapter:

SCENE [X.Y]

Goal: What must this scene accomplish? Conflict: What opposes the goal? Disaster/Turn: How does it shift?

Characters present: Location: Tone/Mood: Key dialogue/moments: Plants/Payoffs: - Sets up: [future scene] - Pays off: [previous setup]


### Save Progress After Each Chapter

python scripts/save_outline.py "./outline-project"


## Phase 4: Narrative Craft Layer

After completing chapter skeletons, add craft elements:

### Foreshadowing Threads

Using `references/narrative-craft.md`, track:

FORESHADOWING TRACKER

Thread: [Description] ├── Plant: Chapter [X], Scene [Y] — [How it's planted] ├── Water: Chapter [X] — [How it's reinforced] └── Payoff: Chapter [X], Scene [Y] — [How it resolves]


Required threads for Crucible stories:

1. Mercy → Unexpected Agents (each mercy must plant, payoff in finale)
2. Dark Mirror reveals (antagonist philosophy shown before confrontation)
3. Fire mastery path (surrender lesson foreshadowed before mastery moment)
4. Constellation fracture/repair (betrayal foreshadowed, bond-holds foreshadowed)

### Pacing Verification

Check chapter-by-chapter:

- Tension curve (rising overall with valleys for rest)
- Strand rotation (no strand absent 3+ chapters)
- Emotional variety (not all dark, not all light)

### Verify Forge Points

Each Forge Point chapter must have:

- All three strands in crisis
- Clear sacrifice made
- Irreversible change
- Forward momentum into next movement

## Phase 5: Compile

### Generate Outline Documents

python scripts/compile_outline.py "./outline-project"


Creates:

outline/ ├── master-outline.md # Full book outline ├── chapter-summaries.md # Quick reference ├── scene-breakdown.md # Detailed scene list ├── foreshadowing-tracker.md # Plant/payoff tracking ├── character-threads.md # Per-character arcs └── by-chapter/ ├── ch01-outline.md ├── ch02-outline.md └── ...


### Present to User

Outline Complete: [Title]

📄 View Master Outline 📄 View Chapter Summaries 📄 View Scene Breakdown 📄 View Foreshadowing Tracker

Use AskUserQuestion for next steps:

{
  "questions": [
    {
      "header": "Next Steps",
      "question": "What would you like to do next?",
      "options": [
        {"label": "Review chapters", "description": "Review and adjust specific chapters"},
        {"label": "Outline next book", "description": "Continue to next book in series"},
        {"label": "Begin drafting", "description": "Start writing prose from this outline"},
        {"label": "Add scene detail", "description": "Expand detail on specific scenes"}
      ],
      "multiSelect": false
    }
  ]
}

Multi-Book Series Handling

For series, outline books in order. Track:

Cross-Book Elements:

  • Mercy plants in Book X → Payoffs in Book Y
  • Character arcs spanning multiple books
  • Foreshadowing threads that span books
  • Series-level pacing (which book is darkest, etc.)

Before outlining Book 2+, request:

  • Previous book outline(s)
  • Updated character states
  • Unresolved threads list

Questioning Principles

  1. Max 2-3 questions per message — Don't overwhelm
  2. Always offer "Other" option — User knows their story
  3. Reference their documents — Use their character names, places, elements
  4. Explain the "why" — Brief context for why this choice matters
  5. Save state frequently — After each chapter or major decision

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.04%
按下载量换算22

Claude

29.29%
按下载量换算18

Cursor

18.63%
按下载量换算12

Gemini CLI

9.48%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills