Skill Claude Code
Activate on "analyze competitor", "competitive analysis", "compare us to [company]".
Skill Claude Code
Activate on "analyze competitor", "competitive analysis", "compare us to [company]".
Skill Claude Code
Activate on "launch checklist", "pre-launch check", "ready to launch?", "launch prep".
Skill Claude Code
Activate on "define metrics", "what should I measure", "success metrics for [feature]", "KPIs for [initiative]".
Skill Claude Code
Activate on "write a PRD", "create a PRD", "draft a PRD", "PRD for [feature]", "spec out [feature]", or "one pager for [feature]".
Skill Claude Code
Activate on "plan sprint", "sprint planning", "what should we work on", "organize the backlog".
Skill Claude Code
Activate on "synthesize research", "analyze interviews", "research findings", "interview synthesis".
Skill Claude CodeCodex
Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.
Skill Claude CodeCodex
Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.
Skill Claude CodeCodex
Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.
Skill Claude CodeCodex
Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.
Skill Claude CodeCodex
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
aakashg/pm-github-workflow-repo
Skill Claude CodeCodex
Researches a competitor and produces a structured, evidence-backed analysis. Use when asked to "analyze a competitor", "run a competitor scan", do "competitive analysis", or "research [company name]".
aakashg/pm-github-workflow-repo
Skill Claude CodeCodex
Synthesizes user feedback from multiple sources into ranked, actionable themes. Use when asked to "synthesize feedback", "analyze user feedback", run a "feedback synthesis", or "what are users saying".
aakashg/pm-github-workflow-repo
Skill Claude CodeCodex
Reviews a PRD against a completeness checklist and flags gaps before a human reviews it. Use when asked to "review this PRD" or for a "PRD review".
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: