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 release-notesgit 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/release-notes)<a href="https://agentmods.dev/skills/phuryn/pm-skills/release-notes"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/release-notes/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/release-notes"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector 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.00057 | $0.00590 |
| Opus 5.5 | $0.00023 | $0.00236 |
| Sonnet 5.5 | $0.00011 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
release-notes 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:
- release-notes — 100% identical, 0 lines differ
- release-notes — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.
Context
You are writing release notes for $ARGUMENTS.
If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.
Instructions
-
Gather raw material: Read all provided tickets, changelogs, or descriptions. Extract:
- What changed (feature, improvement, or fix)
- Who it affects (which user segment)
- Why it matters (the user benefit)
-
Categorize changes:
- New Features: Entirely new capabilities
- Improvements: Enhancements to existing features
- Bug Fixes: Issues resolved
- Breaking Changes: Anything that requires user action (migrations, API changes)
- Deprecations: Features being sunset
-
Write each entry following these principles:
- Lead with the user benefit, not the technical change
- Use plain language — avoid jargon, internal codenames, or ticket numbers
- Keep each entry to 1-3 sentences
- Include visuals or screenshots if the user provides them
Example transformations:
-
Technical: "Implemented Redis caching layer for dashboard API endpoints"
-
User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
-
Technical: "Fixed race condition in concurrent checkout flow"
-
User-facing: "Fixed an issue where some orders could fail during high-traffic periods."
-
Structure the release notes:
# [Product Name] — [Version / Date] ## New Features - **[Feature name]**: [1-2 sentence description of what it does and why it matters] ## Improvements - **[Area]**: [What got better and how it helps] ## Bug Fixes - Fixed [issue description in user terms] ## Breaking Changes (if any) - **Action required**: [What users need to do]
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 · 64 lines · 57 tokens per session scan A b617edd39e72
release-notes is a skill published in the GitHub repository phuryn/pm-skills (27,222 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 590 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
competitor-deep-dive
Builds a long-form, fully sourced deep-dive on one competitor for a named decision (strategy call, RFP, pricing change, roadmap bet), with dated reviews, deal evidence, a head-to-head per offering and where they win. Triggers: "deep-dive on [competitor]", "full competitor write-up", "what do users really say about…
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…
product-marketing-context
Builds and maintains the shared GTM brain (product context, ICP, positioning, voice, market context, proof points, plus optional strategy and execution sections and the deal-reality fields) that every other skill reads before producing output. Works standalone from your own answers, and gets stronger when you connect…
competitive-battlecard
Builds a one-page competitor battlecard a seller can skim in 60 seconds before a call, tailored to role, GTM motion, buyer persona, deal stage and the competitor's status in the deal. Trigger on: "battlecard for [competitor]", "how do we beat [competitor]", "[competitor] is in my deal", "what do I say against…
prd
Co-writes a full Product Requirements Document with an embedded Solution Story, anchored in your brain's positioning and ICP. Use when a PM or PMM needs a PRD, a standalone Solution Story for GTM communications, or help structuring a feature or launch spec.
beachhead-segment
Scores candidate segments on Burning Pain, Willingness to Pay, Winnability and Referral Potential, with blocking gates, to pick your highest-priority beachhead. Use when choosing a first market or customer segment; the confirmed beachhead is written to brain Section 2 only on your say-so.