Token导航 LogoToken导航

Agent Skill · 待分类

crucible-editor(坩埚编辑器)

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

crucible-editor 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 6,894。

总安装 412周安装 17GitHub Stars 48下载 135核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

crucible-editor 为 Crucible 小说写作系统提供四阶编辑支持:发展性、语句级、校对与润色。适用于长篇叙事作品的结构优化、语言精炼与风格统一,严格遵循预设大纲不可越界。每个编辑阶段对应特定检查清单与参考模板,确保专业级文本质量与一致性。

使用前需完整导入规划文档,否则可能因缺乏上下文导致偏离作者原始意图。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

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-editor 怎么安装?

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

crucible-editor 支持哪些 AI 工具?

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

crucible-editor 需要什么权限?

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

crucible-editor 是免费的吗?

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

crucible-editor 用的人多吗?

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

crucible-editor 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
crucible-editor

坩埚编辑器 · 本页

41248只读未明确通过

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

SKILL.md 原文

Crucible Editor

Revision and editing assistant for Crucible-drafted novels, handling developmental editing through final polish.

Overview

The Crucible Editor provides structured editing support at four levels:

  1. Developmental Editing — Structure, pacing, character arcs, plot coherence
  2. Line Editing — Scene-level prose improvement, voice consistency
  3. Copy Editing — Grammar, consistency, style guide adherence
  4. Final Polish — Micro-level refinement, word choice, rhythm

Before Starting

Read these references based on editing phase:

  • references/developmental-checklist.md — Structure and story issues
  • references/line-editing-guide.md — Prose improvement techniques
  • references/copy-editing-standards.md — Grammar and style rules
  • references/polish-techniques.md — Final refinement methods

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 specific issues by location (chapter, scene, paragraph)
  5. Batch similar decisions when possible

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

Required Inputs

Before editing can begin, gather:

  1. Draft Chapter(s) (required) — The crucible-writer output to edit
  2. Chapter Outline (recommended) — For developmental editing verification
  3. Style Profile (recommended) — For voice consistency checking
  4. Story Bible (as needed) — For continuity verification
  5. Review Reports (if available) — From bi-chapter review agents

Workflow

Phase 1: ASSESSMENT → Load draft, identify editing level needed
Phase 2: DEVELOPMENTAL → Structure and story issues (if needed)
Phase 3: LINE EDITING → Prose improvement scene-by-scene
Phase 4: COPY EDITING → Grammar and consistency pass
Phase 5: POLISH → Final refinement
Phase 6: COMPILE → Generate edited manuscript

Phase 1: Assessment

Load Draft Material

Request the draft material:

To begin editing, I need:

1. **The chapter(s) to edit** — paste or specify file location
2. **Any specific concerns?** (Optional)
   - Areas you feel need work
   - Feedback from readers/critique partners
   - Issues flagged in bi-chapter reviews

Then use AskUserQuestion for editing scope:

{
  "questions": [
    {
      "header": "Edit Scope",
      "question": "What level of editing do you want?",
      "options": [
        {"label": "Full edit", "description": "All levels: developmental, line, copy, and polish"},
        {"label": "Developmental only", "description": "Structure, pacing, character arcs, plot coherence"},
        {"label": "Line editing only", "description": "Scene-level prose improvement, voice consistency"},
        {"label": "Copy/Polish only", "description": "Grammar, consistency, final refinement"}
      ],
      "multiSelect": false
    }
  ]
}

Initial Assessment

After loading, provide:

**EDITING ASSESSMENT: Chapter [X]**

Word Count: [X,XXX]
Overall Quality: [Draft/Rough/Polished]

**Developmental Issues Found:**
- [ ] None / [List specific issues]

**Line Editing Needs:**
- [ ] Minimal / Moderate / Significant

**Copy Editing Level:**
- [ ] Clean / Some errors / Needs attention

**Recommended Editing Path:**
[Specific recommendation based on assessment]

Use AskUserQuestion:

{
  "questions": [
    {
      "header": "Edit Path",
      "question": "How would you like to proceed?",
      "options": [
        {"label": "Recommended path", "description": "Follow the suggested editing sequence"},
        {"label": "Specific level", "description": "Focus on one particular editing level"},
        {"label": "Discuss first", "description": "Talk through the issues before deciding"}
      ],
      "multiSelect": false
    }
  ]
}

Phase 2: Developmental Editing

Focus: Structure, story, character, pacing

Structural Checks

Verify against outline (if available):

  • All required scenes present
  • Scene order makes sense
  • No unplanned additions that derail structure
  • Chapter accomplishes its story purpose

Character Arc Verification

  • Character motivations clear
  • Emotional beats land
  • Character voice consistent
  • Relationship dynamics accurate

Pacing Analysis

**PACING REPORT: Chapter [X]**

Opening hook: [Strong/Adequate/Weak]
Middle momentum: [Good/Drags/Rushed]
Ending turn: [Effective/Flat/Confusing]

Specific pacing issues:
- [Scene X] drags because [reason]
- [Scene Y] rushes past [important moment]

Recommendations:
1. [Specific structural change]
2. [Specific pacing adjustment]

Developmental Fixes

For each issue identified:

**DEVELOPMENTAL FIX [X]**

Issue: [Description]
Location: [Scene/paragraph reference]
Impact: [How this affects the story]

Proposed fix:
[Specific change or rewrite recommendation]

Use AskUserQuestion:

{
  "questions": [
    {
      "header": "Fix",
      "question": "How would you like to handle this developmental issue?",
      "options": [
        {"label": "Apply fix", "description": "Implement the proposed change"},
        {"label": "Skip", "description": "Will address differently or later"},
        {"label": "Discuss", "description": "Talk through the approach first"}
      ],
      "multiSelect": false
    }
  ]
}

Phase 3: Line Editing

Focus: Prose quality scene-by-scene

Scene-by-Scene Analysis

For each scene, check:

  • Clarity — Is meaning clear on first read?
  • Economy — Any wasted words or repetition?
  • Voice — Does it match the style profile?
  • Sensory Detail — Appropriate level for scene type
  • Dialogue — Natural, distinct voices, effective tags

Line Editing Report Format

**LINE EDIT: Scene [X.Y]**

Strengths:
- [What's working well]

Issues Found:
1. [Issue type]: "[specific passage]" — [explanation]
2. [Issue type]: "[specific passage]" — [explanation]

Suggested Revisions:
[Show original vs revised for key passages]

Use AskUserQuestion:

{
  "questions": [
    {
      "header": "Revisions",
      "question": "How would you like to handle these line edits?",
      "options": [
        {"label": "Accept all", "description": "Apply all suggested revisions"},
        {"label": "Review each", "description": "Go through revisions one by one"},
        {"label": "Skip scene", "description": "Move to the next scene"}
      ],
      "multiSelect": false
    }
  ]
}

Common Line Edit Categories

  • Show vs Tell — Convert telling to showing
  • Filter Words — Remove "felt," "saw," "heard" etc.
  • Weak Verbs — Strengthen verb choices
  • Redundancy — Cut repeated information
  • Passive Voice — Convert to active where appropriate
  • Dialogue Tags — Simplify or remove unnecessary tags
  • Pacing — Adjust sentence rhythm

Phase 4: Copy Editing

Focus: Grammar, consistency, style

Grammar Check

  • Sentence structure
  • Subject-verb agreement
  • Tense consistency
  • Pronoun clarity
  • Punctuation

Consistency Check

  • Character name spellings
  • Place name spellings
  • Magic/world terminology
  • Timeline references
  • Physical descriptions match story bible

Style Adherence

  • Point of view consistency
  • Narrative distance consistent
  • Dialogue formatting
  • Scene break formatting

Copy Edit Report

**COPY EDIT REPORT: Chapter [X]**

Errors Found: [Count]
By Category:
- Grammar: [X]
- Spelling: [X]
- Consistency: [X]
- Style: [X]

Critical Fixes (must address):
1. [Issue with correction]

Minor Fixes (recommended):
1. [Issue with correction]

Use AskUserQuestion:

{
  "questions": [
    {
      "header": "Copy Fixes",
      "question": "How would you like to handle these copy edits?",
      "options": [
        {"label": "Apply all", "description": "Apply all fixes (critical and minor)"},
        {"label": "Critical only", "description": "Apply only critical fixes"},
        {"label": "Review each", "description": "Go through fixes one by one"}
      ],
      "multiSelect": false
    }
  ]
}

Phase 5: Polish

Focus: Final refinement, micro-level improvements

Polish Checklist

  • Opening sentence hooks reader
  • Closing sentence creates forward momentum
  • Paragraph transitions smooth
  • Sentence variety (length, structure)
  • Word choice precise
  • Rhythm supports content

Polish Techniques

Sentence Rhythm:

  • Vary length: Short. Then longer, more complex structures.
  • Match rhythm to action: Quick sentences for action, flowing for reflection
  • Use fragments intentionally for impact

Word Choice:

  • Specific over generic (not "tree" but "oak")
  • Strong verbs over adverb+verb
  • Sensory words for immersion
  • Period-appropriate for setting

Micro-Pacing:

  • White space for emphasis
  • Paragraph breaks for beats
  • Sentence breaks for tension

Editing Principles

The Three Laws of Editing

  1. Preserve Voice — Improve prose without changing the author's voice
  2. Serve Story — Every edit should make the story clearer/stronger
  3. Respect Intent — Ask before making significant changes

When to Ask the Author

  • Major structural changes
  • Cutting scenes or characters
  • Adding new material
  • Changing plot points
  • Ambiguous passages

Track Changes Protocol

For significant edits:

**EDIT PROPOSAL**

Original:
"[Original text]"

Proposed:
"[Edited text]"

Reason: [Why this improves the passage]

Use AskUserQuestion:

{
  "questions": [
    {
      "header": "Edit",
      "question": "Accept this edit proposal?",
      "options": [
        {"label": "Accept", "description": "Apply the proposed change"},
        {"label": "Reject", "description": "Keep the original text"},
        {"label": "Modify", "description": "Adjust the proposed change"}
      ],
      "multiSelect": false
    }
  ]
}

Output Formats

Per-Chapter Edit Summary

**EDIT COMPLETE: Chapter [X]**

Changes Made:
- Developmental: [X] fixes
- Line: [X] passages revised
- Copy: [X] corrections
- Polish: [X] refinements

Word Count Change: [+/-X words]

Major Improvements:
1. [Description]
2. [Description]

Use AskUserQuestion:

{
  "questions": [
    {
      "header": "Chapter Done",
      "question": "How would you like to proceed?",
      "options": [
        {"label": "Save & continue", "description": "Save chapter and proceed to next"},
        {"label": "Review changes", "description": "Review the changes in detail"},
        {"label": "Revert changes", "description": "Undo specific changes"}
      ],
      "multiSelect": false
    }
  ]
}

Full Manuscript Edit Report

**EDITING COMPLETE: [Title]**

Chapters Edited: [X of Y]
Total Word Count: [Before] → [After]

Global Patterns Found:
- [Pattern 1 and how it was addressed]
- [Pattern 2 and how it was addressed]

Remaining Concerns:
- [Any issues that need author decision]

Deliverables:
- edited-manuscript.md (full edited text)
- edit-report.md (detailed change log)
- continuity-notes.md (issues found for story bible)

Progress Checklist

Copy this checklist to track editing progress:

Editing Progress:
- [ ] Step 1: Assessment complete
- [ ] Step 2: Developmental editing (if needed)
- [ ] Step 3: Line editing pass
- [ ] Step 4: Copy editing pass
- [ ] Step 5: Polish pass
- [ ] Step 6: Final review and compile

Integration with Review Agents

If bi-chapter review reports are available, prioritize:

  1. voice-checker findings → Line editing phase
  2. continuity-checker findings → Copy editing phase
  3. outline-checker findings → Developmental phase
  4. timeline-checker findings → Copy editing phase
  5. prose-checker findings → Line editing and polish phases

Bundled Resources

references/

  • developmental-checklist.md — Full developmental editing guide
  • line-editing-guide.md — Prose improvement techniques
  • copy-editing-standards.md — Grammar and style rules
  • polish-techniques.md — Final refinement methods

scripts/

  • init_edit.py — Initialize editing project
  • save_edit.py — Save editing progress
  • compile_edited.py — Generate final manuscript
  • diff_report.py — Generate change report

平台分布

Codex

38.58%
按下载量换算52

Claude

29.04%
按下载量换算39

Cursor

18.7%
按下载量换算25

Gemini CLI

10.91%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills