Product Lens
Validate the why before building: YC-style product diagnostic, founder review, user journey audit, and ICE feature prioritization.
- What
- Validate the why before building: YC-style product diagnostic, founder review, user journey audit, and ICE feature prioritization.
- Cost
- Free
- Needs
- Use "Product Lens" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a product-diagnosis skill for pressure-testing direction before engineering starts. Four modes: a YC-style product diagnostic that asks the hard questions (who exactly is it for, what is the quantified pain, why now, what is the 10-star version, the MVP, the anti-goal, how you know it is working) and outputs a PRODUCT-BRIEF.md with a go/no-go recommendation; a founder review that reads your README, commits, and billing code to score product-market-fit signals and flag what does not matter; a user journey audit that maps onboarding friction and time-to-value as a new user; and ICE feature prioritization (impact times confidence divided by effort) for choosing between ideas under runway and team constraints. This lane owns diagnosis, not spec writing: a yes leads to implementation planning, not more theater. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: a thinking workflow, nothing to install; it produces documents and recommendations, not code, and its scores are only as good as the project context you give it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Product Lens" with your Muse. Prerequisites: a product idea, feature list, or existing project to diagnose. Thinking workflow, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/product-lens/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Run the product diagnostic on [idea]: ask me the hard questions one by one, then write PRODUCT-BRIEF.md with a go/no-go." 3. For an existing project, ask: "Run the founder review on this repo and tell me the one thing that would 10x it, plus what I should stop building." Tip: answer the diagnostic questions with specific people and numbers, not "developers" and vibes; the brief is only as good as your answers. Safety: a skill is plain-text instructions; it runs nothing by itself. Keep sensitive business numbers out of the chat if you share the brief externally.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.