Grammar Check

Level 2: Style & Readability (Sessions 16-30)

I'll also help you:

• Analyze readability scores
• Suggest style improvements
• Maintain consistent tone
• Reduce passive voice usage
• Track writing patterns over time

Example:

User: Check my blog post for readability
User: Analyze my writing style trends
User: Make this more concise
User: What are my common writing mistakes?

Level 3: Advanced Style Analysis (Sessions 31+)

I'll also help you:

• Compare writing to your style profile
• Match audience-appropriate tone
• Suggest improvements based on context
• Generate style guidelines
• Proactive style suggestions

Example:

User: Does this match my professional voice?
User: Rewrite this for a technical audience
User: What makes my writing distinctive?
User: Create a style guide for my blog

Grammar & Style Checks I Perform

Level 1: Basic Checks

Spelling & Grammar:

• Typos and misspellings
• Subject-verb agreement
• Tense consistency
• Pronoun usage
• Punctuation errors

Sentence Structure:

• Run-on sentences
• Sentence fragments
• Comma splices
• Misplaced modifiers
• Unclear phrasing

Formatting:

• Inconsistent capitalization
• Missing periods
• Quote formatting
• List formatting

Level 2: Style & Readability

Readability Metrics:

• Sentence length analysis
• Word complexity scoring
• Paragraph structure
• Flesch-Kincaid grade level
• Passive voice percentage

Style Consistency:

• Oxford comma usage
• Capitalization style
• Abbreviation handling
• Number formatting
• Date formatting

Writing Patterns:

• Common mistakes tracking
• Overused words/phrases
• Sentence variety
• Vocabulary richness
• Clarity scores

Level 3: Advanced Analysis

Style Profile Matching:

• Tone consistency check
• Voice alignment
• Audience appropriateness
• Context-aware suggestions
• Style deviation detection

Proactive Improvements:

• Automated style fixes
• Contextual corrections
• Tone adjustment suggestions
• Audience-tailored rewrites
• Style guide enforcement

Data I Track

Level 1

• Grammar error types and frequency
• Common spelling mistakes
• Sentence structure patterns
• Formatting inconsistencies
• Auto-correct success rate

Level 2

• Readability scores over time
• Writing style metrics
• Passive voice usage trends
• Vocabulary complexity
• Audience-appropriate scores

Level 3

• Complete writing style profile
• Tone patterns by context
• Audience response tracking
• Style guide adherence
• Proactive suggestion accuracy

Best Practices

1. Context matters: I consider audience and purpose
2. Your voice matters: I preserve your unique style
3. Learn from feedback: I adapt to your preferences
4. Check before sending: Always review before publishing
5. Track progress: Watch your writing improve over time

Questions I'll Ask

At Level 1:

• "What is this text for (email, blog, report)?"
• "Who is the audience?"
• "Should I be formal or informal?"
• "Any specific concerns to check for?"

At Level 2:

• "Should I analyze readability scores?"
• "Want to see your writing patterns?"
• "Should I track common mistakes?"
• "Any style preferences I should know?"

At Level 3:

• "Does this match your usual voice?"
• "Should I suggest improvements proactively?"
• "Want to create a style guide?"
• "How should I balance correction vs. preservation?"

Examples

Basic Grammar Check

User: Check this email for errors
User: "Hi Sarah,

I hope this email finds you good. Theirs a few things I wanted to discuss about the project were working on.

First, the deadline is tommorow and were not quite ready yet. Theirs some bugs in the testing enviroonment that need fixing.

Can we meet at 3pm to discuss?

Thanks,
John"

Assistant: 🔍 Grammar Check Results

FOUND 8 ERRORS:

1. "finds you good" → finds you well (common phrase)
2. "Theirs" → There's (possession vs contraction)
3. "were working" → we're working (verb vs contraction)
4. "tommorow" → tomorrow (spelling)
5. "were not quite ready" → we're not quite ready (verb vs contraction)
6. "Theirs some bugs" → There are some bugs (possession vs existence)
7. "enviroonment" → environment (spelling)
8. "3pm" → 3 PM (formatting consistency)

CORRECTED VERSION:
"Hi Sarah,

I hope this email finds you well. There's a few things I wanted to discuss about the project we're working on.

First, the deadline is tomorrow and we're not quite ready yet. There are some bugs in the testing environment that need fixing.

Can we meet at 3 PM to discuss?

Thanks,
John"

**Note:** I preserved your casual tone and style.

Style & Readability Analysis

User: Check my blog post for readability

User: [Long blog post about productivity]

Assistant: 📊 Readability Analysis

READABILITY SCORES:
- Flesch-Kincaid Grade: 12.4 (College level)
- Average sentence length: 22 words
- Average word length: 5.2 characters
- Passive voice: 15% (good, below 20% threshold)
- Paragraph length: Avg 4.7 sentences

SENTENCE STRUCTURE:
- Short sentences (< 15 words): 20%
- Medium sentences (15-25 words): 50%
- Long sentences (25+ words): 30%

ISSUES FOUND:
1. Very long sentence (42 words) in paragraph 3
   Suggestion: Break into two sentences

2. Consecutive long sentences in paragraph 5
   Suggestion: Add short sentence for pacing

3. Jargon-heavy sentence in paragraph 2
   Suggestion: Simplify or explain terms

STYLE NOTES:
✓ Active voice usage is good (85% active)
✓ Paragraph structure is consistent
✓ Flow is logical and clear
⚠ Consider more sentence variety (shorter intro sentences)

OVERALL:
Your writing is clear and professional. The college-level reading score is appropriate for your audience. Reducing some long sentences would improve readability further.

Want me to suggest specific changes?

Writing Pattern Analysis (Level 2)

User: What are my common writing mistakes?

Assistant: 📈 Your Writing Pattern Analysis (Last 30 days)

COMMON MISTAKES (Top 5):

1. Their/There/They're confusion (12 times)
   - Mistake: Using "their" for "there are"
   - Pattern: Happens when typing quickly
   - Fix: Auto-correct now enabled for this

2. Your/You're confusion (8 times)
   - Mistake: Using "your" instead of "you're"
   - Pattern: Casual writing contexts
   - Fix: Added to your personal dictionary

3. Comma splices (6 times)
   - Mistake: Joining independent clauses with only a comma
   - Pattern: Long sentences with multiple clauses
   - Suggestion: Use periods or semicolons

4. Inconsistent capitalization (5 times)
   - Mistake: "email" vs "Email" vs "EMAIL"
   - Pattern: Technical writing contexts
   - Suggestion: Choose one style and stick to it

5. Passive voice overuse (4 instances > 20% threshold)
   - Pattern: Professional emails and reports
   - Suggestion: Try more active voice when appropriate

IMPROVEMENT TRENDS:
✓ Spelling errors: Down 40% (auto-correct working)
✓ Grammar errors: Down 25% (learning from mistakes)
✓ Passive voice: Down 15% (more active voice usage)
⚠ Comma usage: No change (still learning)

YOUR STRENGTHS:
✓ Clear sentence structure (most of the time)
✓ Good paragraph organization
✓ Strong vocabulary
✓ Consistent tone

FOCUS AREAS:
1. Their/There/They're - Practice with quick exercises
2. Sentence variety - Mix short and long sentences
3. Active voice - More "I did" vs "It was done by me"

Keep writing - you're improving!

Style Profile Matching (Level 3)

User: Does this blog post match my usual voice?

User: [New blog post]

Assistant: 🎯 Style Profile Comparison

YOUR TYPICAL VOICE (from 50+ samples):
- Tone: Conversational but professional
- Sentence length: 18 words average
- Vocabulary: Accessible, occasional technical terms
- Structure: Short paragraphs, clear headers
- Personality: Friendly, first-person, anecdotes

THIS POST COMPARED TO YOUR STYLE:

MATCH SCORE: 78/100

✅ MATCHES YOUR STYLE:
- Conversational tone ✓
- First-person perspective ✓
- Short paragraphs ✓
- Clear structure ✓

⚠ DIFFERENT FROM YOUR USUAL STYLE:
- Sentence length: 26 words (vs 18 average) - too long
- Vocabulary: More technical jargon than usual
- Tone: Slightly more formal
- Structure: Longer paragraphs

SPECIFIC DEVIATIONS:
1. Paragraph 2: Very long (8 sentences vs your 3-4 norm)
   → Suggestion: Break into 2 paragraphs

2. Paragraph 4: Technical term "microservices architecture" without explanation
   → Your style usually explains technical terms

3. Tone: "This methodology leverages..." (formal)
   → Your usual style: "This approach uses..." (conversational)

RECOMMENDATION:
This post is good but doesn't fully sound like you. It reads more like a formal whitepaper than your typical blog voice.

REWRITE SUGGESTION (to match your style):
[Shows a version that sounds more like you]

Want me to apply this rewrite?

Integration with Other Skills

• journaling: Grammar check applies to journal entries too
• draft-email: Auto-check before sending emails
• style-transfer: Change style while fixing grammar
• tone-adjuster: Combine grammar and tone adjustments
• message-review: Comprehensive review before sending

Tips for Success

1. Provide context: Tell me audience and purpose
2. Review corrections: Don't blindly accept all changes
3. Track patterns: Learn from your common mistakes
4. Preserve your voice: I enhance, don't replace
5. Practice writing: The more you write, the better you get

Common Mistakes

• Accepting all corrections without review
• Ignoring tone and audience context
• Not tracking writing patterns over time
• Over-editing and losing personal voice
• Checking grammar but not readability

**Ready to check your writing? Just paste your text and I'll help!**34:["$","$L3a",null,{"content":"$3b","frontMatter":{"name":"grammar-check","description":"Grammar and style checking for written content"}}]