product-manager SKILL.md skillA
product-manager from coreyhaines31/makerskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coreyhaines31/makerskills/product-manager@v0.7.1Pins v0.7.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coreyhaines31/makerskills
- Path
skills/product-manager/SKILL.md- Versions recorded
- 5
- Latest version
- v0.7.1, committed Nov 11, 2026
- First version recorded
- Nov 9, 2026
- Size
- 16,873 bytes
- Repository stars
- 919
- License
- MIT
When you want to plan, build, or check an app from idea through launch readiness — web, Apple, mobile, or extensions. Writes the brief, picks the stack (Next.js + TypeScript + Prisma by default, Swift on Apple), designs complete UX states, defines roles and agent access, measures performance before optimizing, and produces a readiness report where missing evidence is never a pass. Four modes: spec (plan v1), check (launch readiness), audit (ranked improvements, including what a new model…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /product-manager — Take an app from idea to launch-ready Most apps that fail at launch don't fail on the main feature. They fail on what nobody specced: a client who can download another client's files, an invite button that sends twice on a slow network, a backup nobody ever restored, a cache keyed on project ID that leaks internal notes. This skill makes you decide those things up front, and then proves them before calling anything ready. It ends at **launch-ready**, not launched. Promotion, SEO, launch posts and growth go to the marketing skills. ## Mental model - **Applicability, not parity.** A local macOS timer doesn't need organizations. A collaborative SaaS does. Choose a platform profile, then check what applies. - **Evidence, not vibes.** Every requirement ends up as pass, gap, not assessed, or justified N/A. Missing evidence isn't a pass. - **Measure, then fix.** Broken before slow. Baseline before cache. - **Complement the model.** Build what gets *more* useful as models improve. ## Step 0 — Pick the mode | Mode | When | Output | |---|---|---| | **spec** | New app or v1 plan | Brief, stack, UX states, access model, test plan | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5kod2l76ka6u74ky/a3870cb4bd1cbdd07a94aed17871889d898729eeb7c2955f34bba26b4a3d8802.json
Then /plugin install product-manager@markdownregistry-5kod2l76ka6u74ky in Claude Code. It installs v0.7.1, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add coreyhaines31/makerskills/product-manager@sha256:a3870cb4bd1cbdd0The line at the top of this page pins the label v0.7.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5kod2l76ka6u74ky)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in coreyhaines31/makerskills/product-manager since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of product-manager from somewhere else? Ask it: where did my product-manager come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 9, 2026 and Nov 11, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.7.1 latest | 2026-11-11 | 6e9bf90 | 16,873 B | A | view · diff |
| v0.7.0 | 2026-11-11 | 6ec22a4 | 16,846 B | A | view · diff |
| v0.6.0 | 2026-11-10 | 5d49b72 | 16,483 B | A | view · diff |
| v0.5.0 | 2026-11-09 | 82f75c4 | 16,367 B | A | view · diff |
| v0.4.0 | 2026-11-09 | 3f19e33 | 16,029 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/product-manager/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16873 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
coreyhaines31/makerskills · 919 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5kod2l76ka6u74ky GET https://markdownregistry.com/api/v1/resolve?ref=coreyhaines31/makerskills/product-manager GET https://markdownregistry.com/api/v1/blob/a3870cb4bd1cbdd07a94aed17871889d898729eeb7c2955f34bba26b4a3d8802
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from coreyhaines31/makerskills
Every file in coreyhaines31/makerskills