/proofread
Check grammar, logic, and flow in any text — targeted fixes without rewriting
$ npx -y skills add phuryn/pm-skills --agent claude-codeHow it fires
How this command 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
/proofread
Context preview
What this command does when you run it.
Check grammar, logic, and flow in any text — targeted fixes without rewriting
Command definition
proofread.mddescription: Check grammar, logic, and flow in any text — targeted fixes without rewriting
argument-hint: "<text to check>"
/proofread -- Grammar & Flow Check
Identify grammar, logical, and flow errors in text. Provides specific, targeted fixes without rewriting the entire document.
Invocation
/proofread [paste text]
/proofread [upload a document]
Workflow
Step 1: Accept Text
Accept text in any form: pasted, uploaded document (DOCX, PDF, markdown), or email draft.
Step 2: Analyze
Apply the **grammar-check** skill:
Scan for three categories of issues:
**Grammar**: Spelling, punctuation, subject-verb agreement, tense consistency, article usage **Logic**: Contradictions, unsupported claims, circular reasoning, unclear references **Flow**: Awkward transitions, sentence rhythm, paragraph structure, redundancy, readability
Step 3: Report Issues
## Proofread Report
**Text length**: [word count]
**Issues found**: [count by category]
### Issues
#### 1. [Category: Grammar/Logic/Flow]
- **Location**: "[quoted text with issue]"
- **Issue**: [what's wrong]
- **Fix**: "[corrected text]"
[Repeat for each issue]
### Summary
- Grammar: [X] issues
- Logic: [X] issues
- Flow: [X] issues
- Overall quality: [assessment]
Step 4: Offer
- "Want me to **apply all fixes** and return the cleaned text?"
- "Should I **focus on a specific section** in more detail?"
Notes
- Fix suggestions should be minimal — change only what's needed, preserve the author's voice
- For non-native English speakers, be especially clear about *why* a change is suggested
- Don't over-correct style preferences — there's a difference between wrong and different
- For professional documents, also check for tone consistency and audience appropriateness
Read more
description: Check grammar, logic, and flow in any text — targeted fixes without rewriting argument-hint: "<text to check>"
/proofread -- Grammar & Flow Check
Identify grammar, logical, and flow errors in text. Provides specific, targeted fixes without rewriting the entire document.
Invocation
/proofread [paste text] /proofread [upload a document]
Workflow
Step 1: Accept Text
Accept text in any form: pasted, uploaded document (DOCX, PDF, markdown), or email draft.
Step 2: Analyze
Apply the **grammar-check** skill:
Scan for three categories of issues:
**Grammar**: Spelling, punctuation, subject-verb agreement, tense consistency, article usage **Logic**: Contradictions, unsupported claims, circular reasoning, unclear references **Flow**: Awkward transitions, sentence rhythm, paragraph structure, redundancy, readability
Step 3: Report Issues
## Proofread Report **Text length**: [word count] **Issues found**: [count by category] ### Issues #### 1. [Category: Grammar/Logic/Flow] - **Location**: "[quoted text with issue]" - **Issue**: [what's wrong] - **Fix**: "[corrected text]" [Repeat for each issue] ### Summary - Grammar: [X] issues - Logic: [X] issues - Flow: [X] issues - Overall quality: [assessment]
Step 4: Offer
- "Want me to **apply all fixes** and return the cleaned text?"
- "Should I **focus on a specific section** in more detail?"
Notes
- Fix suggestions should be minimal — change only what's needed, preserve the author's voice
- For non-native English speakers, be especially clear about *why* a change is suggested
- Don't over-correct style preferences — there's a difference between wrong and different
- For professional documents, also check for tone consistency and audience appropriateness
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
Other commands on pm-skills.
- /derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI
Open command - /document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply
Open command - /performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact
Open command - /security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks
Open command - /ship-check
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage, and compile the results
Open command - /analyze-cohorts
Perform cohort analysis on user data — retention curves, feature adoption, and engagement trends
Open command

