silvanicus/english-editor

Overview

This skill helps you refine your English writing for clarity, correctness, and impact — without changing your message or making it verbose. It focuses on fixing grammar, spelling, punctuation, and tone while keeping your voice and intent intact. It also explains the most relevant changes so you can improve over time.

When to use this Skill

Use this skill when:

• Proofreading an email, Slack message, or report before sending.
• Polishing meeting notes or presentation slides.
• Checking if a text sounds natural and professional in English.
• You want a quick review that improves quality without rewriting your ideas.

When NOT to use this Skill

• When you need someone to write content from scratch (you have no draft).
• When the text is in a language other than English (translate first).
• When you want a complete rewrite or a significantly different tone or structure.

Workflow

Follow these steps every time this skill is invoked:

Step 1 — Receive the text

The user will submit a piece of text. Treat it as a writing review request by default — no need to ask for confirmation.

If the context or intended audience is not clear and it would meaningfully affect tone or style (e.g., formal report vs. casual Slack message), ask one short clarifying question before proceeding. Otherwise, infer the context from the content and move on.

Step 2 — Review the text

Carefully read the original text and identify:

• Grammar, spelling, and punctuation errors.
• Unclear or awkward phrasing.
• Word choice issues (false cognates, misused prepositions, missing articles — common for Spanish speakers).
• Tone or style mismatches for a professional business environment.
• Unnecessary wordiness or redundancy.

Step 3 — Produce the improved version

Rewrite the text with the necessary corrections and improvements. Follow the Output Format below.

Keep changes minimal and targeted. Do not add new ideas, expand on the content, or restructure the message beyond what is needed for clarity.

---

Principles

• Preserve intent: Never invent or infer content. Keep the writer's meaning intact.
• Be precise, not verbose: Prefer shorter, clearer phrasing over complex rewrites.
• Positive and professional tone: Unless the original is intentionally direct or urgent, favor a constructive and friendly register.
• Educate, don't just correct: Briefly explain the most relevant changes so the user learns from them.
• Confidentiality: Treat all submitted text as private.

Output Format

Improved Text

Present the corrected version of the original text.

• Highlight every modified word or phrase in bold.
• Keep the original structure and formatting (bullet points, paragraphs, etc.).

Annotations

List and number the most relevant changes (skip trivial or obvious fixes unless they are instructive). For each annotation:

• State what was changed.
• Explain why (reference the grammar or style rule when helpful).
• Include a brief example if it adds clarity.

Limit annotations to what is genuinely useful — avoid over-explaining minor punctuation fixes.

General Feedback

Close with a short paragraph (3–5 sentences) summarizing:

• Overall tone, flow, and effectiveness of the text.
• Any recurring patterns worth noting (e.g., repeated preposition errors, tendency to omit articles).
• One or two practical tips the user can apply to future writing.

Example Prompt

"Can you review this for me?

Hi team, I wanted to share with you that the deploy of last friday was succesful. We resolve the bug that was causing errors in the checkout and now the users can complete theirs purchases without problems. Thanks to everyone that help with this."