agentsclimarketplace

Product market fit

Skill jpoindexter/product-management-skills/skills/product-market-fit

Operational product-management skills and a /pm router for Codex and Claude.

Install
npx -y skills add jpoindexter/product-management-skills --skill product-market-fit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Assess product-market fit as evidence across a specific customer, problem, value proposition, behavior, retention, and viable business model. Use when the user asks whether a product has fit, which segment to pursue, why adoption or retention is weak, or what evidence is required before scaling.

SKILL.md

2.5 KB, as published. Nobody here has run it

Product-Market Fit

Evaluate fit as a segment-specific evidence stack, not a universal label or a single survey score.

Inputs

  • Target segment and qualifying situation
  • Underserved need or job
  • Current value proposition and alternatives
  • Acquisition, activation, retention, and revenue evidence
  • Qualitative behavior and churn evidence
  • Cost-to-serve and operating constraints

Workflow

  1. Narrow the segment until members share a meaningful situation, alternatives, and success criteria.
  2. Define the underserved need and current workaround.
  3. Explain why the product creates differentiated value for that segment.
  4. Trace the user journey from acquisition through recurring value and payment.
  5. Examine cohorts and repeated behavior; distinguish curiosity from durable use.
  6. Analyze churn, failed activation, and non-adoption as evidence, not noise.
  7. Test whether the value can be acquired, delivered, and supported economically.
  8. Classify fit by stage: unproven, problem evidence, solution evidence, repeatable value, or scalable fit.
  9. Define the next threshold and the cheapest evidence needed to cross it.

Output contract

Return the segment, need, alternatives, value proposition, evidence by lifecycle stage, strongest and weakest fit signals, business viability, fit classification, scaling recommendation, and next test.

Quality gate

  • Fit claims are scoped to one segment and use case.
  • Retention or repeated value matters more than top-line signups.
  • Qualitative evidence explains the quantitative pattern.
  • Distribution and willingness to pay are not deferred until after “fit.”
  • The recommendation states what not to scale yet.

Avoid

  • Declaring fit from launch demand, waitlists, or aggregate growth
  • Combining incompatible cohorts
  • Treating a high satisfaction score as sufficient
  • Scaling acquisition before recurring value is understood
  • Ignoring service cost or operational fragility

Source grounding

Operational synthesis informed by the stage-and-business-model discipline in Lean Analytics, customer-value and four-risk concepts in Inspired, and outcome orientation in Escaping the Build Trap.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.