
Grammar Check
Proofread drafts for grammar, logic, and flow with focused fixes instead of a full AI rewrite.
Overview
grammar-check is an agent skill most often used in Grow (also Validate, Build, Launch) that finds grammar, logic, and flow issues and suggests focused fixes without full rewrites.
Install
npx skills add https://github.com/phuryn/pm-skills --skill grammar-checkWhat is this skill?
- Three-pass scan: grammar, logical consistency, and flow/readability
- Context-aware review using stated objective and audience tone
- Targeted fix suggestions without rewriting the entire document
- Covers spelling, tense, modifiers, unsupported claims, and incomplete thoughts
- Structured process: understand context, scan errors, then report actionable edits
- Three error categories: grammar, logical, and flow
Adoption & trust: 1.1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a draft that sounds rough or inconsistent but you do not want an agent to overwrite your messaging.
Who is it for?
Solo founders polishing landing pages, pitch decks rendered as text, help docs, and lifecycle emails before they go live.
Skip if: Greenfield copywriting from scratch, deep substantive strategy, or regulated legal/financial wording without human counsel.
When should I use this skill?
Proofreading content, checking writing quality, or reviewing a draft.
What do I get? / Deliverables
You receive a prioritized list of concrete edits aligned to your stated objective so the draft reads clearly and correctly.
- Annotated fix suggestions per issue
- Grammar, logic, and flow finding list
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Polished copy compounds in Grow, but the same checker applies whenever you ship written artifacts. Content and lifecycle messaging is the primary shelf for copy quality work on blogs, emails, and landing updates.
Where it fits
Tighten hero copy and remove contradictory claims before running ads.
Fix tense shifts and unclear procedures in onboarding documentation.
Proofread a launch announcement post for punctuation and flow.
Review a newsletter draft against a stated investor-update objective.
How it compares
Focused proofreading checker—not a brand voice generator or long-form content SEO skill.
Common Questions / FAQ
Who is grammar-check for?
Solo and indie builders who produce their own product, marketing, and support copy and want structured proofreading from an agent.
When should I use grammar-check?
On Validate landing drafts, Build documentation, Launch distribution posts, and Grow content or lifecycle emails whenever you need a quality pass before publishing.
Is grammar-check safe to install?
It processes text you provide; avoid pasting live secrets or unreleased financials, and review the Security Audits panel on this Prism page before use.
SKILL.md
READMESKILL.md - Grammar Check
# 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 - **Flow errors**: Choppy transitions, unclear organization, redundancy, passive voice overuse, vague pronouns, awkward phrasing ### Step 3: Categorize Errors Organize findings by type: 1. Grammar (spelling, punctuation, syntax) 2. Logic (clarity, coherence, reasoning) 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 al