agentleFS
Sign inStart free
PingPingEPingPingE/ai-content-agents/.claude/skills/edit-content/SKILL.md

edit-content

Skill2 starsChanged 9 months agoMITView on GitHub

Polish content for style and clarity

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. anshul-garg27/claude-enhancement-suite★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure smooth flow and transitions

    line 24
  2. Distinctive:

    Don't add new content — only refine existing

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Edit Content

Polish the following content:

Target: $ARGUMENTS

Editing goals:

  1. Improve clarity and readability
  2. Cut unnecessary words (aim for 20% reduction)
  3. Ensure smooth flow and transitions
  4. Fix grammar and style inconsistencies
  5. Preserve the author's voice

Three Editing Passes

Pass 1: Structure (Developmental Edit)

  • Is the organization logical?
  • Do paragraphs flow in a coherent sequence?
  • Are headings descriptive and hierarchical?
  • Does the intro hook the reader?
  • Does the conclusion provide closure?

Action: Reorganize sections if needed, but don't change wording yet.

Pass 2: Clarity (Line Edit)

  • Cut weasel words: very, really, quite, rather, literally
  • Replace passive voice with active voice
  • Simplify long sentences (aim for 15-20 words average)
  • Remove filler phrases: "in order to" → "to", "due to the fact that" → "because"
  • Replace abstractions with concrete examples

Action: Rewrite sentences for maximum clarity and impact.

Pass 3: Grammar (Copy Edit)

  • Fix spelling, punctuation, grammar errors
  • Ensure consistent terminology
  • Check capitalization (API not Api)
  • Verify date/number formats are consistent
  • Confirm heading capitalization is uniform

Action: Final polish, no major rewrites.

Conciseness Target

Goal: 20% word reduction while preserving meaning

Phrases to Cut Without Mercy:

  • "in order to" → "to"
  • "due to the fact that" → "because"
  • "at this point in time" → "now"
  • "it is important to note that" → [delete]
  • "the reason why is that" → "because"
  • Redundant "that" in most cases

Before/After Example:

Before (42 words): "In order to improve the performance of your application, it is important to note that you should consider the fact that caching can be very helpful due to the fact that it reduces database queries."

After (16 words): "To improve application performance, use caching to reduce database queries."

Track Changes Summary

After editing, provide:

Edits Made

  • Word count: [before] → [after] ([X%] reduction)
  • Structure changes: [list major reorganizations]
  • Clarity improvements: [list key sentence rewrites]
  • Consistency fixes: [list terminology/formatting standardizations]

Author Voice Preservation Note

Describe how you maintained the author's unique style and tone.

Flagged Items

List any factual claims you're unsure about that need fact-checking.

Rules

  • Preserve the author's voice and intent
  • Don't add new content — only refine existing
  • Flag factual concerns, don't change facts
  • Aim for 20% word reduction
  • Make three complete passes (structure → clarity → grammar)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free