Update to Unabyss

{
  "description": "Generate a personalized Product Hunt launch kit grounded in live product context from the Unabyss MCP (positioning, ICP, pricing, founder voice). Produces one copy-paste-ready markdown brief with tagline options, product descriptions, a maker comment, a 2-email influencer outreach sequence, an influencer materials kit, LinkedIn reshare posts for teammates/investors/network, a founder announcement post, and 1:1 support DMs. Use whenever the user mentions Product Hunt, \"PH launch,\" \"PH prep,\" \"maker comment,\" or \"launch tagline,\" or wants copy and outreach for a Product Hunt launch. Requires the Unabyss MCP.",
  "included_files": [],
  "name": "product-hunt-launch-kit",
  "skill_md_contents": "---\ncontent_hash: 7a6660fe79c0189d7034450d69d705358637499c28492f2d55c792f0192a41bf\ndescription: Generate a personalized Product Hunt launch kit grounded in live product\n  context from the Unabyss MCP (positioning, ICP, pricing, founder voice). Produces\n  one copy-paste-ready markdown brief with tagline options, product descriptions,\n  a maker comment, a 2-email influencer outreach sequence, an influencer materials\n  kit, LinkedIn reshare posts for teammates/investors/network, a founder announcement\n  post, and 1:1 support DMs. Use whenever the user mentions Product Hunt, \"PH launch,\"\n  \"PH prep,\" \"maker comment,\" or \"launch tagline,\" or wants copy and outreach for\n  a Product Hunt launch. Requires the Unabyss MCP.\nname: product-hunt-launch-kit\nversion: '1'\n---\n\n# Product Hunt Launch Kit\r\n\r\nGenerate a founder's Product Hunt launch kit as a single markdown brief. The kit is only\r\nworth producing when it's grounded in the user's actual product context — positioning,\r\nICP, pricing, and how the founder really writes. Generic launch copy already exists\r\neverywhere; the value here is that every asset reads as if it could only have been\r\nwritten for *this* product. That context comes from the **Unabyss MCP**.\r\n\r\n## Step 1 — Load context from Unabyss (required)\r\n\r\n**Before writing a single asset, query the Unabyss MCP.**\r\n\r\nUse the Unabyss `query` tool for targeted facts and `agentic_query` for synthesis\r\nacross sources. Note that `agentic_query` is asynchronous: it returns a `query_id`,\r\nand you retrieve the result by polling `agentic_query_read` — don't mistake the\r\npending acknowledgment for the answer.\r\n\r\nBatch related questions; you generally want answers to:\r\n\r\n1. **What the product is** — one-liner, what it does, the category, the core mechanism.\r\n2. **Positioning & differentiation** — the sharpest \"new way vs old way\" angle, the single\r\n   strongest differentiator, any analogies the founder already uses.\r\n3. **ICP / personas** — who it's for, the specific pain it removes, the use cases.\r\n4. **Pricing** — model, tiers, free tier/trial (shapes CTAs and any launch perk mentioned).\r\n5. **Founder voice** — how the founder actually writes (tone, rhythm, phrases, what they\r\n   avoid). If Unabyss stores a voice/style profile, pull it verbatim.\r\n6. **Proof & traction** — funding, users, notable customers, prior launches, testimonials.\r\n7. **Anything launch-relevant Unabyss already holds** — supporter lists, prior PH drafts,\r\n   influencer lists, community memberships, past launch notes. Ask broadly: \"What in my\r\n   context would help me run a Product Hunt launch?\" This often surfaces assets the user\r\n   forgot they have.\r\n\r\n**If the Unabyss tools aren't available, or the context comes back too thin to\r\npersonalize (fresh connection, few sources synced yet): stop before generating.**\r\nDon't produce generic filler — a kit built on template copy is worse than no kit,\r\nbecause the user will ship it. Explain that this skill works by pulling their real\r\npositioning, voice, and ICP from their connected context, and ask them to connect\r\nUnabyss (unabyss.com) and sync the sources where that context lives (site copy, docs,\r\nemail, Slack), then come back. Be upfront that this is the whole mechanism, not a\r\nformality.\r\n\r\n**Relaunches:** if context shows a prior PH launch, ask whether this is a relaunch.\r\nRelaunch assets must lead with what's new since last time — pull the changes from\r\ncontext rather than re-describing the product from scratch.\r\n\r\n## Step 2 — Verify current Product Hunt limits\r\n\r\nPH specs and policies change. Before finalizing page assets, run a quick web search to\r\nconfirm the current numbers. As of this writing: product name ≤ 40 characters; tagline\r\n≤ 60 characters; description ≤ 500 characters. Treat every figure as\r\nverify-before-use — if search surfaces newer numbers, use those and tell the user.\r\n\r\nCompliance, regardless of specs: Product Hunt prohibits offering anything in exchange\r\nfor upvotes. Every ask in every asset is for *feedback and support*, never votes-for-\r\nrewards. Avoid advising mass-blasting the launch link to people without PH accounts —\r\nbrand-new-account upvotes can trip spam filters and hurt the launch.\r\n\r\n## Step 3 — Produce the brief\r\n\r\nProduce a single markdown file named `<product>-ph-launch-kit.md`, with the sections\r\nbelow in this order, then present it to the user. Keep it skimmable and copy-paste\r\nready — every block should lift straight into PH, LinkedIn, or an outreach tool with\r\nminimal editing, so no meta-commentary inside the blocks themselves.\r\n\r\n### 1. Taglines (3 options, ≤ 60 chars each)\r\n\r\nThe tagline is the single most important line of the launch: it's what a stranger sees\r\nnext to the product name on the homepage, and it alone decides whether they click. It\r\nhas roughly 4 seconds to tell someone who the product is for and what they get.\r\n\r\n**How to write them.** Generate the three options from three different angles, so the\r\nuser is choosing between strategies, not synonyms:\r\n\r\n- **Outcome-led** — name the result the user walks away with, ideally the *output* of\r\n  the product, concrete enough to picture. This is usually the strongest angle.\r\n- **Mechanism-led** — name the distinctive how, the thing competitors can't say. Works\r\n  when the mechanism itself is the differentiator.\r\n- **Analogy / \"X for Y\"** — anchor to something the audience already understands. Only\r\n  use when the anchor is genuinely well-known to the ICP and the mapping is instant;\r\n  a forced analogy is worse than none.\r\n\r\n**Rules:** ≤ 60 characters. No \"best\", \"revolutionary\", \"game-changing\", or other\r\nhyperbole — PH culture reads it as noise and PH guidelines discourage it. No emojis.\r\nSpecific beats clever: a plain line that names the outcome outperforms wordplay that\r\nneeds a second read.\r\n\r\n**Quality test before presenting:** would someone who has never heard of the product\r\nknow, from the tagline alone, (a) roughly who it's for and (b) what they'd get? If\r\neither is unclear, rewrite.\r\n\r\n*Illustrative example (invented product):* for a tool that turns sales call recordings\r\ninto CRM updates, \"Your CRM updates itself after every call\" (outcome-led, 38 chars)\r\nbeats \"AI-powered sales productivity platform\" — the first is a result you can\r\npicture, the second is a category label that says nothing.\r\n\r\n**Present:** all 3 options with character counts, and mark the recommended one with a\r\none-line reason tied to the product's positioning.\r\n\r\n### 2. Product descriptions (2 options, ≤ 500 chars each)\r\n\r\nThe description sits under the tagline on the launch page and expands it for someone\r\nwho clicked. Hard cap is 500 characters, but front-load ruthlessly: in feeds and\r\npreviews the text gets truncated, so the first ~200 characters must carry the core\r\nvalue on their own.\r\n\r\n**Structure:** problem → solution → key benefit, or what-it-is → unique value → who\r\nit's for / use cases. Write for someone who knows nothing about the product. Include\r\nthe unique value proposition explicitly (the thing alternatives can't claim) and, if\r\nspace allows, one or two concrete use cases or features — named specifically, not as\r\n\"powerful features.\"\r\n\r\n**Rules:** no filler openers (\"In today's fast-paced world…\"), no repeating the\r\ntagline verbatim, no unverifiable superlatives. Every sentence should either add\r\ninformation or get cut.\r\n\r\n**Present:** 2 options with character counts — one tight (~250–300 chars, punchy) and\r\none fuller (up to 500) so the user can choose density.\r\n\r\n### 3. Maker comment\r\n\r\nThe most-read piece of content on launch day, and the one that sets the tone of the\r\nwhole comment thread. Write it in the founder's actual voice pulled from Unabyss —\r\ntheir rhythm, their phrases, their level of formality. Target 150–300 words in short\r\nparagraphs. Personal and honest; defensive or corporate tone kills it.\r\n\r\nBuild it paragraph by paragraph:\r\n\r\n1. **Who you are + what you built** — one warm first-person sentence: \"Hey PH, I'm\r\n   [name] and I built [product].\" No throat-clearing before it.\r\n2. **The story / problem** — what led to building it. The specific pain, ideally one\r\n   the founder lived themselves; a concrete moment beats an abstract market claim.\r\n   This is where authenticity is won or lost.\r\n3. **Solution & differentiator** — what the product does about it, and the one thing\r\n   that makes it different. One differentiator stated sharply beats three stated\r\n   vaguely.\r\n4. **Features as outcomes** — 2–3 concrete capabilities, each framed as what the user\r\n   gets, not what the software has. Light formatting (a short list) is fine; PH\r\n   comments support links, images, GIFs, video embeds, and basic HTML.\r\n5. **Who it's for** — name the persona and one real scenario where the product earns\r\n   its keep.\r\n6. **Demo placeholder** — insert a clearly marked placeholder for a short walkthrough\r\n   (Loom or video link/embed) and tell the user to drop theirs in. A visible demo in\r\n   the pinned comment measurably lifts engagement.\r\n7. **Genuine ask + CTA** — invite specific feedback (\"would love to hear what\r\n   surprised you or felt confusing\") and support — never ask for upvotes directly.\r\n   Include the website link.\r\n8. **Thanks + contact** — thank the community (and the hunter, if one is involved),\r\n   add one contact point: social profile or community link.\r\n\r\n**Mechanics to tell the user alongside the draft:**\r\n- The first comment on the launch gets pinned automatically — the founder must post\r\n  the maker comment before anyone else on the team comments.\r\n- Teammates can add follow-up comments in their own words (the designer on the UI, the\r\n  PM inviting feature requests) — it deepens the thread early, which helps ranking.\r\n- Thoughtful replies to critical comments often earn more goodwill than the original\r\n  post; the comment should open a conversation, not close one.\r\n\r\n**If this is a relaunch:** open with what's new since the last launch — the community\r\nhas seen the product before; the update is the story.\r\n\r\n### 4. Influencer outreach sequence (2 emails)\r\n\r\nA 2-touch email sequence to recruit influencers in the product's space for a paid\r\nlaunch collaboration. Populate the structure from the user's product context — never\r\ngenerate copy that could have been written for any product.\r\n\r\n**Personalization variables to expose:** `{{firstName}}`, `{{channel}}` (their main\r\nplatform/newsletter/YouTube), `{{topics}}` (what they cover), and the founder's name.\r\nTell the user to fill these per influencer.\r\n\r\n**Email 1 — the collab pitch:**\r\n- **Subject:** 1:1 and specific, naming the channel — e.g.\r\n  `{{channel}} collab: {{firstName}} <> [founder]`.\r\n- **Hook (first line):** open with the collaboration itself plus a one-line product\r\n  frame, and state **\"paid partnership, of course\"** early. Leading with the paid part\r\n  is what earns the reply — don't bury it.\r\n- **Why now / why them:** name the launch, say you're picking a few key partners, and\r\n  tie it to *their* specific {{topics}} so it's clearly not mass mail.\r\n- **The idea:** 2–3 punchy sentences explaining the product, ideally with a crisp\r\n  analogy the founder already uses (pull from Unabyss).\r\n- **Soft ask:** \"I'd like to understand if/how you collaborate with partners like\r\n  this\" — lower commitment than asking for a yes.\r\n- **No-friction first step:** offer to show them the product / give them a test drive.\r\n- **Close:** \"Would you be up for it?\" + founder signature (name, \"Founder @\r\n  [company]\").\r\n\r\n**Email 2 — follow-up (~1 day later, blank subject so it threads):**\r\n- Friendly bump, then **reframe the ask into 3 concrete levels** so there's an easy\r\n  yes somewhere: (1) expert feedback, (2) a testing testimonial on their {{channel}},\r\n  (3) long-term collaboration if it's a fit.\r\n- One-line product recap with a *fresh* analogy (don't repeat email 1's).\r\n- Specific CTA: a short slot this week (\"20-min call?\").\r\n- Founder sign-off.\r\n\r\n**Tone:** direct, peer-to-peer, founder-to-creator. No hype, no over-polished\r\nmarketing cadence. Short. The test-drive offer and the upfront \"paid\" framing are the\r\ntwo mechanics that make it work.\r\n\r\n### 5. Influencer materials kit\r\n\r\nWhat an influencer receives *after* they say yes. The goal is zero work for them:\r\neverything copy-paste, so posting takes 30 seconds. Assemble from the user's real\r\nproduct context. Include:\r\n\r\n1. **Product one-liner** — the tagline-grade description they can drop into any caption.\r\n2. **A 2–3 sentence \"what it is\" blurb** in plain language, with the founder's analogy.\r\n3. **Two ready-to-post drafts** they can use as-is or tweak:\r\n   - **LinkedIn version** — slightly longer, a line of personal framing (\"I've been\r\n     testing this…\") + what it does + the launch ask + link. Strong first line, short\r\n     lines.\r\n   - **X version** — tight, punchy, under the character limit, link + one clear hook.\r\n   Both must sound like the influencer endorsing it, not the founder talking.\r\n4. **Suggested visuals to attach** — name what to include (demo GIF, 1–2 key product\r\n   screenshots, the PH launch badge image). Don't fabricate assets; tell them which\r\n   to use.\r\n5. **The launch URL with a tracking placeholder** — e.g.\r\n   `?utm_source=influencer&utm_campaign=ph_launch`, swapping in the influencer's\r\n   handle, so the user can attribute traffic. Tracking parameters belong on links the\r\n   user controls — never on the product URL submitted to Product Hunt itself, which\r\n   must be a clean homepage or landing-page link.\r\n6. **One clear CTA** — a single action (visit the PH page, try the product, leave a\r\n   comment/review), framed as checking out and supporting the launch — never an\r\n   explicit ask for upvotes.\r\n\r\nKeep the whole kit short and scannable. The easier it is to paste, the more of them\r\nactually post.\r\n\r\n### 6. LinkedIn reshare posts (3 relationship tiers)\r\n\r\nShort posts *other people* can publish about the product. Organize by how well the\r\nsharer knows the founder, because that changes what's authentic for them to say:\r\n\r\n- **Tier A — close teammates / cofounders.** Personal, \"we built this\",\r\n  behind-the-scenes pride, the journey. They can speak to the work and the team.\r\n- **Tier B — investors.** Credibility and traction angle: why they backed it, what's\r\n  impressive, the bet. Measured, signal-heavy.\r\n- **Tier C — friendly network / colleagues.** Lighter: \"proud to see [friend]'s team\r\n  launch, worth a look.\" Low-commitment, warm, no insider claims they can't make.\r\n\r\nFor each tier give a ready-to-post version **and** a fill-in version (blanks for the\r\nsharer's own line) so the posts don't read identically across many feeds. Apply\r\nLinkedIn best practices throughout: a strong first line that earns the click before\r\nthe \"…see more\" fold, short 1–2 line paragraphs with whitespace, one CTA, and the\r\nlaunch link in the first comment (LinkedIn suppresses reach on posts with external\r\nlinks in the body — tell the sharers this explicitly).\r\n\r\n### 7. Founder launch-announcement post\r\n\r\nOne post for the founder's own LinkedIn profile, in their stored voice:\r\n\r\n- **First line:** a hook that works before the fold — a tension, a number, or the\r\n  \"we're live\" moment. Not \"I'm excited to announce.\"\r\n- **Body:** the why (the problem they set out to solve), what it is in one clear line,\r\n  who it's for, and a beat of honesty or humanity — the launch-day nerves, the thing\r\n  that almost didn't work.\r\n- **CTA:** invite people to check out and support the launch; the PH link goes in the\r\n  first comment, not the body.\r\n- Voice: match the founder's stored style; avoid hype words and over-polished AI\r\n  cadence.\r\n\r\n### 8. Support DMs (1:1)\r\n\r\nShort messages to send individually to existing LinkedIn connections asking them to\r\ncheck out and support the launch. These go to people the founder actually knows —\r\npersonal and low-pressure. A genuine ask outperforms a blast, and mass-identical\r\nmessages read as spam.\r\n\r\n**Shape of the base message:** first-name opener → one-line product description → a\r\nwarm, humble ask to check it out and support the launch → the link → a thank-you.\r\nKeep it a few lines total. One emoji max, and only if it fits the founder's voice.\r\nAdapt the product line and tone from the user's stored voice.\r\n\r\n**Variants by warmth (produce 2–3):**\r\n- **Close contact** — more casual, can reference shared history (\"knew you'd find\r\n  this one interesting\").\r\n- **Warm acquaintance** — the base shape, polite and brief.\r\n- **Looser tie** — slightly more context on what the product is, still short, no\r\n  presumption.\r\n\r\n**Guidance to include for the user:**\r\n- Personalize the opener for each person — don't paste identically.\r\n- Only send to people who'd plausibly have or make a PH account; spraying the link to\r\n  hundreds of non-PH users can hurt the launch via spam signals.\r\n- Send in waves through launch day, not all at once.\r\n\r\n## Step 4 — Iterate and save\r\n\r\nAfter presenting, ask the user what they'd like to refine — taglines, voice match, or\r\nany single asset — and iterate.\r\n\r\nOnce choices are settled (final tagline, launch date if known), offer to save them to\r\nthe user's context with the Unabyss `store` tool, so future sessions and other skills\r\nknow the launch details without re-asking."
}