[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT97Y3KKZ4FS3E8J4TAM2Q":3,"skill-same:01M6CT97Y3KKZ4FS3E8J4TAM2Q":103},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":38,"updatedAt":39,"install":40,"resources":52},"01M6CT97Y3KKZ4FS3E8J4TAM2Q","market-intelligence",null,"Scans competitors, emerging technologies and market timing. Use when tracking competitors, evaluating a new technology or looking for opportunities.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarket-intelligence\u002FSKILL.md",[],[19,20,21,22,23,24,25],"Market","intelligence","market intelligence","competitors","tracking","use","technology","2026-11-10 10:12:30",false,"---\nname: market-intelligence\ndescription: Scans competitors, emerging technologies and market timing. Use when tracking competitors, evaluating a new technology or looking for opportunities.\nuser-invocable: true\n---\n\n# Market Intelligence\n\n## Reference\n- **ID**: S-PROD-07\n- **Category**: Product \u002F Strategy\n- **Inputs**: company.config.yaml, existing PRDs, competitor list, industry context\n- **Outputs**: market intelligence brief → artifacts\u002Fproduct\u002F, technology radar → artifacts\u002Fproduct\u002F\n- **Used by**: Product Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nProvide structured, ongoing market intelligence that moves beyond reactive discovery (validating a single idea) to proactive opportunity detection. Produces competitive landscape scans, technology radar assessments (ADOPT\u002FTRIAL\u002FASSESS\u002FHOLD), and trend timing analysis.\n\nThis skill turns \"I think our competitors are doing X\" into structured, evidence-based market awareness that feeds into PRD priorities and architecture decisions.\n\n## When to Use\n\n- Quarterly competitive landscape refresh\n- Before major product pivots or new market entry\n- When evaluating whether to adopt a new technology, library, or framework\n- When competitors launch notable features\n- When the Product Agent needs market context for prioritization\n- When the Engineering Agent needs technology evaluation for architecture decisions\n\n## Market Intelligence Procedure\n\n### Step 1: Load Context\n\n1. Read `company.config.yaml` -- understand product, domain, stage, tech stack\n2. Read existing market intelligence in `artifacts\u002Fproduct\u002F` -- avoid duplicate analysis\n3. Read existing PRDs -- what competitive pressure do they reference?\n4. Identify the monitoring scope:\n   - Direct competitors (same problem, same audience)\n   - Adjacent competitors (different approach, overlapping audience)\n   - Emerging threats (new entrants, tangential products expanding)\n\n### Step 2: Competitive Landscape Scan\n\nProduce a structured competitive analysis:\n\n#### Competitor Profile Template\n\nFor each competitor (3-5 direct, 2-3 adjacent):\n\n| Dimension | Analysis |\n|-----------|----------|\n| **Product** | Core features, unique differentiators, pricing model |\n| **Positioning** | Target audience, messaging, value proposition |\n| **Strengths** | What they do better than us |\n| **Weaknesses** | Gaps, complaints (from reviews, social, forums) |\n| **Recent Moves** | Last 90 days: launches, pricing changes, funding, pivots |\n| **Threat Level** | Low \u002F Medium \u002F High -- with justification |\n\n#### Feature Parity Matrix\n\nMap key features across competitors:\n\n```\n| Feature | Us | Competitor A | Competitor B | Competitor C |\n|---------|-----|-------------|-------------|-------------|\n| Feature 1 | Yes | Yes | No | Yes |\n| Feature 2 | No | Yes | Yes | No |\n| Feature 3 | In Progress | Yes | Yes | Yes |\n```\nLegend: Yes = has it, No = doesn't have it, In Progress = building, Partial = incomplete\n\nIdentify: parity gaps (they all have it, we don't), differentiation opportunities (we have it, they don't), table stakes (everyone needs this).\n\n### Step 3: Technology Radar\n\nEvaluate technologies relevant to the product using the ThoughtWorks radar model:\n\n#### Classification\n\n| Ring | Definition | Action |\n|------|-----------|--------|\n| **ADOPT** | Proven, low risk, clear value -- use it now | Include in tech stack |\n| **TRIAL** | Worth trying on a non-critical project | Spike or proof-of-concept |\n| **ASSESS** | Interesting, worth understanding -- not ready to try | Monitor, read docs |\n| **HOLD** | Proceed with caution -- issues identified | Avoid new adoption |\n\n#### Evaluation Criteria\n\nFor each technology being assessed:\n1. **Fitness**: Does it solve a real problem we have?\n2. **Maturity**: Production-ready? Community size? Documentation quality?\n3. **Ecosystem**: Integrates with our stack? Active maintenance? Breaking changes frequency?\n4. **Cost**: Licensing, infrastructure, team ramp-up time\n5. **Risk**: Vendor lock-in? Single maintainer? Regulatory concerns?\n\n#### Technology Radar Template\n\n```\n## Technology Radar -- [Quarter Year]\n\n### ADOPT\n- **[Tech]**: [Why -- 1 sentence] (evaluated: [date])\n\n### TRIAL\n- **[Tech]**: [Why -- 1 sentence, what to try it on] (evaluated: [date])\n\n### ASSESS\n- **[Tech]**: [Why watching -- 1 sentence] (evaluated: [date])\n\n### HOLD\n- **[Tech]**: [Why cautious -- 1 sentence] (evaluated: [date])\n```\n\nNote: This subsumes the \"Tool\u002FTechnology Evaluation\" concept -- technology evaluation happens within the market intelligence context, not in isolation.\n\n### Step 4: Trend Timing Analysis\n\nFor identified trends and opportunities, assess timing:\n\n#### Timing Framework\n\n| Window | Signal | Action |\n|--------|--------|--------|\n| **Too Early** (\u003C5% market adoption) | Only innovators talking about it, no proven business model | ASSESS on radar, monitor monthly |\n| **Sweet Spot** (5-25% adoption) | Early majority adopting, clear use cases, competitors starting | TRIAL or BUILD -- this is the window |\n| **Mainstream** (25-50% adoption) | Table stakes, user expectations set | ADOPT as parity -- differentiate on execution |\n| **Too Late** (>50% adoption) | Saturated, commoditized | Skip unless catching up on parity |\n\nFor each trend:\n1. Estimate current adoption stage\n2. Identify signals that indicate the next transition\n3. Recommend action: monitor, prototype, build, or skip\n4. If \"build\": estimate development effort and link to PRD pipeline\n\n### Step 5: App Store Intelligence (Conditional)\n\nOnly when `platforms.targets` includes `ios` or `android`:\n1. Review competitor app store listings (ratings, review themes, recent updates)\n2. Identify keyword trends and category shifts\n3. Note: feature requests appearing in competitor reviews but not addressed\n4. Track rating trajectories (improving or declining competitors)\n\n### Step 6: Produce Market Intelligence Brief\n\nCreate the brief artifact:\n\n```yaml\n---\nid: MI-XXX\ntype: market-intelligence\nstatus: draft\n---\n```\n\nStructure:\n1. **Executive Summary** (3-5 bullet points: what matters most right now)\n2. **Competitive Landscape** (profiles + feature parity matrix)\n3. **Technology Radar** (ADOPT\u002FTRIAL\u002FASSESS\u002FHOLD)\n4. **Trend Analysis** (timing assessments with recommended actions)\n5. **Opportunities** (gaps we can exploit, ranked by impact)\n6. **Threats** (risks to monitor, ranked by likelihood x impact)\n7. **Recommendations** (specific actions for Product, Engineering, Growth)\n\n### Step 7: Validate and Handoff\n\n1. Save to `artifacts\u002Fproduct\u002F`\n2. Run `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`\n3. Competitive landscape feeds into: `prd-writer` (competitive requirements), `positioning-messaging` (differentiation), `sprint-prioritizer` (priority context)\n4. Technology radar feeds into: `architecture-draft` (tech stack decisions), Engineering Agent (library choices)\n5. Schedule next refresh: quarterly for full scan, monthly for trend monitoring\n\n## Quality Checklist\n\n- [ ] At least 3 direct competitors profiled\n- [ ] Feature parity matrix covers key differentiating features\n- [ ] Technology radar uses ADOPT\u002FTRIAL\u002FASSESS\u002FHOLD classification\n- [ ] Each technology assessment has clear evaluation criteria\n- [ ] Trend timing uses the timing framework (too early \u002F sweet spot \u002F mainstream \u002F too late)\n- [ ] Recommendations are specific and actionable\n- [ ] Brief distinguishes facts (observed) from analysis (interpreted)\n- [ ] Sources are cited (URLs, dates) for key claims\n- [ ] Artifact has valid frontmatter\n\n## Cross-References\n\n- **discovery-validation**: Market intelligence provides context for discovery validation (is this idea already being done? by whom? how?)\n- **positioning-messaging**: Competitive landscape directly informs positioning and differentiation strategy\n- **architecture-draft**: Technology radar feeds into tech stack fitness evaluation in RFCs\n- **sprint-prioritizer**: Competitive pressure and market opportunities feed into priority scoring\n","# Market Intelligence\n\n## Reference\n- **ID**: S-PROD-07\n- **Category**: Product \u002F Strategy\n- **Inputs**: company.config.yaml, existing PRDs, competitor list, industry context\n- **Outputs**: market intelligence brief → artifacts\u002Fproduct\u002F, technology radar → artifacts\u002Fproduct\u002F\n- **Used by**: Product Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nProvide structured, ongoing market intelligence that moves beyond reactive discovery (validating a single idea) to proactive opportunity detection. Produces competitive landscape scans, technology radar assessments (ADOPT\u002FTRIAL\u002FASSESS\u002FHOLD), and trend timing analysis.\n\nThis skill turns \"I think our competitors are doing X\" into structured, evidence-based market awareness that feeds into PRD priorities and architecture decisions.\n\n## When to Use\n\n- Quarterly competitive landscape refresh\n- Before major product pivots or new market entry\n- When evaluating whether to adopt a new technology, library, or framework\n- When competitors launch notable features\n- When the Product Agent needs market context for prioritization\n- When the Engineering Agent needs technology evaluation for architecture decisions\n\n## Market Intelligence Procedure\n\n### Step 1: Load Context\n\n1. Read `company.config.yaml` -- understand product, domain, stage, tech stack\n2. Read existing market intelligence in `artifacts\u002Fproduct\u002F` -- avoid duplicate analysis\n3. Read existing PRDs -- what competitive pressure do they reference?\n4. Identify the monitoring scope:\n   - Direct competitors (same problem, same audience)\n   - Adjacent competitors (different approach, overlapping audience)\n   - Emerging threats (new entrants, tangential products expanding)\n\n### Step 2: Competitive Landscape Scan\n\nProduce a structured competitive analysis:\n\n#### Competitor Profile Template\n\nFor each competitor (3-5 direct, 2-3 adjacent):\n\n| Dimension | Analysis |\n|-----------|----------|\n| **Product** | Core features, unique differentiators, pricing model |\n| **Positioning** | Target audience, messaging, value proposition |\n| **Strengths** | What they do better than us |\n| **Weaknesses** | Gaps, complaints (from reviews, social, forums) |\n| **Recent Moves** | Last 90 days: launches, pricing changes, funding, pivots |\n| **Threat Level** | Low \u002F Medium \u002F High -- with justification |\n\n#### Feature Parity Matrix\n\nMap key features across competitors:\n\n```\n| Feature | Us | Competitor A | Competitor B | Competitor C |\n|---------|-----|-------------|-------------|-------------|\n| Feature 1 | Yes | Yes | No | Yes |\n| Feature 2 | No | Yes | Yes | No |\n| Feature 3 | In Progress | Yes | Yes | Yes |\n```\nLegend: Yes = has it, No = doesn't have it, In Progress = building, Partial = incomplete\n\nIdentify: parity gaps (they all have it, we don't), differentiation opportunities (we have it, they don't), table stakes (everyone needs this).\n\n### Step 3: Technology Radar\n\nEvaluate technologies relevant to the product using the ThoughtWorks radar model:\n\n#### Classification\n\n| Ring | Definition | Action |\n|------|-----------|--------|\n| **ADOPT** | Proven, low risk, clear value -- use it now | Include in tech stack |\n| **TRIAL** | Worth trying on a non-critical project | Spike or proof-of-concept |\n| **ASSESS** | Interesting, worth understanding -- not ready to try | Monitor, read docs |\n| **HOLD** | Proceed with caution -- issues identified | Avoid new adoption |\n\n#### Evaluation Criteria\n\nFor each technology being assessed:\n1. **Fitness**: Does it solve a real problem we have?\n2. **Maturity**: Production-ready? Community size? Documentation quality?\n3. **Ecosystem**: Integrates with our stack? Active maintenance? Breaking changes frequency?\n4. **Cost**: Licensing, infrastructure, team ramp-up time\n5. **Risk**: Vendor lock-in? Single maintainer? Regulatory concerns?\n\n#### Technology Radar Template\n\n```\n## Technology Radar -- [Quarter Year]\n\n### ADOPT\n- **[Tech]**: [Why -- 1 sentence] (evaluated: [date])\n\n### TRIAL\n- **[Tech]**: [Why -- 1 sentence, what to try it on] (evaluated: [date])\n\n### ASSESS\n- **[Tech]**: [Why watching -- 1 sentence] (evaluated: [date])\n\n### HOLD\n- **[Tech]**: [Why cautious -- 1 sentence] (evaluated: [date])\n```\n\nNote: This subsumes the \"Tool\u002FTechnology Evaluation\" concept -- technology evaluation happens within the market intelligence context, not in isolation.\n\n### Step 4: Trend Timing Analysis\n\nFor identified trends and opportunities, assess timing:\n\n#### Timing Framework\n\n| Window | Signal | Action |\n|--------|--------|--------|\n| **Too Early** (\u003C5% market adoption) | Only innovators talking about it, no proven business model | ASSESS on radar, monitor monthly |\n| **Sweet Spot** (5-25% adoption) | Early majority adopting, clear use cases, competitors starting | TRIAL or BUILD -- this is the window |\n| **Mainstream** (25-50% adoption) | Table stakes, user expectations set | ADOPT as parity -- differentiate on execution |\n| **Too Late** (>50% adoption) | Saturated, commoditized | Skip unless catching up on parity |\n\nFor each trend:\n1. Estimate current adoption stage\n2. Identify signals that indicate the next transition\n3. Recommend action: monitor, prototype, build, or skip\n4. If \"build\": estimate development effort and link to PRD pipeline\n\n### Step 5: App Store Intelligence (Conditional)\n\nOnly when `platforms.targets` includes `ios` or `android`:\n1. Review competitor app store listings (ratings, review themes, recent updates)\n2. Identify keyword trends and category shifts\n3. Note: feature requests appearing in competitor reviews but not addressed\n4. Track rating trajectories (improving or declining competitors)\n\n### Step 6: Produce Market Intelligence Brief\n\nCreate the brief artifact:\n\n```yaml\n---\nid: MI-XXX\ntype: market-intelligence\nstatus: draft\n---\n```\n\nStructure:\n1. **Executive Summary** (3-5 bullet points: what matters most right now)\n2. **Competitive Landscape** (profiles + feature parity matrix)\n3. **Technology Radar** (ADOPT\u002FTRIAL\u002FASSESS\u002FHOLD)\n4. **Trend Analysis** (timing assessments with recommended actions)\n5. **Opportunities** (gaps we can exploit, ranked by impact)\n6. **Threats** (risks to monitor, ranked by likelihood x impact)\n7. **Recommendations** (specific actions for Product, Engineering, Growth)\n\n### Step 7: Validate and Handoff\n\n1. Save to `artifacts\u002Fproduct\u002F`\n2. Run `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`\n3. Competitive landscape feeds into: `prd-writer` (competitive requirements), `positioning-messaging` (differentiation), `sprint-prioritizer` (priority context)\n4. Technology radar feeds into: `architecture-draft` (tech stack decisions), Engineering Agent (library choices)\n5. Schedule next refresh: quarterly for full scan, monthly for trend monitoring\n\n## Quality Checklist\n\n- [ ] At least 3 direct competitors profiled\n- [ ] Feature parity matrix covers key differentiating features\n- [ ] Technology radar uses ADOPT\u002FTRIAL\u002FASSESS\u002FHOLD classification\n- [ ] Each technology assessment has clear evaluation criteria\n- [ ] Trend timing uses the timing framework (too early \u002F sweet spot \u002F mainstream \u002F too late)\n- [ ] Recommendations are specific and actionable\n- [ ] Brief distinguishes facts (observed) from analysis (interpreted)\n- [ ] Sources are cited (URLs, dates) for key claims\n- [ ] Artifact has valid frontmatter\n\n## Cross-References\n\n- **discovery-validation**: Market intelligence provides context for discovery validation (is this idea already being done? by whom? how?)\n- **positioning-messaging**: Competitive landscape directly informs positioning and differentiation strategy\n- **architecture-draft**: Technology radar feeds into tech stack fitness evaluation in RFCs\n- **sprint-prioritizer**: Competitive pressure and market opportunities feed into priority scoring\n",{"name":5,"description":7,"user-invocable":31},true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4",".claude\u002Fskills\u002Fmarket-intelligence",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":31},[42,45,48],{"tool":43,"command":44},"npx","npx skills add vibbs\u002Fcompany-os --skill market-intelligence",{"tool":46,"command":47},"bunx","bunx skills add vibbs\u002Fcompany-os --skill market-intelligence",{"tool":49,"command":50},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill market-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarket-intelligence\u002FSKILL.md",[53,59,65,69,75,79,83,87,91,95,99],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"html2pptx.md","REFERENCE","参考文档",19859,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002Fhtml2pptx.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"LICENSE.txt","LICENSE","许可证",1467,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FLICENSE.txt",{"path":66,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":67,"sourceHtmlUrl":68},"ooxml.md",10388,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002Fooxml.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"Ooxml\u002FScripts\u002Fpack.py","SCRIPT","脚本",5596,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FOoxml\u002FScripts\u002Fpack.py",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"Ooxml\u002FScripts\u002Funpack.py",1037,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FOoxml\u002FScripts\u002Funpack.py",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"Ooxml\u002FScripts\u002Fvalidate.py",1959,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FOoxml\u002FScripts\u002Fvalidate.py",{"path":84,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":85,"sourceHtmlUrl":86},"Scripts\u002Fhtml2pptx.js",37795,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FScripts\u002Fhtml2pptx.js",{"path":88,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":89,"sourceHtmlUrl":90},"Scripts\u002Finventory.py",38126,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FScripts\u002Finventory.py",{"path":92,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":93,"sourceHtmlUrl":94},"Scripts\u002Frearrange.py",8514,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FScripts\u002Frearrange.py",{"path":96,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":97,"sourceHtmlUrl":98},"Scripts\u002Freplace.py",13594,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FScripts\u002Freplace.py",{"path":100,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":101,"sourceHtmlUrl":102},"Scripts\u002Fthumbnail.py",15484,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002FPersonal_AI_Infrastructure\u002FPacks\u002FUtilities\u002Fsrc\u002FDocuments\u002FPptx\u002FScripts\u002Fthumbnail.py",[104,113,121,131,147,165],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":26},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[111,112],"typo field","fixture skill",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":26},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[120,112],"spaced comments",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":26},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[128,129,130,112],"crlf comments","CRLF","windows",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":26},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[138,139,140,141,142,143,112,144,145,146],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"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":158,"publishedAt":26},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[159,160,161,162,163,24,164],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":26},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[172,173,174,162,24,175,176,177,178],"weekly review","review","priorities","health","save","support","security"]