How do I install the Edit skill?

Run npx skillmds@latest add majiayu000/edit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Edit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Edit by majiayu000 — Agent Skill

Name: Edit
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Run the editor agent to polish your manuscript at the line level.

What This Does

Processes chapters looking for mechanical issues
Flags spelling, grammar, awkward phrasing, word echoes
Identifies manuscript-wide patterns (overused words, crutch phrases)
Offers to apply mechanical fixes automatically
Updates progress.md with findings

Usage

/fiction:edit                    # Edit most recent chapter
/fiction:edit 5                  # Edit chapter 5
/fiction:edit all                # Edit all drafted chapters
/fiction:edit 3-7                # Edit chapters 3 through 7

If arguments provided: $ARGUMENTS

Parallel Processing (Important for Large Manuscripts)

When editing multiple chapters ("all" or a range), spawn editor agents in parallel for efficiency:

Identify all chapters to process
Launch one editor agent per chapter simultaneously using the Task tool
Each agent processes its chapter independently
After all complete, aggregate manuscript-wide patterns from all reports
Update progress.md with combined findings

Example parallel approach for /fiction:edit all with 20 chapters:

Spawn 20 editor agents in a single message (one Task call per chapter)
Agents run concurrently, each producing its own report
Main conversation aggregates: common crutch words, repeated issues across chapters
Total time ~ time for 1 chapter instead of 20x

What It Catches

Spelling & typos — Including wrong-word errors (their/there)
Grammar — Agreement, punctuation, comma splices
Awkward phrasing — Confusing syntax, unclear references
Word echoes — Repetition in close proximity
Overused words — Filter words, weak verbs, crutch words
Formatting — Inconsistent dashes, ellipses, quotes

Output

A report per chapter with:

Issues by category with line numbers
Suggested fixes
Manuscript-wide patterns (when editing multiple chapters)

When to Use

After completing a chapter draft
Before sending to beta readers
During revision passes
After /fiction:review addresses story issues

Workflow

Recommended order for polishing:

/fiction:review — Fix story/craft issues first
/fiction:edit — Then line-level polish
continuity agent — Check cross-chapter consistency
/fiction:critique — Final literary assessment (if complete)

Related Commands

/fiction:review — Story and craft feedback (run first)
/fiction:critique — Full manuscript literary review
/fiction:reconcile — Project structure audit

---name: editdescription: Run line-level editing across chapters. Catches spelling, grammar, awkward phrasing, and word echoes.--- Run the editor agent to polish your manuscript at the line level. ## What This Does 1. Processes chapters looking for mechanical issues 2. Flags spelling, grammar, awkward phrasing, word echoes 3. Identifies manuscript-wide patterns (overused words, crutch phrases) 4. Offers to apply mechanical fixes automatically 5. Updates `progress.md` with findings ## Usage ``` /fiction:edit # Edit most recent chapter /fiction:edit 5 # Edit chapter 5 /fiction:edit all # Edit all drafted chapters /fiction:edit 3-7 # Edit chapters 3 through 7 ``` If arguments provided: $ARGUMENTS ## Parallel Processing (Important for Large Manuscripts) When editing multiple chapters ("all" or a range), **spawn editor agents in parallel** for efficiency: 1. Identify all chapters to process 2. Launch one editor agent per chapter simultaneously using the Task tool 3. Each agent processes its chapter independently 4. After all complete, aggregate manuscript-wide patterns from all reports 5. Update `progress.md` with combined findings **Example parallel approach for `/fiction:edit all` with 20 chapters:** - Spawn 20 editor agents in a single message (one Task call per chapter) - Agents run concurrently, each producing its own report - Main conversation aggregates: common crutch words, repeated issues across chapters - Total time ~ time for 1 chapter instead of 20x ## What It Catches - **Spelling & typos** — Including wrong-word errors (their/there) - **Grammar** — Agreement, punctuation, comma splices - **Awkward phrasing** — Confusing syntax, unclear references - **Word echoes** — Repetition in close proximity - **Overused words** — Filter words, weak verbs, crutch words - **Formatting** — Inconsistent dashes, ellipses, quotes ## Output A report per chapter with: - Issues by category with line numbers - Suggested fixes - Manuscript-wide patterns (when editing multiple chapters) ## When to Use - After completing a chapter draft - Before sending to beta readers - During revision passes - After `/fiction:review` addresses story issues ## Workflow Recommended order for polishing: 1. `/fiction:review` — Fix story/craft issues first 2. `/fiction:edit` — Then line-level polish 3. `continuity` agent — Check cross-chapter consistency 4. `/fiction:critique` — Final literary assessment (if complete) ## Related Commands - `/fiction:review` — Story and craft feedback (run first) - `/fiction:critique` — Full manuscript literary review - `/fiction:reconcile` — Project structure audit

Frequently asked questions

Edit