/edit

> Revise existing content for clarity, accuracy, and signal-to-noise ratio.

170 stars

Best use case

/edit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Revise existing content for clarity, accuracy, and signal-to-noise ratio.

Teams using /edit should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/edit/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/content/edit/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/edit/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How /edit Compares

Feature / Agent/editStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

> Revise existing content for clarity, accuracy, and signal-to-noise ratio.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /edit

> Revise existing content for clarity, accuracy, and signal-to-noise ratio.

## Usage
```
/edit <file> [--focus <clarity|accuracy|conciseness|tone>] [--for <person>]
```

## What It Does
Reads the target file, analyzes it against Signal Theory principles, and suggests or applies edits to maximize signal-to-noise ratio. Can focus on specific dimensions: clarity (remove ambiguity), accuracy (fact-check against knowledge base), conciseness (cut noise), or tone (match receiver).

## Implementation
1. **Read content** -- load the file.
2. **Analyze** -- score against the 6 encoding principles.
3. **Identify noise** -- filler, hedging, repetition, wrong structure.
4. **Suggest edits** -- specific before/after changes with rationale.
5. **Apply** (if confirmed) -- make the edits.
6. **Validate** -- re-score to confirm improvement.

## Examples
```bash
# Edit for overall quality
/edit docs/pitch-card.md

# Focus on conciseness
/edit docs/architecture/FULL-SYSTEM-ARCHITECTURE.md --focus conciseness

# Edit for a specific receiver
/edit outreach-email.md --for "Ed Honour"
```