Token导航 LogoToken导航

Agent Skill · 前端设计

crucible-outliner(坩埚轮廓线)

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

crucible-outliner 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 9,806。

总安装 194周安装 8GitHub Stars 48下载 63核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

crucible-outliner 将 Crucible 规划文档转化为详细的章节级叙事大纲,注重情节连贯性。适用于史诗奇幻类作品的蓝图展开,融合节拍映射与场景结构设计原则。严格遵循用户提问交互机制,每次最多四个选项与四次追问,确保控制权归属作者。

输出仅为结构框架,具体内容仍需人工填充,避免 AI 越俎代庖破坏创作主权。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/crucible-outliner

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/forsonny/the-crucible-writing-system-for-claud…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

crucible-outliner 怎么安装?

在终端执行 npx skills add https://github.com/forsonny/the-crucible-writing-system-for-claude --skill…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

crucible-outliner 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

crucible-outliner 需要什么权限?

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

crucible-outliner 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

crucible-outliner 用的人多吗?

公开数据是累计安装 194 次,近一周安装 8 次,下载 63 次,GitHub 48 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

crucible-outliner 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
crucible-outliner

坩埚轮廓线 · 本页

19448只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

平台分布

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