← ClaudeAtlas

differentiationlisted

Use after VOC_ANALYSIS state to assess whether a candidate has a real, evidence-backed moat versus competitors. Drives differentiation-prepare/differentiation-submit.
zaidadaqqa/amazon-opportunity-research-skills · ★ 1 · Code & Development · score 72
Install: claude install-skill zaidadaqqa/amazon-opportunity-research-skills
# Differentiation Assess whether this candidate has a genuine, defensible advantage over competitors — grounded strictly in evidence already in the Evidence Ledger. Never invent a moat claim without a citation: per `references/differentiation.md` §2, the engine forcibly collapses any ungrounded moat claim to `LOW_COPYCAT_RESISTANCE` with `moat_categories=[]` regardless of what was submitted, so an ungrounded claim only wastes a turn — it never survives into the persisted result. ## When to use this Opportunity is in state `VOC_ANALYSIS` (after `reddit-voc` or automated `voc-submit` completed). ## Steps 1. **Get the prompt.** ``` hunt differentiation-prepare <opportunity_id> ``` This requires `VOC_ANALYSIS` state and prints the system+user prompt. 2. **Build the `DifferentiationAssessment` JSON, grounded only in real evidence_ids.** Draw only on evidence already in the Evidence Ledger: - VOC findings (from `voc-submit` or `voc-add`) — a repeated, solvable pain point competitors haven't addressed is real differentiation evidence. - Competitor autopsy notes (`competition-analysis` output) — e.g. genuinely fragmented, low-quality competition with a specific addressable gap. - Browser research findings (`hunt browser-evidence-add` output, if collected) — e.g. a verified pattern in what competitors' own listings /pages claim vs. what they lack. - Every moat claim in the JSON must cite the `evidence_id`(s) it is act