grammar-check
by phurynThe grammar-check skill identifies grammar, logic, and flow issues in a draft and suggests targeted fixes without rewriting the whole piece. Use it for grammar-check for Proofreading, writing quality checks, and editorial review when you want clear, context-aware edits.
This skill scores 78/100, which means it is a solid directory listing candidate for users who want a focused grammar/flow review workflow. The repository gives enough operational detail to help agents trigger and use it with less guesswork than a generic proofreading prompt, though it would benefit from more adoption-oriented support material.
- Clear trigger and scope: the frontmatter says to use it for proofreading, writing-quality checks, and draft review, with a specific focus on grammar, logical, and flow errors.
- Good operational guidance: it defines input arguments ($OBJECTIVE and $TEXT) and lays out a step-by-step review process, which helps an agent execute the skill consistently.
- Substantive skill body: the file is non-trivial in length with multiple headings and constraint sections, suggesting real workflow content rather than a placeholder.
- No install command, references, or support files are provided, so users have limited help understanding integration or expected runtime behavior.
- The visible excerpt shows no examples or test cases, so edge-case behavior and output format may still require interpretation by the user or agent.
Overview of grammar-check skill
What grammar-check does
The grammar-check skill identifies grammar, logic, and flow problems in a draft and returns targeted fixes instead of rewriting the whole piece. It is built for proofreading content where accuracy, tone, and readability matter more than a full rewrite.
Who should use it
Use this grammar-check skill if you need a fast editorial pass on marketing copy, documentation, emails, posts, or internal writing. It fits best when you already know the message and want the text cleaned up for clarity, not re-authored from scratch.
Why it is worth installing
The main value is structured review: it asks for the document’s purpose, then checks grammar, logical consistency, and flow against that context. That makes it more useful than a generic “fix this text” prompt, especially for grammar-check for Proofreading where the same sentence may be correct grammatically but wrong for the audience or goal.
How to Use grammar-check skill
Install grammar-check
Use the repo’s install command to add the skill: npx skills add phuryn/pm-skills --skill grammar-check. After install, confirm the skill is available in your agent workflow and that it can receive both an objective and the text to review.
Give the skill the right input
The core inputs are $OBJECTIVE and $TEXT. A weak request says, “Check this draft.” A stronger grammar-check usage prompt says, “Review this landing page to persuade trial users to sign up, then flag grammar, logic, and flow issues without rewriting the voice.” That context helps the skill judge wording, structure, and tone.
Read the right files first
Start with SKILL.md to understand the intended review process and output style. Then check any nearby repo guidance if it exists in your setup, but the supplied skill is intentionally lightweight, so the main decision point is whether your workflow can provide a clear objective and a clean text block.
Use a review workflow that improves output
For best grammar-check guide results, send one discrete draft at a time, not a mixed bundle of unrelated snippets. Ask for issues grouped by grammar, logic, and flow when you want actionable proofreading; ask for only the highest-priority fixes when speed matters more than completeness.
grammar-check skill FAQ
Is grammar-check only for grammar mistakes?
No. The grammar-check skill also looks for logical breaks and flow problems, which matters when a sentence is grammatically fine but the argument is confusing or the transitions are awkward.
How is this different from a normal prompt?
A normal prompt often produces a rewrite or broad comments. This grammar-check skill is more constrained: it is meant to inspect a draft against an objective and give focused edits, which usually reduces guesswork during proofreading.
Is grammar-check good for beginners?
Yes, if the user can state the draft’s purpose in one sentence. Beginners usually get better results when they provide the audience, tone, and text type up front instead of asking for a vague “proofread.”
When should I not use it?
Skip grammar-check when you want a creative rewrite, a brand-new draft, or strategic messaging work. It is best for grammar-check usage in editing workflows, not for generating original copy from a blank page.
How to Improve grammar-check skill
Make the objective specific
The strongest grammar-check inputs explain what the text is supposed to do: inform users, convert leads, reassure customers, or align internal teams. If the goal is vague, the skill can still catch errors, but it will be less precise about what counts as a flow or logic problem.
Include context that changes the edit
Provide audience, tone, and format when they affect the judgment. For example, “customer-facing help article for first-time users” leads to different fixes than “investor update for executives,” even if the sentences look similar.
Ask for the kind of feedback you need
If you want clean proofreading, ask for issue-by-issue notes and suggested corrections. If you want speed, ask for only blocking issues or the top five fixes. This makes grammar-check more practical than a broad editorial pass and keeps the output closer to how you will actually revise the draft.
Fix common failure points before the first run
The biggest quality hit comes from incomplete text, unclear goals, and mixed document types in one request. Before you run grammar-check, remove placeholders, decide whether the draft should sound formal or casual, and separate copy that serves different audiences.