[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FMMNNK92JWSC7YHA06VBMX":3,"skill-same:01M6FMMNNK92JWSC7YHA06VBMX":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6FMMNNK92JWSC7YHA06VBMX","follow-up-generator",null,"Generate personalized post-event follow-ups for founders: the 2-day, 2-week, and 2-month check-ins that reference each founder's own commitments, numbers, and path. Use after the event, per startup.","stealthxco\u002Ffounderjamskills","stealthxco","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F172341267?v=4","01M6CPBW6VADDD6ABHPP7TR7ZA","Drew Burdick","01M6CPBWB1MV2YYQDZ54N1BBRM",4,"CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fsherpa\u002Ffollow-up-generator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"up","follow up","generator","follow up generator","generate","startup","check","use","reference","founder","post","event","founders","follow-ups","2026-11-10 10:12:30",false,"---\nname: follow-up-generator\ndescription: \"Generate personalized post-event follow-ups for founders: the 2-day, 2-week, and 2-month check-ins that reference each founder's own commitments, numbers, and path. Use after the event, per startup.\"\nlicense: CC-BY-4.0\n---\n\n# Follow-Up Generator\n\nPost-event skill for sherpas. Generate three ready-to-send follow-up messages per founder, personalized to their specific commitments, metrics, and selections from the workshop.\n\n## Overview\n\nThis skill produces three messages:\n1. **2-Day check-in**: accountability nudge while commitments are fresh\n2. **2-Week milestone**: progress check against specific targets\n3. **2-Month validation gate**: Green \u002F Yellow \u002F Red assessment against the 2-month commitment\n\n**When to run:** After the event, using notes from each startup's validation planner output. Run once per startup.\n\n## Process\n\n### Step 1: Input collection\n\nAsk the sherpa for the following information about one startup. Collect everything before generating messages.\n\nIf the founder shared their FOUNDER JAM HANDOFF block (the format is defined in the `founder-setup` skill; if `founder-setup` is not installed, the same format is in `HANDOFF-FORMAT.md` next to this file), read `startup_name`, `path`, `icp_segment`, `hypothesis_selected`, `lead_magnet`, `outbound_system`, and `channels_selected` from it and confirm them instead of asking again.\n\n**Questions to ask (in order):**\n\n1. \"What's the startup name?\"\n   -> `startup_name`\n\n2. \"What's the founder's first name?\"\n   -> `founder_first_name`\n\n3. \"Which path did they pick in Focus? (product and positioning, GTM and growth, sales, ops and automation, or undecided)\"\n   -> `path`\n\n   If they left undecided, skip the path-specific language in Step 2 and use the words that fit what they built.\n\n   On ops and automation, also ask: \"Was it an internal or support process, or go-to-market work like lead enrichment?\"\n   -> `process_type`\n\n4. \"What were their 3 commitments from the validation planner?\"\n   - 2-day commitment: [specific action]\n   - 2-week commitment: [specific action with a number]\n   - 2-month commitment: [specific outcome with a number]\n   -> `commitment_2day`, `commitment_2week`, `commitment_2month`\n\n   If the 2-week or 2-month commitment has no number, ask: \"What number would count as hitting it?\" Message 2 checks progress against `thirty_day_target`, and Message 3 grades against the 2-month commitment's number.\n\n5. \"What were their Week 1 actions from the 30-day plan? List 3-5 specific actions.\"\n   -> `week1_actions[]`\n\n   Only founders who ran `growth-builder` have a 30-day plan. If they did not (the usual case on the product and positioning and sales paths), don't ask for a 30-day plan. Use the 2-day commitment as the first action and ask for 2 more steps they planned for the first week, so there are 3 actions in all.\n\n6. \"What was their Week 2 success criteria? Give me the specific metrics or milestones they wrote down.\"\n   -> `week2_milestones[]`\n\n   Without a 30-day plan, use the 2-week commitment as the first milestone, with its number as the metric, and ask for one more thing they expect to have done by week 2, so there are 2 milestones.\n\n7. \"What specific number did they set as their 30-day target? (e.g., 50 landing page visitors, 10 email signups, 3 discovery calls)\"\n   -> `thirty_day_target`\n\n   Without a 30-day plan, don't ask. Use the number from the 2-week commitment.\n\n8. \"What was their North Star metric and target number? (Expected on GTM and growth, sales, and ops and automation; optional on product and positioning)\"\n   -> `north_star_metric`, `north_star_target`\n\n9. \"What hypothesis or ICP did they select?\"\n   -> `hypothesis_or_icp`\n\n10. \"What did they build? (a prototype, a lead magnet and sequence, an outbound system, or an automation)\"\n    -> `artifact_built`\n\n11. \"Which channels did they select?\"\n    -> `channels_selected[]`\n\n12. \"What's your name? (The sherpa's first name)\"\n    -> `sherpa_name`\n\nIf any required field is missing, ask for it before generating messages. Do not generate with empty personalization tokens.\n\n### Step 2: Generate 3 messages\n\nGenerate all three messages using the `templates\u002Ffollow-up-messages.md` format.\n\n**Requirements for each message:**\n- Founder's first name (not \"Hi there\" or generic opening)\n- Specific numbers from their commitments: not generic percentages or vague language\n- Specific actions they said they would take, pulled directly from their 30-day plan (without one, from their validation-planner commitments and the extra steps they named in Step 1)\n- Path-specific language:\n  - Product and positioning: use \"hypothesis,\" \"prototype,\" \"validate,\" \"test\"\n  - GTM and growth: use \"ICP,\" \"lead magnet,\" \"sequence,\" \"pipeline\"\n  - Sales: use \"prospects,\" \"replies,\" \"calls,\" \"pipeline\"\n  - Ops and automation: use \"workflow,\" \"automation,\" \"hours saved,\" \"handoff\"\n- No em dashes\n- Plain text only: no markdown formatting in the messages themselves\n\n**Message 1: 2-Day Check-In**\n\nFill the template with:\n- `[Founder Name]` -> `founder_first_name`\n- `[Day]` -> day of week the event was held (ask if not known)\n- `[specific commitment from validation planner]` -> `commitment_2day`\n- `[Week 1 action 1-3]` -> first 3 items from `week1_actions[]`\n- `[Sherpa Name]` -> `sherpa_name`\n\n**Message 2: 2-Week Milestone**\n\nFill the template with:\n- `[Founder Name]` -> `founder_first_name`\n- `[specific metric]` -> the primary metric from `week2_milestones[0]`\n- `[Week 2 milestone 1-2]` -> first 2 items from `week2_milestones[]`\n- `[specific number from 30-day plan]` -> `thirty_day_target`\n- `[Sherpa Name]` -> `sherpa_name`\n\n**Message 3: 2-Month Validation Gate**\n\nFill the template with:\n- `[Founder Name]` -> `founder_first_name`\n- `[2-month commitment]` -> `commitment_2month`\n- `[specific metric]` -> `north_star_metric`\n- `[specific number]` -> `north_star_target`\n- `[Sherpa Name]` -> `sherpa_name`\n\nThe 2-month commitment is the validation gate, so grade against its number, even when a North Star target exists and differs. The North Star line is context only. If no North Star metric was captured (common on product and positioning), leave that line out and note the omission in a sherpa comment above the message.\n\nOn ops and automation with an internal or support process, replace the Red line with: \"Red (under 40%): Time to revisit the process. Talk to 3-5 people who tried it and stopped, then re-scope the process, fix the step where adoption stalls, or pick a different process to automate.\"\n\n### Step 3: Personalization check\n\nBefore presenting messages, verify:\n\n- [ ] No template tokens remain (no `[brackets]` in any message)\n- [ ] All numbers are specific (not \"your target\" without a number)\n- [ ] Path-specific language is used correctly\n- [ ] Founder's name appears in each message\n- [ ] Sherpa's name appears at the end of each message\n- [ ] Messages are plain text (no asterisks, no markdown bullets)\n\nIf any check fails, fix before presenting.\n\n### Step 4: Output\n\nPresent the three messages in sequence with clear labels:\n\n```\n--- MESSAGE 1: Send within 48 hours ---\n\n[message text]\n\n--- MESSAGE 2: Send in 14 days ---\n\n[message text]\n\n--- MESSAGE 3: Send in 60 days ---\n\n[message text]\n```\n\nAfter output, ask: \"Would you like messages for another startup?\"\n\nIf yes, return to Step 1.\n\n## Context\n\n**Reads:** Nothing.\n**Writes:** Nothing. The sherpa copies messages directly to email.\n\n## Where this runs\n\n| Where | What happens |\n|-------|--------------|\n| claude.ai or Claude desktop (skill uploaded) | Full flow. Output is text in the chat; copy what you want to keep. |\n| Claude Code | Full flow. May write a file on request. |\n\n## Timing reminders\n\n- **Message 1:** Send within 48 hours of the event, ideally the evening of or morning after.\n- **Message 2:** Send exactly 14 days post-event. Set a calendar reminder before you leave.\n- **Message 3:** Send approximately 60 days post-event.\n- If a founder replies to an earlier message, acknowledge their update and skip the scheduled message if it's redundant.\n\n---\n\nFounder Jam curriculum and skills by Drew Burdick · program co-created with Innovate Charlotte · CC BY 4.0 · drewburdick.com\u002Ffounderjam\n","# Follow-Up Generator\n\nPost-event skill for sherpas. Generate three ready-to-send follow-up messages per founder, personalized to their specific commitments, metrics, and selections from the workshop.\n\n## Overview\n\nThis skill produces three messages:\n1. **2-Day check-in**: accountability nudge while commitments are fresh\n2. **2-Week milestone**: progress check against specific targets\n3. **2-Month validation gate**: Green \u002F Yellow \u002F Red assessment against the 2-month commitment\n\n**When to run:** After the event, using notes from each startup's validation planner output. Run once per startup.\n\n## Process\n\n### Step 1: Input collection\n\nAsk the sherpa for the following information about one startup. Collect everything before generating messages.\n\nIf the founder shared their FOUNDER JAM HANDOFF block (the format is defined in the `founder-setup` skill; if `founder-setup` is not installed, the same format is in `HANDOFF-FORMAT.md` next to this file), read `startup_name`, `path`, `icp_segment`, `hypothesis_selected`, `lead_magnet`, `outbound_system`, and `channels_selected` from it and confirm them instead of asking again.\n\n**Questions to ask (in order):**\n\n1. \"What's the startup name?\"\n   -> `startup_name`\n\n2. \"What's the founder's first name?\"\n   -> `founder_first_name`\n\n3. \"Which path did they pick in Focus? (product and positioning, GTM and growth, sales, ops and automation, or undecided)\"\n   -> `path`\n\n   If they left undecided, skip the path-specific language in Step 2 and use the words that fit what they built.\n\n   On ops and automation, also ask: \"Was it an internal or support process, or go-to-market work like lead enrichment?\"\n   -> `process_type`\n\n4. \"What were their 3 commitments from the validation planner?\"\n   - 2-day commitment: [specific action]\n   - 2-week commitment: [specific action with a number]\n   - 2-month commitment: [specific outcome with a number]\n   -> `commitment_2day`, `commitment_2week`, `commitment_2month`\n\n   If the 2-week or 2-month commitment has no number, ask: \"What number would count as hitting it?\" Message 2 checks progress against `thirty_day_target`, and Message 3 grades against the 2-month commitment's number.\n\n5. \"What were their Week 1 actions from the 30-day plan? List 3-5 specific actions.\"\n   -> `week1_actions[]`\n\n   Only founders who ran `growth-builder` have a 30-day plan. If they did not (the usual case on the product and positioning and sales paths), don't ask for a 30-day plan. Use the 2-day commitment as the first action and ask for 2 more steps they planned for the first week, so there are 3 actions in all.\n\n6. \"What was their Week 2 success criteria? Give me the specific metrics or milestones they wrote down.\"\n   -> `week2_milestones[]`\n\n   Without a 30-day plan, use the 2-week commitment as the first milestone, with its number as the metric, and ask for one more thing they expect to have done by week 2, so there are 2 milestones.\n\n7. \"What specific number did they set as their 30-day target? (e.g., 50 landing page visitors, 10 email signups, 3 discovery calls)\"\n   -> `thirty_day_target`\n\n   Without a 30-day plan, don't ask. Use the number from the 2-week commitment.\n\n8. \"What was their North Star metric and target number? (Expected on GTM and growth, sales, and ops and automation; optional on product and positioning)\"\n   -> `north_star_metric`, `north_star_target`\n\n9. \"What hypothesis or ICP did they select?\"\n   -> `hypothesis_or_icp`\n\n10. \"What did they build? (a prototype, a lead magnet and sequence, an outbound system, or an automation)\"\n    -> `artifact_built`\n\n11. \"Which channels did they select?\"\n    -> `channels_selected[]`\n\n12. \"What's your name? (The sherpa's first name)\"\n    -> `sherpa_name`\n\nIf any required field is missing, ask for it before generating messages. Do not generate with empty personalization tokens.\n\n### Step 2: Generate 3 messages\n\nGenerate all three messages using the `templates\u002Ffollow-up-messages.md` format.\n\n**Requirements for each message:**\n- Founder's first name (not \"Hi there\" or generic opening)\n- Specific numbers from their commitments: not generic percentages or vague language\n- Specific actions they said they would take, pulled directly from their 30-day plan (without one, from their validation-planner commitments and the extra steps they named in Step 1)\n- Path-specific language:\n  - Product and positioning: use \"hypothesis,\" \"prototype,\" \"validate,\" \"test\"\n  - GTM and growth: use \"ICP,\" \"lead magnet,\" \"sequence,\" \"pipeline\"\n  - Sales: use \"prospects,\" \"replies,\" \"calls,\" \"pipeline\"\n  - Ops and automation: use \"workflow,\" \"automation,\" \"hours saved,\" \"handoff\"\n- No em dashes\n- Plain text only: no markdown formatting in the messages themselves\n\n**Message 1: 2-Day Check-In**\n\nFill the template with:\n- `[Founder Name]` -> `founder_first_name`\n- `[Day]` -> day of week the event was held (ask if not known)\n- `[specific commitment from validation planner]` -> `commitment_2day`\n- `[Week 1 action 1-3]` -> first 3 items from `week1_actions[]`\n- `[Sherpa Name]` -> `sherpa_name`\n\n**Message 2: 2-Week Milestone**\n\nFill the template with:\n- `[Founder Name]` -> `founder_first_name`\n- `[specific metric]` -> the primary metric from `week2_milestones[0]`\n- `[Week 2 milestone 1-2]` -> first 2 items from `week2_milestones[]`\n- `[specific number from 30-day plan]` -> `thirty_day_target`\n- `[Sherpa Name]` -> `sherpa_name`\n\n**Message 3: 2-Month Validation Gate**\n\nFill the template with:\n- `[Founder Name]` -> `founder_first_name`\n- `[2-month commitment]` -> `commitment_2month`\n- `[specific metric]` -> `north_star_metric`\n- `[specific number]` -> `north_star_target`\n- `[Sherpa Name]` -> `sherpa_name`\n\nThe 2-month commitment is the validation gate, so grade against its number, even when a North Star target exists and differs. The North Star line is context only. If no North Star metric was captured (common on product and positioning), leave that line out and note the omission in a sherpa comment above the message.\n\nOn ops and automation with an internal or support process, replace the Red line with: \"Red (under 40%): Time to revisit the process. Talk to 3-5 people who tried it and stopped, then re-scope the process, fix the step where adoption stalls, or pick a different process to automate.\"\n\n### Step 3: Personalization check\n\nBefore presenting messages, verify:\n\n- [ ] No template tokens remain (no `[brackets]` in any message)\n- [ ] All numbers are specific (not \"your target\" without a number)\n- [ ] Path-specific language is used correctly\n- [ ] Founder's name appears in each message\n- [ ] Sherpa's name appears at the end of each message\n- [ ] Messages are plain text (no asterisks, no markdown bullets)\n\nIf any check fails, fix before presenting.\n\n### Step 4: Output\n\nPresent the three messages in sequence with clear labels:\n\n```\n--- MESSAGE 1: Send within 48 hours ---\n\n[message text]\n\n--- MESSAGE 2: Send in 14 days ---\n\n[message text]\n\n--- MESSAGE 3: Send in 60 days ---\n\n[message text]\n```\n\nAfter output, ask: \"Would you like messages for another startup?\"\n\nIf yes, return to Step 1.\n\n## Context\n\n**Reads:** Nothing.\n**Writes:** Nothing. The sherpa copies messages directly to email.\n\n## Where this runs\n\n| Where | What happens |\n|-------|--------------|\n| claude.ai or Claude desktop (skill uploaded) | Full flow. Output is text in the chat; copy what you want to keep. |\n| Claude Code | Full flow. May write a file on request. |\n\n## Timing reminders\n\n- **Message 1:** Send within 48 hours of the event, ideally the evening of or morning after.\n- **Message 2:** Send exactly 14 days post-event. Set a calendar reminder before you leave.\n- **Message 3:** Send approximately 60 days post-event.\n- If a founder replies to an earlier message, acknowledge their update and skip the scheduled message if it's redundant.\n\n---\n\nFounder Jam curriculum and skills by Drew Burdick · program co-created with Innovate Charlotte · CC BY 4.0 · drewburdick.com\u002Ffounderjam\n",{"name":5,"license":15,"description":7},"main","a4461fb3a0db8de239d78627ef95d4ab0112dec7","skills\u002Fsherpa\u002Ffollow-up-generator",1,"https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills","https:\u002F\u002Fgithub.com\u002Fstealthxco","stealthx.co","2026-11-02 11:15:39",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add stealthxco\u002Ffounderjamskills --skill follow-up-generator",{"tool":52,"command":53},"bunx","bunx skills add stealthxco\u002Ffounderjamskills --skill follow-up-generator",{"tool":55,"command":56},"pnpm","pnpm dlx skills add stealthxco\u002Ffounderjamskills --skill follow-up-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fsherpa\u002Ffollow-up-generator\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"templates\u002Ffollow-up-messages.md","REFERENCE","参考文档",3659,"https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fsherpa\u002Ffollow-up-generator\u002Ftemplates\u002Ffollow-up-messages.md",[67,89,108,124,147,173],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":33},"01M6FMNSTJRX8HT4590YWT6MVK","validation-planner","Create the plan that closes the day: 2-day, 2-week, and 2-month commitments with numbers and owners, funnel math, a 30-day Green\u002FYellow\u002FRed framework, and an accountability partner. Validate stage.","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002Fvalidation-planner\u002FSKILL.md",[],[74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"validation","validation planner","planner","create","partner","with","red","stage","green","funnel","math","plan","owners","framework","validate",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":33},"01M6FMNN8373B8CVCYSAHV4G4R","testimonial-collector","Write personalized testimonial request emails, keep a collection tracker, format testimonials for the website, and run champion activation plans. Validate stage, once early customers or pilots exist.","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002Ftestimonial-collector\u002FSKILL.md",[],[96,97,98,99,88,100,101,102,103,104,105,81,106,107],"testimonial collector","collection","website","run","activation","format","testimonial request","keep","plans","emails","tracker","write",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":33},"01M6FMNHXGPNPPSG9YXWWBF8XQ","pitch-builder","Structure the end-of-day share-out. Picks a prototype or customer-and-offer format by path and slot length, then builds talking points, timing, and a one-sentence pitch. Validate stage.","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002Fpitch-builder\u002FSKILL.md",[],[115,116,117,118,88,119,101,120,81,121,122,123],"pitch","pitch builder","builder","timing","share","end","structure","prototype","customer",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":135,"publishedAt":33},"01M6FMNDY6FEDGPA02D19YGX71","landing-page-auditor","Audit a landing page across 8 dimensions using Hormozi's Value Equation and Dickerson's positioning angles, and produce prioritized fixes and A\u002FB test variants. Validate stage, once a page exists.","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002Flanding-page-auditor\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[136,137,138,139,140,141,142,81,143,144,145,146,88],"page","landing","landing page auditor","landing page","across","test","positioning angles","positioning","dimensions","audit","produce",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":161,"publishedAt":33},"01M6FMN9E6GPJNGGZKZFAMNMWZ","case-study-generator","Turn results into a case study package: website case study, companion blog post, LinkedIn posts, and newsletter section, using Dickerson's referral flywheel. Validate stage, once real results exist.","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002Fcase-study-generator\u002FSKILL.md",[153,156],{"categoryNo":154,"categoryName":155,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[162,163,164,21,98,165,88,166,167,168,29,81,169,170,171,172],"case study generator","study","case","package","blog","posts","companion","newsletter","results","linkedin","blog post",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":33},"01M6FMN5NN14Z8TTZJDWR0X9FZ","market-analyzer","Rapid market intelligence: TAM, SAM, and SOM sizing, competitive landscape map, and channel opportunity sizing. Works with web search or pasted research. Understand stage.","https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Funderstand\u002Fmarket-analyzer\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000021","资料检索与研究",[183,184,185,186,79,187,188,189,81,190,191,192,193,194,195,196,197,198,199,200],"analyzer","market analyzer","Market","map","understand","competitive","sam","market intelligence","landscape","opportunity","intelligence","competitive landscape map","channel","web search","search","competitive landscape","web","research"]