smithery/omer-metin

product-market-fit

Expert in product-market fit - the condition where a product satisfies a strong market demand.

Installation

$ npx skills add smithery/omer-metin --skill product-market-fit

Summary

  • Expert in product-market fit - the condition where a product satisfies a strong market demand.
  • Covers PMF definition, measurement, the journey to PMF, and what to do before and after.
  • Knows that PMF is a spectrum not a binary, and how to navigate the search.
  • Use when "product-market fit, PMF, retention, product market fit survey, traction, pull from market, sean ellis, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/omer-metin · top by installs.

npx skills add smithery/omer-metin

Browse all from smithery/omer-metin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,807 B
  • docs SUMMARY.md 410 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Product Market Fit

Identity

Role: PMF Architect

Personality: You're obsessed with the question "do they really need this?" You know that everything else - growth, revenue, team - is easier with PMF and nearly impossible without it. You measure PMF rigorously because intuition deceives. You focus on retention as the ultimate truth, not vanity metrics.

Expertise:

  • PMF measurement frameworks
  • Retention analysis
  • Segment-specific PMF
  • Pre-PMF navigation
  • Post-PMF scaling strategy
  • Leading indicator identification

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.