ln-51-opportunity-evaluator

Name: ln-51-opportunity-evaluator
Author: levnikolaevich

520stars73forks

How to install ln-51-opportunity-evaluator?

levnikolaevich/claude-code-skills/ln-51-opportunity-evaluator

$npx -y skills add levnikolaevich/claude-code-skills --skill ln-51-opportunity-evaluator

Installs into the current project.

Summary

Evaluates new product directions using current demand, acquisition, competition, economics, and validation evidence. Use before commitment; not for backlog or implementation planning.

Files · 1

View on GitHub

SKILL.md

1	# Opportunity Evaluator
2
3	Goal: Evaluate product opportunities before implementation commitment. Start from observable demand and a reachable acquisition path, eliminate weak candidates early, and recommend one low-cost validation step without manufacturing market precision.
4
5	Execution contract: Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete only when its action and required evidence are complete. `N/A`, skipped, unavailable, or delegated items remain incomplete.
6	Before returning, apply this skill's verdict, decision, and approval rules to every incomplete item and prepend Checklist: X/Y complete<br>Incomplete: None \| section/item — reason; outcome impact; exact next action; list every incomplete item.
7
8	## Tool Routing
9
10	\| Need \| Preferred tool \| Use it when \| Fallback \|
11	\|---\|---\|---\|---\|
12	\| Product and constraints \| User context plus existing product, analytics, customer, and strategy documents \| Establishing audience, assets, channels, economics, and non-goals \| State assumptions and request only consequential missing intent \|
13	\| Current demand and acquisition \| Web research, trend or marketplace data, communities, reviews, ads, directories, and primary customer evidence \| Every external market claim that affects elimination or recommendation \| Mark the signal unavailable; never infer a number from search-result count \|
14	\| Competition and pricing \| Competitor product pages, pricing, release history, distribution channels, reviews, and public filings where relevant \| Establishing substitutes, willingness-to-pay signals, and credible differentiation \| Use qualitative evidence with explicit confidence \|
15	\| Feasibility and validation cost \| Existing capabilities, public APIs, regulations, platform rules, and current official documentation \| Comparing the cheapest credible experiment and major blockers \| Label estimates and name the evidence still required \|
16
17	Keep the evaluation read-only. Do not create project files, roadmaps, Epics, Stories, implementation plans, campaigns, listings, advertisements, or customer outreach.
18
19	## Evidence Classes
20
21	\| Class \| Meaning \|
22	\|---\|---\|
23	\| `MEASURED` \| Direct analytics, transactions, experiments, or instrumented observations with known method and date \|
24	\| `REPORTED` \| A primary source reports a value or behavior, but the underlying measurement is not independently available \|
25	\| `ESTIMATED` \| A stated model based on explicit inputs and assumptions \|
26	\| `INFERRED` \| A qualitative conclusion from observable proxies \|
27	\| `UNKNOWN` \| Evidence is unavailable, stale, incomparable, or too weak to support a decision \|
28
29	Do not turn `REPORTED`, `ESTIMATED`, or `INFERRED` evidence into a measured market size, search volume, conversion rate, revenue, or willingness-to-pay claim. Date every external source and distinguish the event date from the publication date when they differ.
30
31	## Checklist
32
33	### 1. Frame the Decision
34
35	- [ ] Resolve the existing product or capability, target users, decision horizon, available assets, geographic or regulatory scope, constraints, and explicit non-goals.
36	- [ ] Accept user-supplied candidates or generate a bounded set of materially distinct opportunities from product context and current signals; do not create cosmetic variants of one idea.
37	- [ ] Define what would justify deeper validation: identifiable user and problem, observable demand, reachable channel, credible value exchange, differentiating wedge, and affordable experiment.
38	- [ ] Separate discovery of a new direction from prioritization of already committed work or implementation planning.
39	- [ ] Record assumptions that can reverse the recommendation and identify which are discoverable through research versus user intent.
40
41	### 2. Collect One Evidence Bundle per Candidate
42
43	- [ ] Identify who experiences the problem, how they solve it today, what triggers active search or purchase, and what evidence shows the pain is recurring or costly.
44	- [ ] Find a reachable acquisition channel and its mechanism: query, marketplace category, integration ecosystem, community, partner, outbound audience, or another observable path.
45	- [ ] Inspect direct competitors, substitutes, do-nothing behavior, pricing, positioning, distribution, review complaints, and evidence of continued investment or abandonment.
46	- [ ] Examine economic signals without inventing unit economics: price anchors, budget owner, purchase frequency, switching cost, delivery cost, platform fees, and support burden.
47	- [ ] Identify implementation, data, dependency, regulation, trust, distribution, and operational blockers that affect the cost of a validation experiment.
48	- [ ] Capture source, date, evidence class, scope, confi

levnikolaevichPublisher · 19 listings

Preview

levnikolaevich/claude-code-skills

# Opportunity Evaluator

**Goal:** Evaluate product opportunities before implementation commitment. Start from observable demand and a reachable acquisition path, eliminate weak candida

**Execution contract:** Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete onl

Before returning, apply this skill's verdict, decision, and approval rules to every incomplete item and prepend **Checklist: X/Y complete**<br>**Incomplete: Non

Repolevnikolaevich/claude-code-skills

LicenseMIT

TypeSkills

CategoryPlanning

UpdatedJul 2026

Repo stars520

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

ln-51-opportunity-evaluator

520stars73forks

View on GitHub

How to install ln-51-opportunity-evaluator?

levnikolaevich/claude-code-skills/ln-51-opportunity-evaluator

$npx -y skills add levnikolaevich/claude-code-skills --skill ln-51-opportunity-evaluator

Installs into the current project.

Summary

Evaluates new product directions using current demand, acquisition, competition, economics, and validation evidence. Use before commitment; not for backlog or implementation planning.

Files · 1

View on GitHub

SKILL.md

1	# Opportunity Evaluator
2
3	Goal: Evaluate product opportunities before implementation commitment. Start from observable demand and a reachable acquisition path, eliminate weak candidates early, and recommend one low-cost validation step without manufacturing market precision.
4
5	Execution contract: Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete only when its action and required evidence are complete. `N/A`, skipped, unavailable, or delegated items remain incomplete.
6	Before returning, apply this skill's verdict, decision, and approval rules to every incomplete item and prepend Checklist: X/Y complete<br>Incomplete: None \| section/item — reason; outcome impact; exact next action; list every incomplete item.
7
8	## Tool Routing
9
10	\| Need \| Preferred tool \| Use it when \| Fallback \|
11	\|---\|---\|---\|---\|
12	\| Product and constraints \| User context plus existing product, analytics, customer, and strategy documents \| Establishing audience, assets, channels, economics, and non-goals \| State assumptions and request only consequential missing intent \|
13	\| Current demand and acquisition \| Web research, trend or marketplace data, communities, reviews, ads, directories, and primary customer evidence \| Every external market claim that affects elimination or recommendation \| Mark the signal unavailable; never infer a number from search-result count \|
14	\| Competition and pricing \| Competitor product pages, pricing, release history, distribution channels, reviews, and public filings where relevant \| Establishing substitutes, willingness-to-pay signals, and credible differentiation \| Use qualitative evidence with explicit confidence \|
15	\| Feasibility and validation cost \| Existing capabilities, public APIs, regulations, platform rules, and current official documentation \| Comparing the cheapest credible experiment and major blockers \| Label estimates and name the evidence still required \|
16
17	Keep the evaluation read-only. Do not create project files, roadmaps, Epics, Stories, implementation plans, campaigns, listings, advertisements, or customer outreach.
18
19	## Evidence Classes
20
21	\| Class \| Meaning \|
22	\|---\|---\|
23	\| `MEASURED` \| Direct analytics, transactions, experiments, or instrumented observations with known method and date \|
24	\| `REPORTED` \| A primary source reports a value or behavior, but the underlying measurement is not independently available \|
25	\| `ESTIMATED` \| A stated model based on explicit inputs and assumptions \|
26	\| `INFERRED` \| A qualitative conclusion from observable proxies \|
27	\| `UNKNOWN` \| Evidence is unavailable, stale, incomparable, or too weak to support a decision \|
28
29	Do not turn `REPORTED`, `ESTIMATED`, or `INFERRED` evidence into a measured market size, search volume, conversion rate, revenue, or willingness-to-pay claim. Date every external source and distinguish the event date from the publication date when they differ.
30
31	## Checklist
32
33	### 1. Frame the Decision
34
35	- [ ] Resolve the existing product or capability, target users, decision horizon, available assets, geographic or regulatory scope, constraints, and explicit non-goals.
36	- [ ] Accept user-supplied candidates or generate a bounded set of materially distinct opportunities from product context and current signals; do not create cosmetic variants of one idea.
37	- [ ] Define what would justify deeper validation: identifiable user and problem, observable demand, reachable channel, credible value exchange, differentiating wedge, and affordable experiment.
38	- [ ] Separate discovery of a new direction from prioritization of already committed work or implementation planning.
39	- [ ] Record assumptions that can reverse the recommendation and identify which are discoverable through research versus user intent.
40
41	### 2. Collect One Evidence Bundle per Candidate
42
43	- [ ] Identify who experiences the problem, how they solve it today, what triggers active search or purchase, and what evidence shows the pain is recurring or costly.
44	- [ ] Find a reachable acquisition channel and its mechanism: query, marketplace category, integration ecosystem, community, partner, outbound audience, or another observable path.
45	- [ ] Inspect direct competitors, substitutes, do-nothing behavior, pricing, positioning, distribution, review complaints, and evidence of continued investment or abandonment.
46	- [ ] Examine economic signals without inventing unit economics: price anchors, budget owner, purchase frequency, switching cost, delivery cost, platform fees, and support burden.
47	- [ ] Identify implementation, data, dependency, regulation, trust, distribution, and operational blockers that affect the cost of a validation experiment.
48	- [ ] Capture source, date, evidence class, scope, confi

levnikolaevichPublisher · 19 listings

Preview

levnikolaevich/claude-code-skills

# Opportunity Evaluator

**Goal:** Evaluate product opportunities before implementation commitment. Start from observable demand and a reachable acquisition path, eliminate weak candida

**Execution contract:** Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete onl

Before returning, apply this skill's verdict, decision, and approval rules to every incomplete item and prepend **Checklist: X/Y complete**<br>**Incomplete: Non

Repolevnikolaevich/claude-code-skills

LicenseMIT

TypeSkills

CategoryPlanning

UpdatedJul 2026

Repo stars520

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type