mcpField
R
red-pen

red-pen

github.com/borkwebDocuments858 installsUpdated 2d ago
Repository

About red-pen

Red Pen is an editorial skill for reviewing and revising prose while preserving the author's meaning, voice, and factual claims. It supports review-only, batched revisions, and interactive editing without publishing or sending text.

Key features

  1. 01Review clarity, economy, and typography
  2. 02Offer review-only or revision modes
  3. 03Preserve meaning, voice, and claims
  4. 04Make scoped prose edits
  5. 05Keep quotations and literal strings exact

Use cases

  1. 01Review a draft for clarity and concision
  2. 02Apply approved prose edits to a file
  3. 03Edit text while preserving its format

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/borkweb/skills --skill red-pen

After installing, type/red-penin Claude Code to confirm it loaded.

Details

From the project README

Red Pen

Review prose for clarity, economy and appropriate typography. Use the requested mode: review-only (default), batched revision or interactive editing. A request to edit a file authorizes scoped prose edits; preserve its format and non-prose structure. Do not publish or send the text.

Editorial judgment

Read the whole piece before suggesting local changes. Keep the author's meaning, voice, claims, uncertainty and necessary technical vocabulary. Direct quotations, code, URLs, numbers and literal strings stay exact. Add no facts, advice, citations or personal experiences.

Look for dead metaphors, inflated words, filler, unclear subjects, passive constructions that hide responsibility, repetitive sentence patterns and theatrical setup sentences. Do not flag an intentional choice that serves the writing. Style patterns are not proof of AI authorship. A passage that works needs no change.

Use typography appropriate to the output medium and existing house style. Straight quotes in source/plain text and curly quotes in typeset prose can both be valid. Preserve quoted content. Check spacing, dashes, apostrophes, ellipses and emphasis for clarity rather than applying a universal substitution rule.

Output and interaction

For review-only, give concise numbered findings with a short identifying quotation, the specific problem and a suggested correction. Group by language or typography only when useful. No issue quota or mandatory overall praise.

For batched revision, apply the authorized corrections, compare the result to the source for factual or structural losses, then return the revised text or file link. Ask only for consequential unresolved choices; do not force an issue-by-issue approval loop.

Use one-at-a-time editing only when requested. Offer keep, one or two meaningfully distinct rewrites, and a custom replacement. Carry each choice forward, honor stop immediately, and return the accepted revisions. Do not reinterpret unrelated user steering as replacement prose.

Aim for shorter, clearer writing; factual preservation outranks a length target. Follow the same typography policy as humanize so sequential editing does not flip styles back and forth.

Comments

Markdown supported