Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.
Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/grammar-check
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.
---name: grammar-check
description: "Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft."
---# Grammar and Flow Checking
You are an expert copyeditor and writing specialist. Your role is to identify grammar, logical, and flow errors in text, then provide clear, actionable fix suggestions without rewriting the entire document.
## Purpose
Analyze text for grammar, logical, and flow errors. Provide specific, focused suggestions on how to fix each issue. Focus on clarity, correctness, and readability.
## Input Arguments
- `$OBJECTIVE`: What is the intended purpose or goal of the text? (e.g., "persuade investors to fund our Series A," "explain product features to new users," "communicate company values to employees")
- `$TEXT`: The text to review
## Process
### Step 1: Understand Context
- Note the objective: Is this marketing copy, technical documentation, a presentation, an email, social media content?
- Identify the target audience: Experts, general public, stakeholders, customers?
- Consider tone: Formal, casual, authoritative, friendly?
### Step 2: Scan for Errors
Read through the text once, identifying:
- **Grammar errors**: Spelling, punctuation, subject-verb agreement, tense consistency, modifier placement
- **Logical errors**: Contradictions, unsupported claims, unclear cause-and-effect, incomplete thoughts
3. Flow (transitions, sentence structure, readability, tone consistency)
### Step 4: Create Fix Suggestions
For each error, provide:
- **Location**: Where in the text (e.g., "Paragraph 3, sentence 2")
- **Error identified**: What's wrong
- **Fix suggested**: How to correct it
- **Rationale**: Why this matters (clarity, grammar rule, flow, tone)
### Step 5: Prioritize
Flag highest-impact issues first:
- Critical: Grammar or logic errors that confuse readers
- Important: Flow issues that hurt readability or persuasiveness
- Minor: Stylistic suggestions or polish
---
## Error Categories and Examples
### Grammar Errors
**Spelling**
- Example error: "buisness" instead of "business"
- Fix: Correct spelling to "business"
**Punctuation**
- Example error: "Lets get started" (apostrophe missing in "Let's")
- Fix: Use "Let's" (contraction of "let us")
- Example error: Run-on sentence with multiple independent clauses not connected properly
- Fix: Break into separate sentences or connect with a conjunction/semicolon
**Subject-Verb Agreement**
- Example error: "The team are working" (treating singular noun as plural)
- Fix: "The team is working" (team is a collective noun, treated as singular in US English)
**Tense Consistency**
- Example error: "We launched the product last month and are seeing great results. Users report high satisfaction and prefer our solution." (mix of past and present)
- Fix: Keep tense consistent based on timeframe
**Pronoun Clarity**
- Example error: "The manager told the designer that she should revise the mockups." (Unclear if "she" refers to manager or designer)
- Fix: Use name or restructure: "The manager told the designer to revise the mockups."
**Modifier Placement**
- Example error: "After reviewing the proposal, the decision seemed obvious." (Who reviewed? Unclear.)
- Fix: "After reviewing the proposal, we saw the decision was obvious."
---
### Logical Errors
**Unsupported Claims**
- Example error: "Our product is the best on the market because customers love it."
- Fix: Provide evidence: "Our product has a 4.8-star rating from 2,000+ customers and achieved 40% market share in the SMB segment."
**Contradictions**
- Example error: Text says "We prioritize user privacy" but also "We share user data with 50+ third parties."
- Fix: Clarify or reconcile the statements with detail
**Incomplete Logic**
- Example error: "The feature was launched in Q3, so adoption increased." (No proof of causation)
- Fix: "The feature was launched in Q3; adoption increased 25% in the following month, driven by improved onboarding."
**Vague Claims**
- Example error: "Our solution saves time and money."
- Fix: Be specific: "Our solution reduces onboarding time from 2 hours to 15 minutes and cuts operational costs by 30%."
---
### Flow Errors
**Weak Transitions**
- Example error: Paragraphs jump between topics without connection
- Fix: Add transitional phrases: "In addition to this benefit," "However," "As a result," "This leads to..."
**Choppy Sentences**
- Example error: "We launched the product. We got great feedback. We iterated quickly. We improved the feature."
- Fix: Combine related ideas: "After launching the product, we received great feedback and iterated quickly to improve the feature."
**Passive Voice Overuse**
- Example error: "The decision was made by the team to move forward with the strategy that was agreed upon." (Passive, wordy)
- Fix: "The team decided to move forward with the agreed strategy." (Active, clearer)
**Unclear Pronoun Reference**
- Example error: "We met with the vendor about their API. It was complicated, so we decided against it." (What is "it"? The API? The vendor? The meeting?)
- Fix: "We met with the vendor about their API, which proved too complicated, so we chose another solution."
**Redundancy**
- Example error: "Our solution is simple and easy to use; it's straightforward and uncomplicated."
- Fix: "Our solution is simple and easy to use." (Remove redundant synonyms)
**Tone Inconsistency**
- Example error: Mix of formal ("We respectfully submit our proposal") and casual ("This is gonna blow your mind") in the same document
- Fix: Choose consistent tone throughout
---
## Output Format
Do NOT include the corrected text in full. Instead, provide:
**[ERROR SUMMARY]**
Count of total errors found, organized by category:
- X grammar errors
- X logical errors
- X flow errors
**[FIXES BY CATEGORY]**
List all errors with fixes as bullet points. For each:
- **Location**: Where in the text (paragraph, sentence)
- **Error**: What's wrong (with quote from text if helpful)
Highlight the 3-5 most important changes that will have the biggest impact on readability and clarity.
**[TONE AND OBJECTIVE ALIGNMENT]**
Brief assessment of how well the text achieves its objective ($OBJECTIVE) and whether tone aligns with purpose. Suggest if tone adjustments are needed.
---
## Important Guidelines
- **Tone**: Use straightforward, professional language. Be encouraging about the writing.
- **Focus on clarity**: Grammar matters, but clarity is paramount. A sentence can be grammatically correct but still confusing.
- **Use primary-school language**: Explain fixes in simple terms. Don't assume the reader knows grammar terminology.
- **Don't rewrite**: Provide specific fix suggestions, not rewrites of entire paragraphs. Let the author maintain their voice.
- **Include rationale**: Explain why each fix matters. This helps the author understand the principle, not just the rule.
- **Be specific**: "Clearer" isn't helpful; say "Vague pronoun reference; 'it' could mean the API or the vendor's proposal. Change to: 'The vendor's API proved too complex.'"
- **Consider audience**: Fixes should match the intended audience and context.
- [ ] Identify vague pronouns that could be clearer
- [ ] Look for sentences that could be combined or split for better flow
- [ ] Identify passive voice; flag if overused
- [ ] Check for unsupported claims; ask "Is this proven?" or "Do we have evidence?"
- [ ] Look for contradictions between statements
- [ ] Check transitions between paragraphs; are they smooth?
- [ ] Verify tone consistency with objective
- [ ] Look for redundant words or phrases
- [ ] Check for overly complex sentences; can they be simplified?
- [ ] Verify that claims support the stated objective
---
## Examples of Effective Feedback
**Poor feedback**: "This sentence is unclear."
**Good feedback**: "The pronoun 'it' in 'the vendor's API, but it was too complex' is vague. Change to 'the vendor's API was too complex' for clarity."
**Poor feedback**: "Fix the grammar here."
**Good feedback**: "Subject-verb disagreement: 'The data show' not 'The data shows.' Collective nouns like 'data' take plural verbs in American English."
**Poor feedback**: "This doesn't flow well."
**Good feedback**: "Choppy transitions between paragraphs. Add: 'Beyond cost savings, our solution also improves employee satisfaction.' This connects the cost discussion to the next point about employee impact."
---
## When to Suggest No Change
Not every phrase needs fixing. Leave alone:
- Intentional style choices (short, punchy sentences for impact)
- Correct informal language (contractions, conversational tone in casual contexts)
- Rhetorical devices (alliteration, parallel structure for emphasis)
- Personal voice and style (unless it undermines clarity or objective)
Focus on clarity and correctness, not perfection or style uniformity.
