Grammar Check

What Is This?

Overview

Grammar Check is a targeted proofreading skill that identifies grammar, logical, and flow errors in written content and suggests precise fixes without rewriting the entire document. Unlike full rewrite tools, this skill operates as a surgical editor, pinpointing specific issues and offering actionable corrections that preserve the author's original voice and intent. It functions as an expert copyeditor working alongside the writer rather than replacing them.

The skill analyzes text across three distinct dimensions: grammatical correctness, logical consistency, and narrative flow. Grammatical errors include subject-verb disagreement, incorrect tense usage, punctuation mistakes, and pronoun reference issues. Logical errors cover contradictory statements, unsupported claims, and reasoning gaps. Flow errors address awkward transitions, abrupt topic shifts, and sentence rhythm problems that disrupt readability.

This approach is particularly valuable when content is largely sound but needs refinement before publication. Rather than receiving a completely rewritten draft, users get a structured list of identified issues with targeted suggestions, allowing them to make informed decisions about each correction.

Who Should Use This

• Content writers and bloggers who need a final quality check before publishing articles or posts
• Technical writers reviewing documentation, API guides, or user manuals for clarity and correctness
• Product managers proofreading product requirement documents, release notes, or stakeholder communications

Why Use It?

Problems It Solves

• Preserving authorial voice: Full rewrite tools often strip away the writer's tone and style. Grammar Check provides corrections without altering the overall structure or personality of the text.
• Identifying logical inconsistencies: Standard spell-checkers miss reasoning errors, contradictory statements, or unsupported conclusions that undermine credibility.
• Improving readability without over-editing: Writers often need minor flow improvements, not a complete restructure. This skill targets only what needs fixing.

Core Highlights

• Identifies grammatical errors including tense inconsistency, subject-verb disagreement, and punctuation misuse
• Flags logical errors such as contradictions, unsupported assertions, and reasoning gaps
• Detects flow problems including abrupt transitions, repetitive sentence structures, and unclear pronoun references
• Suggests targeted fixes rather than full rewrites
• Preserves the original author's voice and document structure
• Provides issue-by-issue breakdowns for easy review
• Works across content types including technical documentation, marketing copy, and academic writing
• Supports iterative editing workflows

How to Use It?

Basic Usage

To invoke the Grammar Check skill, provide the text you want reviewed along with a clear instruction:

/grammar-check

Please review the following paragraph for grammar, logic, and flow errors:

"The new API endpoint returns a JSON response. However, it also sometimes 
return XML depending on the headers. Developers should always check the 
response type before parsing, which is a best practice we recommend."

The skill will return a structured list of identified issues with suggested corrections.

Specific Scenarios

Scenario 1: Technical Documentation Review A technical writer submits a draft API reference guide. The skill identifies a subject-verb disagreement ("it also sometimes return XML" should be "returns"), flags a redundant qualifier ("which is a best practice we recommend" restates the preceding instruction), and notes an abrupt transition between the endpoint description and the developer guidance.

Scenario 2: Marketing Copy Proofreading A marketing manager submits a product landing page draft. The skill catches inconsistent tense usage across sections, identifies a logical gap where a claim is made without supporting context, and flags a transition sentence that disrupts the persuasive flow.

Real-World Examples

A product manager reviewing a feature specification document uses Grammar Check to catch three subject-verb disagreements and two contradictory requirement statements before sharing the document with engineering.

A blogger proofreading a 1,200-word article receives a list of six targeted corrections covering punctuation errors, one logical inconsistency in the argument structure, and two flow improvements for paragraph transitions.

When to Use It?

Use Cases

• Final proofreading pass before publishing blog posts or articles
• Reviewing technical documentation before developer release
• Checking product requirement documents for logical consistency
• Proofreading email campaigns and marketing copy
• Reviewing academic papers and research drafts
• Auditing user-facing error messages and UI copy for clarity
• Preparing client-facing reports and proposals for submission

Important Notes

Requirements

• Input text should be provided in plain text or markdown format for accurate analysis
• The skill performs best on complete sentences and paragraphs rather than isolated fragments or bullet lists
• Users should specify the intended audience or content type when context-specific grammar standards apply
• For documents exceeding 1,000 words, segmenting the input into logical sections improves output precision