[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTDBV70FRN57CWZDZP8BNG":3,"skill-same:01M6CTDBV70FRN57CWZDZP8BNG":64},{"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":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6CTDBV70FRN57CWZDZP8BNG","discovery-validation",null,"Checks whether a new feature idea is worth building before you write a PRD. Use for novel features; common patterns are skipped.","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\u002Fos\u002Fskills\u002Fdiscovery-validation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34],"validation","discovery","discovery validation","prd","write a prd","common","write","new feature","use","idea","patterns","2026-11-10 10:12:30",false,"---\nname: discovery-validation\ndescription: Checks whether a new feature idea is worth building before you write a PRD. Use for novel features; common patterns are skipped.\nruntimes:\n  claude:\n    user-invocable: false\n---\n\n# Discovery Validation\n\n## Reference\n- **ID**: S-PROD-05\n- **Category**: Product\n- **Inputs**: objective description, company.config.yaml, market context\n- **Outputs**: Discovery Validation section (appended to PRD), or \"skip\" verdict for common patterns\n- **Used by**: Product Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nNot every feature needs discovery. Authentication, CRUD, and notifications are well-understood patterns -- just build them. But novel concepts (new business models, AI-powered interfaces, marketplace dynamics) carry real uncertainty and deserve lightweight validation before committing engineering time. This skill acts as a smart filter: it classifies the objective, skips discovery for common patterns, and runs a focused validation for novel concepts.\n\n## When to Use\n\n- Before writing a PRD for any new feature or product\n- When the solopreneur\u002FPM is unsure if an idea has legs\n- When the feature involves unfamiliar territory (new market, new UX paradigm, new business model)\n- The Product Agent should invoke this skill as a first step before PRD generation\n\n## Discovery Validation Procedure\n\n### Step 1: Classify Objective (Smart Filter)\n\nDetermine whether this feature needs discovery by matching it against known patterns.\n\n#### COMMON PATTERNS (skip discovery -- proceed directly to PRD)\n\nThese are well-understood, solved problems with established implementation patterns:\n\n- Authentication \u002F login \u002F signup \u002F password reset\n- CRUD operations (create, read, update, delete for any entity)\n- Notifications (email, push, in-app)\n- File uploads \u002F media management\n- Search \u002F filtering \u002F sorting\n- Pagination\n- Settings \u002F preferences pages\n- Admin panels \u002F dashboards\n- Payment integration (Stripe, PayPal)\n- User profiles \u002F account management\n- Comments \u002F ratings \u002F reviews\n- Tags \u002F categories \u002F labels\n- Export \u002F import (CSV, PDF, etc.)\n- Webhooks \u002F integrations with known services\n- Role-based access control (RBAC)\n- Audit logging\n- Internationalization (i18n)\n\nIf the objective matches a common pattern:\n\n> **Output**: \"Discovery skipped -- [feature] matches common pattern: [category]. Proceeding to PRD.\"\n\nExit the skill. No further steps needed.\n\n#### NOVEL CONCEPTS (full discovery required)\n\nThese involve genuine uncertainty about problem-solution fit:\n\n- New business model or pricing paradigm\n- New market segment the product has not served before\n- New UX paradigm (AI-powered interface, voice UI, AR\u002FVR)\n- Marketplace or multi-sided platform dynamics\n- AI\u002FML-powered features without precedent in the product\n- Social\u002Fcommunity features with network effects\n- Features requiring new data sources or partnerships\n- Anything the solopreneur describes as \"I have never built something like this\"\n- Gamification or behavioral mechanics\n- Content creation or collaboration tools with novel workflows\n\nIf the objective matches a novel concept, proceed to Step 2.\n\n#### UNCERTAIN\n\nIf the objective does not clearly fit either category, ask the user:\n\n> \"This feature sits between common and novel. Should I run discovery validation or proceed directly to PRD?\"\n\nRespect the user's decision.\n\n### Step 2: Lean Canvas (for NOVEL Concepts)\n\nProduce a one-page lean canvas covering all nine boxes. Be specific -- generic answers defeat the purpose.\n\n| Box | Prompt | Output |\n|-----|--------|--------|\n| **Problem** | What are the top 3 problems this feature solves? | Specific, observable problems with evidence |\n| **Customer Segments** | Who specifically has these problems? | Named persona(s) with context (role, company size, behavior) |\n| **Unique Value Proposition** | Single clear compelling message | One sentence that would make the target persona stop scrolling |\n| **Solution** | Top 3 features that address the problems | Concrete capabilities, not abstract descriptions |\n| **Channels** | How will users discover this feature? | Specific channels (in-app prompt, email campaign, blog post, word-of-mouth) |\n| **Revenue Streams** | How does this feature contribute to revenue? | Direct (new pricing tier, add-on) or indirect (retention, upsell trigger) |\n| **Cost Structure** | What are the build + ongoing costs? | Engineering time estimate, infrastructure costs, third-party service costs |\n| **Key Metrics** | What numbers prove this works? | 2-4 specific metrics with target values |\n| **Unfair Advantage** | What makes this defensible? | Data, network effects, domain expertise, integrations, brand |\n\n### Step 3: Competitive Quick-Scan\n\nIdentify 3-5 closest alternatives and analyze them:\n\nFor each alternative:\n- **Name**: Product or feature name\n- **How they solve the same problem**: Specific approach, not vague description\n- **Pricing**: Free, freemium, paid (with price point if known)\n- **Key differentiator**: What they do better than others\n\n**Gap Analysis**: What is missing from existing solutions? What do users complain about? Where is there whitespace?\n\n**Positioning**: How will our approach be different or better? What trade-offs are we making? Why would someone switch from an existing solution?\n\nUse WebSearch to find current competitors, recent reviews, and user complaints if needed. Do not fabricate competitor information -- if data is unavailable, state that explicitly.\n\n### Step 4: Risk Assessment\n\n#### Riskiest Assumption\n\nIdentify the ONE thing that, if wrong, kills this idea. Be specific:\n- Bad: \"Users might not want this\"\n- Good: \"Freelance designers earning $50-100K\u002Fyear will pay $29\u002Fmonth for AI-generated client proposals because they currently spend 5+ hours per proposal\"\n\n#### Validation Approach\n\nHow to test the riskiest assumption cheaply, before building:\n- Landing page with email capture (test demand)\n- Concierge MVP (manual delivery of the value proposition)\n- Survey of target persona (test willingness to pay)\n- Wizard-of-Oz prototype (fake the backend, real the frontend)\n- Competitor review mining (do users complain about the gap we would fill?)\n\n#### Problem Validation Questions\n\n| Question | How to Answer |\n|----------|---------------|\n| Who has this problem? | Specific persona with demographics and behavior |\n| How painful is it? (1-10 scale) | Evidence-based: time wasted, money lost, frustration signals |\n| How are they solving it today? | Current workarounds, tools, manual processes |\n| Will they pay for a better solution? | Willingness-to-pay signals: existing spend, stated intent, market comps |\n\n#### Go\u002FNo-Go Recommendation\n\nBased on the lean canvas, competitive scan, and risk assessment, provide one of three recommendations:\n\n- **Proceed to PRD**: Evidence supports building this. Riskiest assumption is testable and the upside justifies the cost.\n- **Validate first**: The idea has potential but the riskiest assumption is untested. Run the validation approach before committing to a PRD.\n- **Reconsider**: Multiple red flags -- strong competition with no clear differentiator, unclear demand, or high cost with uncertain return.\n\nInclude a clear rationale for the recommendation (2-3 sentences).\n\n### Step 5: Output\n\nAppend a \"Discovery Validation\" section to the PRD (this is NOT a separate artifact -- it lives within the PRD):\n\n```markdown\n## Discovery Validation\n\n**Classification**: NOVEL -- [reason why this needed discovery]\n**Lean Canvas**: [summary of the 9 boxes, or \"See full canvas above\"]\n**Competitive Landscape**: [3-5 alternatives with gap analysis summary]\n**Riskiest Assumption**: [the one specific thing that could kill this]\n**Validation Status**: Validated \u002F Needs Testing \u002F Risky\n**Recommendation**: Proceed to PRD \u002F Validate first \u002F Reconsider\n**Rationale**: [2-3 sentences explaining the recommendation]\n```\n\nIf discovery was skipped (common pattern), the PRD should include a brief note:\n\n```markdown\n## Discovery Validation\n\n**Classification**: COMMON PATTERN -- [category name]\n**Discovery**: Skipped. This is a well-understood pattern with established implementation approaches.\n```\n\n## Quality Checklist\n\n- [ ] Smart filter correctly classified the objective (common vs. novel)\n- [ ] If NOVEL: lean canvas is complete (all 9 boxes filled with specifics)\n- [ ] Competitive scan has 3-5 real alternatives (not generic or fabricated)\n- [ ] Riskiest assumption is specific and testable (not vague)\n- [ ] Problem validation questions are answered with evidence (not assumptions)\n- [ ] Go\u002FNo-Go recommendation is clear with rationale\n- [ ] If COMMON: skip is justified with pattern category\n- [ ] Output format matches the template (appended to PRD, not separate artifact)\n","# Discovery Validation\n\n## Reference\n- **ID**: S-PROD-05\n- **Category**: Product\n- **Inputs**: objective description, company.config.yaml, market context\n- **Outputs**: Discovery Validation section (appended to PRD), or \"skip\" verdict for common patterns\n- **Used by**: Product Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nNot every feature needs discovery. Authentication, CRUD, and notifications are well-understood patterns -- just build them. But novel concepts (new business models, AI-powered interfaces, marketplace dynamics) carry real uncertainty and deserve lightweight validation before committing engineering time. This skill acts as a smart filter: it classifies the objective, skips discovery for common patterns, and runs a focused validation for novel concepts.\n\n## When to Use\n\n- Before writing a PRD for any new feature or product\n- When the solopreneur\u002FPM is unsure if an idea has legs\n- When the feature involves unfamiliar territory (new market, new UX paradigm, new business model)\n- The Product Agent should invoke this skill as a first step before PRD generation\n\n## Discovery Validation Procedure\n\n### Step 1: Classify Objective (Smart Filter)\n\nDetermine whether this feature needs discovery by matching it against known patterns.\n\n#### COMMON PATTERNS (skip discovery -- proceed directly to PRD)\n\nThese are well-understood, solved problems with established implementation patterns:\n\n- Authentication \u002F login \u002F signup \u002F password reset\n- CRUD operations (create, read, update, delete for any entity)\n- Notifications (email, push, in-app)\n- File uploads \u002F media management\n- Search \u002F filtering \u002F sorting\n- Pagination\n- Settings \u002F preferences pages\n- Admin panels \u002F dashboards\n- Payment integration (Stripe, PayPal)\n- User profiles \u002F account management\n- Comments \u002F ratings \u002F reviews\n- Tags \u002F categories \u002F labels\n- Export \u002F import (CSV, PDF, etc.)\n- Webhooks \u002F integrations with known services\n- Role-based access control (RBAC)\n- Audit logging\n- Internationalization (i18n)\n\nIf the objective matches a common pattern:\n\n> **Output**: \"Discovery skipped -- [feature] matches common pattern: [category]. Proceeding to PRD.\"\n\nExit the skill. No further steps needed.\n\n#### NOVEL CONCEPTS (full discovery required)\n\nThese involve genuine uncertainty about problem-solution fit:\n\n- New business model or pricing paradigm\n- New market segment the product has not served before\n- New UX paradigm (AI-powered interface, voice UI, AR\u002FVR)\n- Marketplace or multi-sided platform dynamics\n- AI\u002FML-powered features without precedent in the product\n- Social\u002Fcommunity features with network effects\n- Features requiring new data sources or partnerships\n- Anything the solopreneur describes as \"I have never built something like this\"\n- Gamification or behavioral mechanics\n- Content creation or collaboration tools with novel workflows\n\nIf the objective matches a novel concept, proceed to Step 2.\n\n#### UNCERTAIN\n\nIf the objective does not clearly fit either category, ask the user:\n\n> \"This feature sits between common and novel. Should I run discovery validation or proceed directly to PRD?\"\n\nRespect the user's decision.\n\n### Step 2: Lean Canvas (for NOVEL Concepts)\n\nProduce a one-page lean canvas covering all nine boxes. Be specific -- generic answers defeat the purpose.\n\n| Box | Prompt | Output |\n|-----|--------|--------|\n| **Problem** | What are the top 3 problems this feature solves? | Specific, observable problems with evidence |\n| **Customer Segments** | Who specifically has these problems? | Named persona(s) with context (role, company size, behavior) |\n| **Unique Value Proposition** | Single clear compelling message | One sentence that would make the target persona stop scrolling |\n| **Solution** | Top 3 features that address the problems | Concrete capabilities, not abstract descriptions |\n| **Channels** | How will users discover this feature? | Specific channels (in-app prompt, email campaign, blog post, word-of-mouth) |\n| **Revenue Streams** | How does this feature contribute to revenue? | Direct (new pricing tier, add-on) or indirect (retention, upsell trigger) |\n| **Cost Structure** | What are the build + ongoing costs? | Engineering time estimate, infrastructure costs, third-party service costs |\n| **Key Metrics** | What numbers prove this works? | 2-4 specific metrics with target values |\n| **Unfair Advantage** | What makes this defensible? | Data, network effects, domain expertise, integrations, brand |\n\n### Step 3: Competitive Quick-Scan\n\nIdentify 3-5 closest alternatives and analyze them:\n\nFor each alternative:\n- **Name**: Product or feature name\n- **How they solve the same problem**: Specific approach, not vague description\n- **Pricing**: Free, freemium, paid (with price point if known)\n- **Key differentiator**: What they do better than others\n\n**Gap Analysis**: What is missing from existing solutions? What do users complain about? Where is there whitespace?\n\n**Positioning**: How will our approach be different or better? What trade-offs are we making? Why would someone switch from an existing solution?\n\nUse WebSearch to find current competitors, recent reviews, and user complaints if needed. Do not fabricate competitor information -- if data is unavailable, state that explicitly.\n\n### Step 4: Risk Assessment\n\n#### Riskiest Assumption\n\nIdentify the ONE thing that, if wrong, kills this idea. Be specific:\n- Bad: \"Users might not want this\"\n- Good: \"Freelance designers earning $50-100K\u002Fyear will pay $29\u002Fmonth for AI-generated client proposals because they currently spend 5+ hours per proposal\"\n\n#### Validation Approach\n\nHow to test the riskiest assumption cheaply, before building:\n- Landing page with email capture (test demand)\n- Concierge MVP (manual delivery of the value proposition)\n- Survey of target persona (test willingness to pay)\n- Wizard-of-Oz prototype (fake the backend, real the frontend)\n- Competitor review mining (do users complain about the gap we would fill?)\n\n#### Problem Validation Questions\n\n| Question | How to Answer |\n|----------|---------------|\n| Who has this problem? | Specific persona with demographics and behavior |\n| How painful is it? (1-10 scale) | Evidence-based: time wasted, money lost, frustration signals |\n| How are they solving it today? | Current workarounds, tools, manual processes |\n| Will they pay for a better solution? | Willingness-to-pay signals: existing spend, stated intent, market comps |\n\n#### Go\u002FNo-Go Recommendation\n\nBased on the lean canvas, competitive scan, and risk assessment, provide one of three recommendations:\n\n- **Proceed to PRD**: Evidence supports building this. Riskiest assumption is testable and the upside justifies the cost.\n- **Validate first**: The idea has potential but the riskiest assumption is untested. Run the validation approach before committing to a PRD.\n- **Reconsider**: Multiple red flags -- strong competition with no clear differentiator, unclear demand, or high cost with uncertain return.\n\nInclude a clear rationale for the recommendation (2-3 sentences).\n\n### Step 5: Output\n\nAppend a \"Discovery Validation\" section to the PRD (this is NOT a separate artifact -- it lives within the PRD):\n\n```markdown\n## Discovery Validation\n\n**Classification**: NOVEL -- [reason why this needed discovery]\n**Lean Canvas**: [summary of the 9 boxes, or \"See full canvas above\"]\n**Competitive Landscape**: [3-5 alternatives with gap analysis summary]\n**Riskiest Assumption**: [the one specific thing that could kill this]\n**Validation Status**: Validated \u002F Needs Testing \u002F Risky\n**Recommendation**: Proceed to PRD \u002F Validate first \u002F Reconsider\n**Rationale**: [2-3 sentences explaining the recommendation]\n```\n\nIf discovery was skipped (common pattern), the PRD should include a brief note:\n\n```markdown\n## Discovery Validation\n\n**Classification**: COMMON PATTERN -- [category name]\n**Discovery**: Skipped. This is a well-understood pattern with established implementation approaches.\n```\n\n## Quality Checklist\n\n- [ ] Smart filter correctly classified the objective (common vs. novel)\n- [ ] If NOVEL: lean canvas is complete (all 9 boxes filled with specifics)\n- [ ] Competitive scan has 3-5 real alternatives (not generic or fabricated)\n- [ ] Riskiest assumption is specific and testable (not vague)\n- [ ] Problem validation questions are answered with evidence (not assumptions)\n- [ ] Go\u002FNo-Go recommendation is clear with rationale\n- [ ] If COMMON: skip is justified with pattern category\n- [ ] Output format matches the template (appended to PRD, not separate artifact)\n",{"name":5,"runtimes":40,"description":7},{"claude":41},{"user-invocable":36},"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4","os\u002Fskills\u002Fdiscovery-validation",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add vibbs\u002Fcompany-os --skill discovery-validation",{"tool":56,"command":57},"bunx","bunx skills add vibbs\u002Fcompany-os --skill discovery-validation",{"tool":59,"command":60},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill discovery-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fdiscovery-validation\u002FSKILL.md",true,[],[65,74,82,92,108,126],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":35},"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",[],[72,73],"typo field","fixture skill",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":35},"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",[],[81,73],"spaced comments",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":35},"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",[],[89,90,91,73],"crlf comments","CRLF","windows",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":35},"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",[],[99,100,101,102,103,104,73,105,106,107],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"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":119,"publishedAt":35},"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",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[120,121,122,123,124,32,125],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":35},"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",[],[133,134,135,123,32,136,137,138,139],"weekly review","review","priorities","health","save","support","security"]