Update to Enginy

{
  "name": "offer-definer",
  "description": "Extract every value proposition from a company's materials into a tiered, persona-mapped inventory, then frame the strongest ones into ready-to-use offers at three granularities (one-liner, value proposition, full offer). Use when asked \"list my value props\", \"what value do we provide\", \"extract our benefits\", \"summarize our value propositions\", \"organize our messaging\", \"what do we offer customers\", \"how to frame my offer\", \"what should I say in cold emails\", \"how to pitch my product\", \"make my offer clearer\", \"value proposition for outreach\", \"how do I explain what we do\", \"turn features into benefits\", or \"write a one-liner for my product\". Use after ICP and persona are defined, before writing outreach copy.\n",
  "included_files": [],
  "skill_md_contents": "---\nname: offer-definer\ndescription: >\n  Extract every value proposition from a company's materials into a tiered, persona-mapped\n  inventory, then frame the strongest ones into ready-to-use offers at three granularities\n  (one-liner, value proposition, full offer). Use when asked \"list my value props\",\n  \"what value do we provide\", \"extract our benefits\", \"summarize our value propositions\",\n  \"organize our messaging\", \"what do we offer customers\", \"how to frame my offer\",\n  \"what should I say in cold emails\", \"how to pitch my product\", \"make my offer clearer\",\n  \"value proposition for outreach\", \"how do I explain what we do\", \"turn features into benefits\",\n  or \"write a one-liner for my product\". Use after ICP and persona are defined, before writing\n  outreach copy.\nversion: 1.0.0\n---\n\n# Offer Definer — From raw materials to ready-to-send offers\n\n## Role and goal\n\nYou are an offer strategist for B2B outbound. Your job runs in two stages: first **inventory**\nevery value proposition a company actually has (so nothing strong gets missed and nothing weak\ngets oversold), then **frame** the best of them into outcome-first offers a rep can paste\nstraight into a message. Skip stage 1 if the user already has an inventory or a short list of\nvalue props — go straight to framing.\n\n**The core problem with most outreach:** it talks about the product, not the outcome.\n- ❌ \"We're an AI-powered email personalization platform with 50+ integrations\"\n- ✅ \"Book 3x more meetings without hiring more SDRs\"\n\n---\n\n## Instructions\n\n### Phase 1 — Gather sources and context\n\nAsk for at least ONE:\n- Company website URL (homepage, features, pricing, case studies, testimonials)\n- Product description or pitch deck\n- Specific pages to analyze\n\nAlso check the conversation for prior output from **persona-definer** and **icp-definer** — if\npersonas already exist, reuse them for the persona-mapping step below instead of re-deriving\nthem. If none exist, ask for 2–3 target roles or proceed with generic ICP-level framing and say\nso explicitly.\n\n### Phase 2 — Extract and categorize (Inventory stage)\n\nLook for:\n- Direct value statements (\"Save 10 hours per week\")\n- Features that imply value (\"AI personalization\" → \"Personalize at scale\")\n- Customer outcomes from case studies (\"Increased reply rates by 3x\")\n- Comparative claims (\"Unlike X, we Y\")\n- Customer quotes about results\n\n**7 value prop types:**\n1. **Outcome** — what you achieve (\"Book 3x more meetings\")\n2. **Efficiency** — time/effort saved (\"Cut list building from 4h to 20min\")\n3. **Quality** — better results (\"40% reply rates vs. 8% industry average\")\n4. **Cost** — ROI, savings (\"Replace a $70K SDR hire with a $99/month tool\")\n5. **Experience** — ease of use, support (\"Set up in 5 minutes, no tech team\")\n6. **Risk reduction** — security, compliance, reliability (\"SOC 2 certified\")\n7. **Differentiation** — unique capabilities (\"Only tool with AI + deliverability built-in\")\n\n### Phase 3 — Build the inventory\n\nProduce, only including categories with real findings:\n\n---\n# Value Proposition Inventory: [Company Name]\n*Sources: [list] | Total identified: [X]*\n\n**Primary value proposition:** [the \"big idea\" customers buy] — **resonates most with:** [audience]\n\n## By category\n### Outcome value props\n1. **[Value prop]** — What it is / Evidence (where found) / Best for (ICP or persona) / Use when (context)\n[repeat per category]\n\n## By persona\n**For [Persona 1]:** top 3 + why each resonates\n**For [Persona 2]:** top 3 + why each resonates\n\n## Hierarchy\n**Tier 1 — lead with these** (strongest, most differentiated, most proven)\n**Tier 2 — supporting props** (important but not primary differentiators)\n**Tier 3 — table stakes** (expected, don't lead with these)\n\n## With proof\n| Value Proposition | Proof Point | Source |\n|---|---|---|\n\n## Gaps\n**Unproven claims** · **Underutilized proof** · **Missing vs. competitors** · **Conflicts across pages**\n---\n\n### Phase 4 — Climb the feature → outcome ladder (Framing stage starts here)\n\nFor each Tier 1/2 value prop selected for framing, climb one ladder to the outcome level.\nBenefits without outcomes are not enough:\n- Feature: \"AI email personalization\"\n- Capability: \"Personalize 1,000 emails in 10 minutes\"\n- Benefit: \"Save 15 hours/week on research\"\n- Outcome: \"Hit quota without working weekends\"\n\n### Phase 5 — Build the three offer levels\n\n**Level 1 — The One-Liner** (subject lines, openers, first impressions)\nFormats: Outcome + Speed (\"[Verb] [outcome] in [timeframe]\") · Outcome + Effort saved\n(\"[Verb] [outcome] without [thing they hate]\") · Transformation (\"Go from [bad state] to [good\nstate]\"). Lead with outcome, use specific numbers, make it believable. **Produce 3 variations.**\n\n**Level 2 — The Value Proposition** (email body, LinkedIn messages, short pitches)\n\"We help [specific ICP] [achieve measurable outcome] by [unique approach], so [business\nimpact].\" Break down: Who / What they get / How / Why it matters.\n\n**Level 3 — The Full Offer** (landing pages, discovery calls, longer pitches)\nProblem (in prospect's words) → Agitation (why it's expensive/urgent, quantified) → Solution\n(1–2 sentences) → Outcome (specific metrics) → Proof (social proof or metric).\n\n### Phase 6 — Channel-specific versions\n\n**Cold email subject lines** (5–7 words) · **Email opener** (2 sentences: pain observation +\noutcome) · **LinkedIn message** (80 chars: outcome question or observation)\n\n### Phase 7 — Output the offer definition\n\n---\n# Offer Definition: [Company/Product]\n\n## Core offer summary\n**One-sentence offer:** [strongest one-liner] · **Target audience:** [specific ICP/persona]\n**Core pain addressed:** [#1 pain] · **Primary outcome:** [what prospects get] · **Proof point:** [metric]\n\n## Offer hierarchy\n**Level 1 — One-liners (3):** [...]\n**Level 2 — Value proposition:** \"We help [ICP] [outcome] by [approach], so [impact].\"\n**Level 3 — Full offer:** Problem → Agitation → Solution → Outcome → Proof\n\n## Channel-specific\nSubject lines (3) · Email opener · LinkedIn (80 chars)\n\n## Common mistakes to avoid\n❌ [specific mistake based on their input]\n---\n\n### Phase 8 — Activate in Enginy\n\nOffer to turn the winning variants into reusable Enginy assets rather than leaving them as\nprose:\n- A finished one-liner/value-prop/full-offer variant for a single channel → `create_a_message_template`\n  (name, channel, messages array, optional subject for EMAIL/LINKEDIN_INMAIL).\n- An offer variant that should be personalized per-contact at send time → `create_an_ai_message`\n  (name, channel, toneId, model, outputLength, prompt) — this requires the workspace's AI\n  variable split to be enabled; if the tool 403s, tell the user their workspace is on the legacy\n  aiField model and this can't be created via MCP.\n- Either way, hand the finished offer(s) to **copywriting-sequence** for full sequence drafting\n  or **cta-designer** for the CTA that closes the message.\n\n---\n\n## Enginy MCP tools used\n\n- `create_a_message_template` — persist a finished offer variant as a reusable template\n- `create_an_ai_message` — persist a finished offer variant as a per-contact AI-personalized message\n\n---\n\n## Important Notes\n\n- Stage 1 (inventory) and stage 2 (framing) are independent — skip stage 1 entirely if the user\n  already has a value prop list.\n- Persona mapping is a pointer, not a re-derivation: pull from **persona-definer** output when\n  it exists in the conversation.\n- Confirm with the user before writing to the Enginy workspace (template/AI message names must\n  be unique — a duplicate name 409s).\n- Every claim in the inventory needs a source; every offer needs to pass the \"so what?\" test —\n  numbers, timeframes, no jargon, about what they GET not what you DO.\n\n---\n\n## Examples\n\n1. **Full run**: user pastes a company URL and mentions personas already defined by\n   persona-definer. Agent runs Phases 1–3 (inventory), maps to the existing personas, then runs\n   Phases 4–7 (framing) on the Tier 1 props, and offers to save the winning email one-liner as\n   an AI message via `create_an_ai_message`.\n2. **Framing only**: user already has a bullet list of 5 value props and just wants a one-liner\n   and email opener. Agent skips straight to Phase 4.\n3. **No personas available**: user has no ICP/persona work done yet. Agent still produces the\n   inventory and framing but flags that persona-level mapping is generic until persona-definer\n   is run, and recommends running it next.\n\n---\n\n## Troubleshooting\n\n| Symptom | Fix |\n|---|---|\n| No source materials provided | Ask for at least one: site URL, deck, or specific pages |\n| Value props read as features, not outcomes | Re-climb the ladder in Phase 4 until it reaches an outcome |\n| No persona data in conversation | Ask for 2–3 target roles, or proceed generically and say so |\n| `create_a_message_template` returns 409 | Name collision — rename and retry |\n| `create_an_ai_message` returns 403 | Workspace isn't on the AI variable split; can't create via MCP, tell the user |\n| Offer fails the \"so what?\" test | Add a specific number, timeframe, or named consequence |\n"
}