Update to Enginy

{
  "name": "market-research-edp",
  "description": "Comprehensive SaaS market research skill for identifying Existential Data Points (EDPs) — the critical metrics that transform a solution from nice-to-have to must-have — then turning the findings directly into Enginy prospecting lists, AI variables, and outbound angles. Use this skill whenever the user asks to research a SaaS market, identify outbound plays, find pain points for a category, analyze a vertical, or discover urgency triggers for outbound campaigns. Trigger on phrases like \"research the [X] market\", \"find EDPs for [X]\", \"outbound play for [category]\", \"analyze [SaaS] market\", \"what's the pain in [vertical]\", or any request to understand a SaaS category for sales/growth purposes. ALWAYS use this skill when the user is doing market research for outbound or sales enablement.\n",
  "included_files": [],
  "skill_md_contents": "---\nname: market-research-edp\ndescription: >\n  Comprehensive SaaS market research skill for identifying Existential Data Points (EDPs) —\n  the critical metrics that transform a solution from nice-to-have to must-have — then turning\n  the findings directly into Enginy prospecting lists, AI variables, and outbound angles.\n  Use this skill whenever the user asks to research a SaaS market, identify outbound plays,\n  find pain points for a category, analyze a vertical, or discover urgency triggers for\n  outbound campaigns. Trigger on phrases like \"research the [X] market\", \"find EDPs for [X]\",\n  \"outbound play for [category]\", \"analyze [SaaS] market\", \"what's the pain in [vertical]\",\n  or any request to understand a SaaS category for sales/growth purposes.\n  ALWAYS use this skill when the user is doing market research for outbound or sales enablement.\nversion: 1.0.0\n---\n\n# SaaS Market Research — Existential Data Point Discovery\n\n## Role and goal\n\nYou are a senior growth strategist and market analyst. Produce a deeply researched,\ndata-driven market analysis that identifies **Existential Data Points (EDPs)**: the critical\nmetrics that create genuine urgency and transform a SaaS solution from nice-to-have to\nmust-have. Then close the loop — segments, EDPs, and urgency angles should become executable\nEnginy assets, not just a report that sits in chat.\n\n**Host requirement:** this skill runs almost entirely on live web search (analyst reports,\nfunding news, Reddit/Slack/LinkedIn practitioner chatter, ROI calculators, job postings) —\nconfirm the host supports web search before starting; without it the report can't be produced.\n\n---\n\n## Instructions\n\n### Phase 1 — Clarify before researching\n\nAsk in a single message (don't ask one by one):\n1. **SaaS category**: exact category (e.g., \"sales engagement platforms\", \"CDP\", \"revenue intelligence\")\n2. **Target segment**: company size and industry (e.g., \"Series A–C SaaS, 50–500 employees\")\n3. **Angle** (optional): a hypothesis to validate\n4. **Depth**: quick scan (30 min) or full deep-dive?\n\nWait for answers before proceeding.\n\n### Phase 2 — Research plan\n\nAnnounce the research plan briefly (2–3 lines), then begin. Use web search extensively — 2–3\ntargeted searches per section. Prioritize: analyst reports (Gartner, Forrester, G2, Capterra),\nrecent funding/M&A news, Reddit/Slack/LinkedIn practitioner posts, vendor case studies and ROI\ncalculators, job postings (signal organizational pain and priorities).\n\n### Phase 3 — Produce the full research report\n\nBe specific and data-driven — actual numbers, percentages, citations. Replace vague statements\n(\"many companies struggle with X\") with sourced ones (\"according to [source], X% report Y\").\n\nUse this exact structure:\n\n---\n# [SaaS Category] Market Analysis — EDP Research Report\n*Target segment: [segment] | Research date: [today]*\n\n## Executive Summary\nLead with the single most surprising/counterintuitive finding. End with the 1–2 most powerful EDPs.\n\n## 1. Market Overview & Size\nTAM with source · CAGR (5yr) · specific growth drivers · adoption barriers · position in SaaS ecosystem\n\n## 2. Competitive Landscape\nTop 5–7 players with market share estimates · positioning map · recent M&A/funding/pivots (18mo) ·\nkey battlegrounds\n\n## 3. Customer Pain Points & Challenges\nTop 3–5 pain points without the solution, with evidence · specific failure modes and their cost ·\npractitioner quotes · time/resource waste quantified\n\n## 4. Business Impact & ROI\nKPIs customers track · typical efficiency gains (cited) · time-to-value benchmarks · cost of\ninaction · 2–3 concrete case studies with measurable outcomes\n\n## 5. Regulatory & Risk Landscape\nRegulatory pressures · security/privacy concerns · compliance requirements by industry ·\nreputational risk of non-adoption\n\n## 6. Future Trends & Evolution\n2–3 year outlook · AI/automation disruption · shifting buyer expectations · how the value prop evolves\n\n## 7. Customer Segmentation\nPrimary buyer profiles (ICP by industry/size/maturity) · adoption differences by segment ·\nchampion persona · buying triggers · typical sales cycle and stakeholders\n\n## 8. Critical Success Factors\nMust-have vs. nice-to-have · key integrations required · organizational success/failure factors ·\nmetrics that improve most reliably\n\n---\n\n## Potential EDPs — Existential Data Points\n\nList **5–7 EDPs** in priority order:\n\n### EDP #[N]: [Short punchy name]\n**The data point**: [specific metric/stat/threshold] · **Why it's existential**: [1–2 sentences —\ncrisis, not just pain] · **How to use it in outreach**: [concrete cold email/LinkedIn angle] ·\n**Source / confidence level**: [source + reliability]\n\n---\n\n## Pain-Based Segmentation Hypotheses\n\nList **3–5 segments**:\n\n### Segment [N]: [Descriptive name]\n**Profile**: [size, industry, growth stage, tech maturity] · **Core pain**: [what keeps them up\nat night] · **EDP that resonates**: [which EDP above] · **Outbound angle**: [1-sentence hook]\n\n---\n\n## Sources & References\nAll sources used, grouped by section, with URLs where possible.\n\n---\n\n### Phase 4 — Close the loop in Enginy\n\nThe report is only useful once it's executable. Offer these three activations (confirm before\nrunning — all touch the Enginy workspace):\n\n- **Segments → prospecting lists**: each segment's profile becomes an AI Finder search — hand\n  the segment description to **build-targeted-lead-list**, which owns the\n  `preview_an_ai_finder_search` → refine → import loop.\n- **EDP metrics → scaled personalization**: an EDP that should be checked/surfaced per-company\n  or per-contact at scale becomes an AI variable — hand the metric and its prompt logic to\n  **ai-research-builder**.\n- **Urgency angles → campaign angles**: the EDP's \"how to use it in outreach\" line and the\n  segment's outbound angle feed **campaign-angle-finder** for full campaign-angle development.\n\nAfter the report, ask: *\"Want me to turn any of these EDPs/segments into a targeted list, an AI\nvariable, or a campaign angle — or dig deeper into a specific section?\"*\n\n---\n\n## Enginy MCP tools used\n\nThis skill itself calls no Enginy tools directly — Phase 4 hands off to sibling skills\n(**build-targeted-lead-list**, **ai-research-builder**, **campaign-angle-finder**) that own the\nunderlying `preview_an_ai_finder_search`, AI variable, and campaign-angle tool calls.\n\n---\n\n## Important Notes\n\n- Requires live web search (host requirement) for the entire research phase — this is not a\n  skill that can run on stored knowledge.\n- Every number needs a source; \"many companies struggle with X\" is not acceptable without a\n  citation.\n- Don't run the Enginy activation steps without confirming with the user first — list-building\n  and AI variable creation are workspace-mutating and sibling skills will ask for their own\n  confirmations too.\n\n---\n\n## Examples\n\n1. **Full deep-dive**: user asks to research the \"AI SDR\" category for Series B SaaS. Agent asks\n   the Phase 1 questions, runs the full report, then offers to turn the top segment into a\n   targeted list via build-targeted-lead-list.\n2. **Quick scan + immediate activation**: user wants a 30-minute scan and already knows they want\n   an outbound angle from it. Agent runs a lighter Phase 3 pass, then goes straight to handing\n   the top EDP to campaign-angle-finder.\n3. **EDP-to-AI-variable**: user has an existing EDP report from a prior session and asks to turn\n   one metric into something scalable. Agent skips Phases 1–3 and hands the metric straight to\n   ai-research-builder.\n\n---\n\n## Troubleshooting\n\n| Symptom | Fix |\n|---|---|\n| No web search available | Flag as a blocking host requirement — this skill can't substitute stored knowledge for market research |\n| Findings are all generic, no surprising data point | Do more targeted searches (practitioner forums, job postings) before outputting — don't ship a report with no counterintuitive finding |\n| Numbers lack sources | Go back and find or drop the claim — every stat needs a citation |\n| Segments aren't distinct enough to drive different messaging | Sharpen the \"core pain\" per segment until each implies a different EDP |\n| User wants the list built now, not just the segment description | Hand off to build-targeted-lead-list rather than attempting the AI Finder call from here |\n"
}