[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FMMJC0T8FSD6C8CZ0N37PW":3,"skill-same:01M6FMMJC0T8FSD6C8CZ0N37PW":68},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6FMMJC0T8FSD6C8CZ0N37PW","cohort-prep",null,"Pre-event prep for sherpas. Ingest a cohort roster, build a briefing card per startup with predicted sticking points by path, suggest sherpa assignments, and make a Miro checklist.","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\u002Fcohort-prep\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"cohort","cohort prep","startup","ingest","checklist","build","card","roster","make","event","with","briefing","2026-11-10 10:12:30",false,"---\nname: cohort-prep\ndescription: Pre-event prep for sherpas. Ingest a cohort roster, build a briefing card per startup with predicted sticking points by path, suggest sherpa assignments, and make a Miro checklist.\nlicense: CC-BY-4.0\n---\n\n# Cohort Prep\n\nPre-event skill for sherpas. Run this before each Founder Jam to review the cohort, surface predicted sticking points, and prepare your table setup. The day follows four stages (Understand, Focus, Build, Validate) and each founder picks one of four paths with their sherpa during Focus.\n\n## Overview\n\nThis skill walks through:\n1. Roster ingestion (text, CSV, or JSON)\n2. Per-startup briefing card generation\n3. Sherpa assignment suggestions\n4. Miro board setup checklist\n\n**When to run:** 24-48 hours before the event.\n\n## Process\n\n### Step 1: Ingest roster\n\nAccept cohort data in any of these formats:\n\n**Pasted text:** Ask the sherpa to paste startup details. Parse freeform. Extract: startup name, founder names, problem statement, stage, business type, and the focus area they chose on the application (their likely path).\n\n**CSV or JSON:** Accept structured input directly.\n\n**Founder handoff blocks:** If a founder shares 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`, `stage`, `business_type`, `problem_statement`, `icp_segment`, `hypothesis_selected`, `lead_magnet`, `outbound_system`, `channels_selected`, and `published_pages` from it instead of asking.\n\n**Required fields per startup:**\n- `startup_name`\n- `founder_names` (one or more)\n- `problem_statement` (1-2 sentences)\n- `stage` (Idea \u002F Pre-Revenue \u002F Early-Revenue)\n- `business_type` (B2B SaaS \u002F Services \u002F Marketplace \u002F Consumer)\n- `path` (product and positioning \u002F GTM and growth \u002F sales \u002F ops and automation \u002F undecided)\n\n**Optional fields:**\n- `traction` (users, revenue, waitlist, LOIs)\n- `team_size`\n- `notes` (anything unusual or flagged by organizers)\n\nIf any required field is missing, ask for it before proceeding.\n\n### Step 2: Generate briefing cards\n\nFor each startup, produce a briefing card using the `templates\u002Fcohort-briefing-card.md` format.\n\n**Auto-predict sticking points based on stage + business type + path:**\n\n| Condition | Predicted Sticking Points |\n|-----------|--------------------------|\n| Idea stage | Will struggle with specificity in hypothesis; may not have real competitor data; may over-index on solution instead of problem |\n| Pre-revenue, product and positioning | Will resist narrowing ICP to one segment; may want to over-engineer prototype instead of building minimum artifact |\n| Pre-revenue, GTM and growth or sales | Will have no baseline data for metrics; may struggle with lead magnet format selection |\n| Early-revenue, product and positioning | Will resist pivoting what's \"working\"; hypothesis may be too incremental |\n| Early-revenue, GTM and growth or sales | May under-invest in automation (\"I'll just do it manually\"); will struggle defining North Star vs. vanity metrics |\n| Ops and automation | May want custom code when a simple workflow would test the idea; may automate a process they haven't mapped yet |\n| B2B SaaS | Competitive data is available but dense; may spend too long on battle cards |\n| Services | ICP is often vague (\"any business\"); push for job title and company size specificity |\n| Marketplace | Two-sided ICP problem, push them to choose one side for the day |\n| Consumer | Distribution channel selection is hardest; may lack budget for paid; needs organic channel plan |\n\n**Recommended emphasis areas:** Flag which stage of the day (Understand, Focus, Build, or Validate) will likely need extra time for this startup. Reference `templates\u002Fsession-pacing-guide.md`.\n\n### Step 3: Suggest sherpa assignments\n\nIf sherpa names and domains are provided, suggest assignments based on:\n\n1. **Domain expertise match**: Pair sherpas with startups in adjacent industries or similar business models.\n2. **Business type match**: B2B SaaS startups benefit from sherpas with software or sales backgrounds; Services from operational experience.\n3. **Table size balance**: Distribute startups evenly. No sherpa should have more than 2 startups unless the cohort is small.\n\nOutput suggested assignments as a table:\n\n```\n| Startup | Path | Stage | Suggested Sherpa | Rationale |\n|---------|-------|-------|----------------------|-----------|\n```\n\nIf sherpa roster is not provided, skip this step and note it as a manual action item.\n\n### Step 4: Miro board setup checklist\n\nBuild one board layout for the whole cohort with four stage columns: Understand, Focus, Build, Validate. Founders pick their path in Focus, so pre-load the shared frames for every table and keep the path frames ready to drop in.\n\n**All tables (shared frames):**\n- [ ] Startup name on each frame header\n- [ ] Sherpa name in corner\n- [ ] Timer sticky note (15\u002F30-minute blocks)\n- [ ] Understand: SWOT template (2x2 grid, labeled) and battle card frames (one per competitor, 4-5 frames)\n- [ ] Focus: path picker frame listing the four paths with one line on each\n- [ ] Validate: validation planner template (2 days \u002F 2 weeks \u002F 2 months) and share-out notes frame\n- [ ] Color coding applied: blue = competitive and customer data, yellow = hypotheses and decisions, orange = offer and content, green = prototype and build artifacts\n\n**Path frames (ready to drop in once the founder chooses):**\n- [ ] Product and positioning: hypothesis workspace (diverge zone + converge zone with effort\u002Fimpact matrix) and prototype build space (open canvas with sticky note palette)\n- [ ] GTM and growth: ICP canvas (Jobs-to-be-Done template), competitive growth matrix (channel analysis grid), lead magnet brainstorm frame (format options pre-listed), 30-day plan grid (4 weeks x 5 rows), North Star metric tracker\n- [ ] Sales: ICP canvas, first-100-prospects list frame, sequence drafts frame, call tracker\n- [ ] Ops and automation: manual-time audit table, workflow diagram space (node mapping area), North Star metric tracker\n\n### Step 5: Output summary\n\nAfter processing all startups, present a cohort overview:\n\n```\n## Cohort overview: [Event date]\n\n**Total Startups:** N\n**Path Distribution:** N product and positioning \u002F N GTM and growth \u002F N sales \u002F N ops and automation \u002F N undecided\n**Stage Distribution:** N Idea \u002F N Pre-Revenue \u002F N Early-Revenue\n\n### Common themes\n[2-3 patterns across the cohort, e.g., \"3 of 5 startups are services businesses with vague ICPs\"]\n\n### Predicted high-attention startups\n[List startups that will likely need the most sherpa intervention, with reason]\n\n### Top risks for the day\n[2-3 cohort-level risks, e.g., \"Most startups are idea-stage, expect slow battle card research phase\"]\n\n### Sherpa assignments\n[Table from Step 3, or \"Manual assignment needed\"]\n```\n\n## Context\n\n**Reads:** Nothing (pre-event). Roster details come from the sherpa, the application form, or founders' handoff blocks.\n**Writes:** Nothing (informational only). Sherpas may save output manually.\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---\n\nFounder Jam curriculum and skills by Drew Burdick · program co-created with Innovate Charlotte · CC BY 4.0 · drewburdick.com\u002Ffounderjam\n","# Cohort Prep\n\nPre-event skill for sherpas. Run this before each Founder Jam to review the cohort, surface predicted sticking points, and prepare your table setup. The day follows four stages (Understand, Focus, Build, Validate) and each founder picks one of four paths with their sherpa during Focus.\n\n## Overview\n\nThis skill walks through:\n1. Roster ingestion (text, CSV, or JSON)\n2. Per-startup briefing card generation\n3. Sherpa assignment suggestions\n4. Miro board setup checklist\n\n**When to run:** 24-48 hours before the event.\n\n## Process\n\n### Step 1: Ingest roster\n\nAccept cohort data in any of these formats:\n\n**Pasted text:** Ask the sherpa to paste startup details. Parse freeform. Extract: startup name, founder names, problem statement, stage, business type, and the focus area they chose on the application (their likely path).\n\n**CSV or JSON:** Accept structured input directly.\n\n**Founder handoff blocks:** If a founder shares 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`, `stage`, `business_type`, `problem_statement`, `icp_segment`, `hypothesis_selected`, `lead_magnet`, `outbound_system`, `channels_selected`, and `published_pages` from it instead of asking.\n\n**Required fields per startup:**\n- `startup_name`\n- `founder_names` (one or more)\n- `problem_statement` (1-2 sentences)\n- `stage` (Idea \u002F Pre-Revenue \u002F Early-Revenue)\n- `business_type` (B2B SaaS \u002F Services \u002F Marketplace \u002F Consumer)\n- `path` (product and positioning \u002F GTM and growth \u002F sales \u002F ops and automation \u002F undecided)\n\n**Optional fields:**\n- `traction` (users, revenue, waitlist, LOIs)\n- `team_size`\n- `notes` (anything unusual or flagged by organizers)\n\nIf any required field is missing, ask for it before proceeding.\n\n### Step 2: Generate briefing cards\n\nFor each startup, produce a briefing card using the `templates\u002Fcohort-briefing-card.md` format.\n\n**Auto-predict sticking points based on stage + business type + path:**\n\n| Condition | Predicted Sticking Points |\n|-----------|--------------------------|\n| Idea stage | Will struggle with specificity in hypothesis; may not have real competitor data; may over-index on solution instead of problem |\n| Pre-revenue, product and positioning | Will resist narrowing ICP to one segment; may want to over-engineer prototype instead of building minimum artifact |\n| Pre-revenue, GTM and growth or sales | Will have no baseline data for metrics; may struggle with lead magnet format selection |\n| Early-revenue, product and positioning | Will resist pivoting what's \"working\"; hypothesis may be too incremental |\n| Early-revenue, GTM and growth or sales | May under-invest in automation (\"I'll just do it manually\"); will struggle defining North Star vs. vanity metrics |\n| Ops and automation | May want custom code when a simple workflow would test the idea; may automate a process they haven't mapped yet |\n| B2B SaaS | Competitive data is available but dense; may spend too long on battle cards |\n| Services | ICP is often vague (\"any business\"); push for job title and company size specificity |\n| Marketplace | Two-sided ICP problem, push them to choose one side for the day |\n| Consumer | Distribution channel selection is hardest; may lack budget for paid; needs organic channel plan |\n\n**Recommended emphasis areas:** Flag which stage of the day (Understand, Focus, Build, or Validate) will likely need extra time for this startup. Reference `templates\u002Fsession-pacing-guide.md`.\n\n### Step 3: Suggest sherpa assignments\n\nIf sherpa names and domains are provided, suggest assignments based on:\n\n1. **Domain expertise match**: Pair sherpas with startups in adjacent industries or similar business models.\n2. **Business type match**: B2B SaaS startups benefit from sherpas with software or sales backgrounds; Services from operational experience.\n3. **Table size balance**: Distribute startups evenly. No sherpa should have more than 2 startups unless the cohort is small.\n\nOutput suggested assignments as a table:\n\n```\n| Startup | Path | Stage | Suggested Sherpa | Rationale |\n|---------|-------|-------|----------------------|-----------|\n```\n\nIf sherpa roster is not provided, skip this step and note it as a manual action item.\n\n### Step 4: Miro board setup checklist\n\nBuild one board layout for the whole cohort with four stage columns: Understand, Focus, Build, Validate. Founders pick their path in Focus, so pre-load the shared frames for every table and keep the path frames ready to drop in.\n\n**All tables (shared frames):**\n- [ ] Startup name on each frame header\n- [ ] Sherpa name in corner\n- [ ] Timer sticky note (15\u002F30-minute blocks)\n- [ ] Understand: SWOT template (2x2 grid, labeled) and battle card frames (one per competitor, 4-5 frames)\n- [ ] Focus: path picker frame listing the four paths with one line on each\n- [ ] Validate: validation planner template (2 days \u002F 2 weeks \u002F 2 months) and share-out notes frame\n- [ ] Color coding applied: blue = competitive and customer data, yellow = hypotheses and decisions, orange = offer and content, green = prototype and build artifacts\n\n**Path frames (ready to drop in once the founder chooses):**\n- [ ] Product and positioning: hypothesis workspace (diverge zone + converge zone with effort\u002Fimpact matrix) and prototype build space (open canvas with sticky note palette)\n- [ ] GTM and growth: ICP canvas (Jobs-to-be-Done template), competitive growth matrix (channel analysis grid), lead magnet brainstorm frame (format options pre-listed), 30-day plan grid (4 weeks x 5 rows), North Star metric tracker\n- [ ] Sales: ICP canvas, first-100-prospects list frame, sequence drafts frame, call tracker\n- [ ] Ops and automation: manual-time audit table, workflow diagram space (node mapping area), North Star metric tracker\n\n### Step 5: Output summary\n\nAfter processing all startups, present a cohort overview:\n\n```\n## Cohort overview: [Event date]\n\n**Total Startups:** N\n**Path Distribution:** N product and positioning \u002F N GTM and growth \u002F N sales \u002F N ops and automation \u002F N undecided\n**Stage Distribution:** N Idea \u002F N Pre-Revenue \u002F N Early-Revenue\n\n### Common themes\n[2-3 patterns across the cohort, e.g., \"3 of 5 startups are services businesses with vague ICPs\"]\n\n### Predicted high-attention startups\n[List startups that will likely need the most sherpa intervention, with reason]\n\n### Top risks for the day\n[2-3 cohort-level risks, e.g., \"Most startups are idea-stage, expect slow battle card research phase\"]\n\n### Sherpa assignments\n[Table from Step 3, or \"Manual assignment needed\"]\n```\n\n## Context\n\n**Reads:** Nothing (pre-event). Roster details come from the sherpa, the application form, or founders' handoff blocks.\n**Writes:** Nothing (informational only). Sherpas may save output manually.\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---\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\u002Fcohort-prep",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add stealthxco\u002Ffounderjamskills --skill cohort-prep",{"tool":50,"command":51},"bunx","bunx skills add stealthxco\u002Ffounderjamskills --skill cohort-prep",{"tool":53,"command":54},"pnpm","pnpm dlx skills add stealthxco\u002Ffounderjamskills --skill cohort-prep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fsherpa\u002Fcohort-prep\u002FSKILL.md",true,[58,64],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"templates\u002Fcohort-briefing-card.md","REFERENCE","参考文档",764,"https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fsherpa\u002Fcohort-prep\u002Ftemplates\u002Fcohort-briefing-card.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"templates\u002Fsession-pacing-guide.md",11409,"https:\u002F\u002Fgithub.com\u002Fstealthxco\u002Ffounderjamskills\u002Fblob\u002Fmain\u002Fskills\u002Fsherpa\u002Fcohort-prep\u002Ftemplates\u002Fsession-pacing-guide.md",[69,90,109,125,148,176],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":31},"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",[],[76,77,78,79,80,29,81,82,83,84,85,86,87,88,89],"validation","validation planner","planner","create","partner","red","stage","green","funnel","math","plan","owners","framework","validate",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":31},"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",[],[97,98,99,100,89,101,102,103,104,105,106,82,107,108],"testimonial collector","collection","website","run","activation","format","testimonial request","keep","plans","emails","tracker","write",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":31},"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",[],[116,117,118,119,89,120,102,121,82,122,123,124],"pitch","pitch builder","builder","timing","share","end","structure","prototype","customer",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":31},"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",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[137,138,139,140,141,142,143,82,144,145,146,147,89],"page","landing","landing page auditor","landing page","across","test","positioning angles","positioning","dimensions","audit","produce",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":162,"publishedAt":31},"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",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[163,164,165,166,99,167,89,168,169,170,171,82,172,173,174,175],"case study generator","study","case","generator","package","blog","posts","companion","post","newsletter","results","linkedin","blog post",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":31},"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",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000021","资料检索与研究",[186,187,188,189,29,190,191,192,82,193,194,195,196,197,198,199,200,201,202,203],"analyzer","market analyzer","Market","map","understand","competitive","sam","market intelligence","landscape","opportunity","intelligence","competitive landscape map","channel","web search","search","competitive landscape","web","research"]