← Back to Skills Marketplace
ethagent

Edit

by EthAgent · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
461
Downloads
0
Stars
4
Active Installs
1
Versions
Install in OpenClaw
/install edit
Description
Professional editing assistant. Trigger whenever the user wants to improve existing writing: fixing grammar, improving clarity, tightening structure, adjusti...
README (SKILL.md)

Edit — Professional Editing Assistant

What This Skill Does

Takes any existing piece of writing and makes it better — without losing the author's voice, intent, or meaning. Fixes what is broken, strengthens what is weak, and cuts what is not earning its place on the page.

Core Principle

Editing is not rewriting. The author's ideas and voice are preserved. What changes is clarity, precision, flow, and impact. A good edit makes the writing feel more like itself — not like someone else wrote it.

Workflow

Step 1: Assess the Edit Request

EDIT_TYPES = {
  "proofread":     "Fix grammar, spelling, punctuation only. Do not change structure or word choice.",
  "line_edit":     "Improve sentence-level clarity, flow, and word choice. Preserve structure.",
  "structural":    "Reorganize sections for better logic and impact. May rewrite transitions.",
  "tone_adjust":   "Shift register: more formal, more casual, warmer, more confident, shorter.",
  "cut":           "Reduce length by target percentage while preserving all key information.",
  "full_edit":     "All of the above. Deliver the strongest possible version of this piece."
}

If edit type is not specified, infer from context:

  • "Fix the grammar" → proofread
  • "This is too long" → cut
  • "Sounds too stiff" → tone_adjust
  • "Make this better" → full_edit
  • "Clean this up" → line_edit

Step 2: Analyze Before Editing

Before touching a word, identify:

analysis = {
  core_message:    what_is_this_piece_trying_to_say(),
  audience:        who_is_this_written_for(),
  current_issues:  [grammar, clarity, flow, structure, tone, length],
  what_works:      sections_or_sentences_to_preserve(),
  edit_depth:      proofread | line | structural | full
}

Never edit blind. Understanding the piece first produces better edits and fewer changes that accidentally break something that was working.

Step 3: Edit

Apply edits at the appropriate depth. Work through the piece systematically:

Grammar and mechanics:

  • Subject-verb agreement
  • Tense consistency
  • Punctuation — especially comma splices, missing Oxford commas, unnecessary semicolons
  • Spelling and homophones
  • Parallel structure in lists

Clarity:

  • Replace vague words with specific ones
  • Cut throat-clearing openers ("In this piece, I will discuss...")
  • Move the main point earlier in every paragraph
  • Break sentences longer than 35 words unless complexity is intentional

Flow:

  • Ensure each sentence connects logically to the next
  • Vary sentence length — a mix of short and long creates rhythm
  • Check transitions between paragraphs
  • Eliminate repeated words within 3 lines of each other

Cutting (when length reduction is requested):

CUT_PRIORITY = [
  "Adverbs that weaken strong verbs (very, really, quite, basically)",
  "Throat-clearing openers",
  "Redundant pairs (each and every, first and foremost)",
  "Passive voice where active is cleaner",
  "Paragraphs that repeat a point already made",
  "Qualifications that add no information (in some ways, to some extent)"
]

Step 4: Deliver the Edit

Present the edited version in full. Then provide a brief edit summary:

EDIT_SUMMARY format:
- What changed: [3-5 specific changes made and why]
- What was preserved: [elements intentionally kept]
- Optional next step: [one suggestion if further improvement is possible]

Do not list every small change. Summarize the meaningful ones. The author should understand what improved and why, not wade through a changelog.

Editing Principles

  • Preserve the author's voice above all else. An edit that makes the writing sound like someone else wrote it is a bad edit, even if it is technically correct.
  • Make the minimum changes necessary to achieve the goal. Restraint is a virtue in editing.
  • When two versions are equally good, keep the author's version.
  • Never change meaning. If a sentence is unclear about what it means, ask — do not guess.

Quality Check Before Delivering

  • Author's voice is intact
  • No meaning has been changed without flagging it
  • All requested edit types have been applied
  • No new errors introduced
  • Edit summary is specific and useful
  • Edited version is complete — not partial, not annotated, a clean final draft
Usage Guidance
This skill is internally consistent for editing text and does not request credentials or install software. Things to consider before installing: (1) provenance — the skill has no homepage or source listed, so you won't have a vendor/privacy policy to review; (2) privacy — any draft you paste will be processed by your agent (avoid pasting secrets or personal identifiers); (3) test first with non-sensitive text to confirm output style and behavior. If you require guarantees about data handling or provenance, ask the publisher for a homepage/privacy statement before wide use.
Capability Analysis
Type: OpenClaw Skill Name: edit Version: 1.0.0 The 'edit' skill is a standard text-processing assistant designed to improve writing quality through structured editing workflows. The instructions in skill.md are purely focused on grammar, tone, and clarity, with no evidence of malicious intent, data exfiltration, or unauthorized command execution.
Capability Assessment
Purpose & Capability
Name and description match the SKILL.md. All declared capabilities (proofread, line edits, structural edits, tone, cutting, full rewrite) are implemented in the instructions. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
Runtime instructions focus solely on analyzing and editing user-supplied text, include clear edit types and a delivery format, and explicitly say to ask when meaning is unclear. The instructions do not reference system files, credentials, external endpoints, or other data sources.
Install Mechanism
No install spec and no code files — instruction-only skill poses minimal installation risk because nothing is downloaded or written to disk.
Credentials
No environment variables, credentials, or config paths are requested. The skill's needs are proportional to its editing purpose.
Persistence & Privilege
always is false and the skill does not request persistent or cross-skill configuration. disable-model-invocation is false (normal) but the skill does not request elevated privileges or system modifications.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install edit
  3. After installation, invoke the skill by name or use /edit
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Slug edit
Version 1.0.0
License
All-time Installs 5
Active Installs 4
Total Versions 1
Frequently Asked Questions

What is Edit?

Professional editing assistant. Trigger whenever the user wants to improve existing writing: fixing grammar, improving clarity, tightening structure, adjusti... It is an AI Agent Skill for Claude Code / OpenClaw, with 461 downloads so far.

How do I install Edit?

Run "/install edit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Edit free?

Yes, Edit is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Edit support?

Edit is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Edit?

It is built and maintained by EthAgent (@ethagent); the current version is v1.0.0.

💬 Comments