Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides structured frameworks for product managers to navigate the intersection of finance and growth. It transforms complex decision-making processes—such as evaluating acquisition channels or designing multi-agent AI workflows—into repeatable, evidence-based activities.
By grounding growth decisions in unit economics and customer quality, the skill set helps practitioners determine when to scale or terminate specific acquisition channels with financial rigor.
WHO IT'S FOR
Product Managers
evaluate acquisition channels using unit economics
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: pm-skills-codex.zip installed into a project-local .agents/skills folder · Codex
Before you start
Codex
An existing project or repository root
Platform: Codex
Run from: Your project or repository root
Open the Product Manager Skills Releases page and download pm-skills-codex.zip.
Unzip pm-skills-codex.zip into the root of the project or repository where you will use Codex.
Confirm that the root contains AGENTS.md and .agents/skills/<skill-name>/SKILL.md. Here, <skill-name> denotes each installed skill folder and should be replaced by the particular folder name when checking a skill.
Open Codex in that repository and ask it to use a named skill; the documented example names jobs-to-be-done.
Use the workshop-facilitation skill to facilitate a 45-minute retrospective on our failed beta launch. Start by offering the documented entry modes, then ask one targeted question at a time and show progress.
The positioning decision the research should support
Known competitors, or permission to identify them
Any prior competitive snapshot, if available
Use the competitive-research-snapshot skill. We are rewriting our positioning next sprint. Create a cited, decision-focused snapshot of our three most relevant competitors, clearly labeling facts, inferences, and assumptions. Ask for the product and positioning decision if I have not supplied them.
A prior capture, optionally; omit it for baseline mode
Use the pricing-packaging-tracker skill in baseline mode for one competitor. Capture its public tiers, prices, feature gates, and limits in the stable schema, include source URLs and dates, and do not invent values where pricing is opaque.