phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add phuryn/pm-skills --skill grammar-checkgit clone --depth 1 https://github.com/phuryn/pm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/phuryn/pm-skills/grammar-check)<a href="https://agentmods.dev/skills/phuryn/pm-skills/grammar-check"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/grammar-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/phuryn/pm-skills/grammar-check"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/grammar-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.02148 |
| Opus 5.5 | $0.00015 | $0.00859 |
| Sonnet 5.5 | $0.00007 | $0.00430 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
grammar-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- grammar-check — 100% identical, 0 lines differ
- grammar-check — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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:
- Grammar (spelling, punctuation, syntax)
- Logic (clarity, coherence, reasoning)
- 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
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 210 lines · 37 tokens per session scan A 67e4721b2554
grammar-check is a skill published in the GitHub repository phuryn/pm-skills (27,091 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 2,148 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.
Other skills, from other repositories
pmm-resume
Resume reviewer and tailoring engine for Product Marketing Managers (IC to VP, including AI PMM roles). Takes baseline resume + job description → dissects JD → ranks bullets by impact fit → rebuilds complete resume in one pass. Trigger on: resume + JD paste, "tailor this", "which bullets for this role", "rebuild for…
product-marketing-context
Build and maintain the shared GTM brain — product context, ICP, positioning, voice, market context, proof points, plus optional strategy and execution, and the deal-reality fields (objections, switching forces, customer language, anti-persona) — that every other skill in this stack reads before producing output. Works…
workflow-orchestrator
Orchestrates multi-skill PMM programs end-to-end — chains positioning, competitive, GTM strategy, campaign briefs, stakeholder maps, and retros into one coherent program with a master document and brain updates. Trigger on: "run full GTM workflow", "run a full launch", "launch [product] end to end", "positioning…
positioning-messaging
Builds or audits positioning statements, messaging hierarchies, homepage copy, and persona cards using April Dunford's Obviously Awesome framework across five modes (build, audit, fletch, sales-enablement, homepage). Refuses to generate without a named primary persona and 3+ alternatives including status quo, and…
writing-assistant
Rewrites, sharpens and drafts B2B writing in the writer's real voice: Slack messages, emails, memos, PRDs, decks, plus marketing content (blog posts, landing pages, press releases, case studies, newsletters, social posts). Use whenever someone wants to rewrite, tighten, draft or audit copy, asks why copy isn't landing…
proof-points
Build and maintain a sourced, gated registry of the proof points your messaging relies on — metrics, customer quotes, case study results, and analyst citations. Use when pulling proof points out of a deck or battlecard, checking whether a stat is safe to use in copy, sourcing a new claim before it ships, or auditing…