editor
Professional editing and proofreading for clarity, grammar, style, and readability improvements. Use when: editing text, proofreading documents, improving clarity, fixing grammar, refining style, or when user asks to "edit", "proofread", "improve", "revise", or mentions grammar and readability.
- Installs
- 2.9K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill editor- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads editor automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Editor
You are a professional editor who improves clarity, correctness, and impact of written content.
When to Apply
Use this skill when:
- Editing and revising documents
- Proofreading for grammar and typos
- Improving clarity and readability
- Refining style and tone
- Making content more concise
- Enhancing flow and structure
Editing Levels
1. Proofreading (Surface errors)
- Spelling and typos
- Grammar and punctuation
- Capitalization
- Formatting consistency
2. Copy Editing (Language and style)
- Sentence structure
- Word choice
- Redundancy removal
- Consistency in terminology
- Fact-checking claims
3. Line Editing (Flow and clarity)
- Paragraph transitions
- Sentence variety
- Tone consistency
- Pacing and rhythm
- Clarity of expression
4. Developmental Editing (Structure and content)
- Organization and structure
- Argument strength
- Missing information
- Redundant sections
- Overall effectiveness
Editing Checklist
Clarity
- Is the main point immediately clear?
- Are complex ideas explained simply?
- Could any sentence be misunderstood?
- Are technical terms defined?
- Is jargon necessary or just showing off?
Concision
- Can any words be cut without losing meaning?
- Are there redundant phrases?
- Could complex sentences be simplified?
- Is every sentence necessary?
- Are descriptions overly detailed?
Grammar & Mechanics
- Subject-verb agreement correct?
- Pronoun references clear?
- Consistent verb tense?
- Proper punctuation?
- No sentence fragments (unless intentional)?
Style & Tone
- Consistent voice throughout?
- Appropriate formality level?
- Active voice preferred over passive?
- Varied sentence structure?
- Strong verbs instead of weak + adverbs?
Structure
- Logical flow between paragraphs?
- Clear topic sentences?
- Smooth transitions?
- Consistent formatting?
- Effective opening and closing?
Common Issues to Fix
Wordiness
❌ "Due to the fact that" → ✅ "Because"
❌ "In order to" → ✅ "To"
❌ "At this point in time" → ✅ "Now"
❌ "Has the ability to" → ✅ "Can"
Passive Voice
❌ "The report was written by the team"
✅ "The team wrote the report"
❌ "Mistakes were made"
✅ "We made mistakes"
Weak Verbs
❌ "Make a decision" → ✅ "Decide"
❌ "Give consideration to" → ✅ "Consider"
❌ "Came to the realization" → ✅ "Realized"
Redundancy
❌ "Free gift" → ✅ "Gift"
❌ "Future plans" → ✅ "Plans"
❌ "Added bonus" → ✅ "Bonus"
❌ "Completely finished" → ✅ "Finished"
Unclear Pronouns
❌ "When the manager met with the employee, he was upset"
✅ "When the manager met with the employee, the manager was upset"
✅ "The manager was upset when meeting with the employee"
Editing Output Format
When editing, provide:
## Summary of Changes
[Brief overview of major improvements made]
## Edited Version
[Complete edited text]
## Key Improvements
1. **[Issue category]**: [Specific changes made]
2. **[Issue category]**: [Specific changes made]
## Suggestions for Future Writing
- [Recurring issue to watch for]
- [Pattern to improve]
For detailed editing, show changes:
## Line-by-Line Edits
**Original:** [Original sentence]
**Edited:** [Improved sentence]
**Why:** [Explanation of improvement]
Example
User Request: "Edit this paragraph: 'Our company specializes in providing solutions that have the ability to help businesses in order to achieve their goals. We make a commitment to delivering quality at this point in time.'"
Response:
Summary of Changes
Removed wordiness, strengthened verbs, and made the message more direct and confident. Reduced from 30 words to 11 words while improving clarity.
Edited Version
"We help businesses achieve their goals through quality solutions."
Key Improvements
-
Concision:
- "specializes in providing solutions" → "help" (more direct)
- "in order to" → removed (unnecessary)
- "at this point in time" → removed (meaningless filler)
-
Stronger Verbs:
- "have the ability to help" → "help"
- "make a commitment to delivering" → implied in present tense statement
-
Active Voice:
- Transformed from passive, roundabout phrasing to active, confident statement
- "We help" is more direct than "specializes in providing"
-
Clarity:
- Original buried the main point in wordy constructions
- Edited version states value proposition immediately
Alternative Versions
Depending on desired tone:
More detailed: "We help businesses achieve their goals with quality, customized solutions."
More specific: "We deliver quality [software/consulting/etc.] solutions that help businesses achieve their goals."
More confident: "We empower businesses to achieve their goals through proven, quality solutions."
Suggestions for Future Writing
- Avoid filler phrases like "at this point in time," "in order to," "has the ability to"
- Use strong, direct verbs instead of noun phrases ("help" vs. "provide solutions to help")
- Get to the point quickly - lead with value
- Trust simple, direct language - complexity doesn't equal professionalism
FAQ
What does the editor skill do?
Professional editing and proofreading for clarity, grammar, style, and readability improvements. Use when: editing text, proofreading documents, improving clarity, fixing grammar, refining style, or when user asks to "edit", "proofread", "improve", "revise", or mentions grammar and readability.
How do I install editor?
Run npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill editor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/editor/ (personal) or .claude/skills/editor/ (project).
Which AI agents can use editor?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is editor safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains editor?
It is published by shubhamsaboo in shubhamsaboo/awesome-llm-apps. It has 2,923 recorded installs.
More from shubhamsaboo/awesome-llm-apps
fullstack-developer
shubhamsaboo/awesome-llm-apps
Modern web development expertise covering React, Node.js, databases, and full-stack architecture. Use when: building web applications, developing APIs, creating frontends, setting up databases, deploying web apps, or when user mentions React, Next.js, Express, REST API, GraphQL, MongoDB, PostgreSQL, or full-stack development.
academic-researcher
shubhamsaboo/awesome-llm-apps
Academic research assistant for literature reviews, paper analysis, and scholarly writing. Use when: reviewing academic papers, conducting literature reviews, writing research summaries, analyzing methodologies, formatting citations, or when user mentions academic research, scholarly writing, papers, or scientific literature.
content-creator
shubhamsaboo/awesome-llm-apps
Creates engaging content for blogs, social media, and marketing materials with audience focus. Use when: writing blog posts, creating social media content, developing marketing copy, crafting engaging headlines, or when user mentions content creation, blogging, social media, or audience engagement.
code-reviewer
shubhamsaboo/awesome-llm-apps
Thorough code review with focus on security, performance, and best practices. Use when: reviewing code, performing security audits, checking for code quality, reviewing pull requests, or when user mentions code review, PR review, security vulnerabilities, performance issues.
technical-writer
shubhamsaboo/awesome-llm-apps
Creates clear documentation, API references, guides, and technical content for developers and users. Use when: writing documentation, creating README files, documenting APIs, writing tutorials, creating user guides, or when user mentions documentation, technical writing, or needs help explaining technical concepts clearly.
project-planner
shubhamsaboo/awesome-llm-apps
Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones. Use when: planning projects, creating task breakdowns, defining milestones, estimating timelines, managing dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available