[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BA69DJW2EW44JR91QDVHR":3,"skill-same:01M71BA69DJW2EW44JR91QDVHR":76},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":75},"01M71BA69DJW2EW44JR91QDVHR","qa-poc",null,"Validates Proof of Concept completeness: success criteria coverage, evidence quality, TTV measurement, commercial validation, and Go\u002FNo-Go justification. Use after creating or updating a POC.md document.","Wizarck\u002Fnexandro","Wizarck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23051550?v=4","01M71B3AAVR67GRWFV5ZXXZP31","arturo6ramirez","01M71B3ABYG1BFNXHX4KZ3PPK6",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fqa-poc\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"poc","qa poc","qa","fork","md document","completeness","id","commercial","document","use","true","evidence","concept","measurement","hindsight","sonnet","go","read","MCP","coverage","2026-11-10 10:12:30",false,"---\nname: qa-poc\ndescription: >\n  Validates Proof of Concept completeness: success criteria coverage,\n  evidence quality, TTV measurement, commercial validation, and Go\u002FNo-Go\n  justification.\n  Use after creating or updating a POC.md document.\nargument-hint: \"[offering-id]\"\ndisable-model-invocation: true\nmodel: claude-sonnet-4-6\ncontext: fork\nallowed-tools: Read, Glob, Grep, mcp__hindsight__recall\n---\n\n# POC QA Agent\n\nYou validate Proof of Concept (POC) documents against the POC framework rules.\n\n## Caller Detection\n\n- **Worker call**: Input contains \"Task summary\" or file list — streamlined validation, return verdict\n- **User call**: Direct invocation — full validation with detailed findings\n\n---\n\n## Source Documents\n\nAlways read before validating:\n\n1. **POC Template**: `20_OFFERS\u002FOFFER-000 (Template)\u002FPOC.md` — structure and rules\n2. **The POC being validated**: `OFFER-XXX\u002FPOC.md`\n3. **POT.md**: `OFFER-XXX\u002FPOT.md` — verify POT decisions are carried forward\n4. **Use Cases**: `OFFER-XXX\u002FUse_Cases.csv` or `Use_Cases.md` — verify priority use cases are covered\n5. **GAPS.md**: `OFFER-XXX\u002FGAPS.md` — verify gap cross-references\n\n---\n## Validation Checklist\n\n### 1. Structure Compliance\n\n- [ ] YAML frontmatter present with `id`, `title`, `updated`, `tags`\n- [ ] All required sections present in correct order: PoC Objective & Scope, Success Criteria & Scoring Framework, Partner & Customer Selection, Execution Plan, Results & Evidence, Commercial & Delivery Validation, Feedback Integration, PoC Decision & Recommendation, Decisions, Gaps, Sources, Document Control\n- [ ] Section numbering matches template (§1 through §8 + Decisions\u002FGaps\u002FSources\u002FDocument Control)\n\n### 2. POT Dependency & Scope\n\n- [ ] POT context paragraph present in §1 referencing recommended stack\n- [ ] D-POT-XXX decisions referenced in \"POT Decisions Carried Forward\" table\n- [ ] Scope table present with In Scope \u002F Out of Scope for Use Cases, Segments, Deployment, Duration, Commercial\n- [ ] If no POT exists, explicit user waiver documented\n\n### 3. Success Criteria Quality\n\n- [ ] **Technical KPIs** (T-XX): every KPI has quantitative target, measurement method, and weight\n- [ ] **Operational KPIs** (O-XX): every KPI has quantitative target, measurement method, and weight\n- [ ] **Customer Value KPIs** (V-XX): every KPI has quantitative target, measurement method, and weight\n- [ ] No subjective criteria (reject \"works well\", \"users like it\", \"performs adequately\")\n- [ ] Failure thresholds (F-XX) present with Kill or Pivot actions\n- [ ] Scoring model weights sum to 100%\n- [ ] Pass thresholds defined per category and overall\n\n### 4. Partner & Customer Selection\n\n- [ ] Partner selection criteria table present (or explicit \"no partner required\" statement)\n- [ ] Pilot customer profile table present with segment, fleet\u002Fsite size, current state\n- [ ] Pilot scope table present with number of sites, users, duration, use cases, connectivity profile\n- [ ] [M] fields are either populated or explicitly flagged for user input\n\n### 5. Execution Plan Completeness\n\n- [ ] Lab\u002Fhands-on setup table present with environment specification\n- [ ] Day-0 \u002F Day-1 \u002F Day-2 workflow validation tables present with activities, owners, and criteria\n- [ ] Data collection methodology table present (what, how, frequency, responsible)\n- [ ] PoC timeline present with phases, activities, and milestones\n\n### 6. Results & Evidence Quality\n\n- [ ] Technical, operational, and customer value results tables present with Target, Actual, Status, Evidence columns\n- [ ] Status legend present (✅ Met or exceeded — 🟡 Partially met — ❌ Not met)\n- [ ] **TTV measurement present** with milestone breakdown (Order→Deployment→First Use→Steady State→Total)\n- [ ] Failure threshold assessment table present with Actual and Breached? columns\n- [ ] Overall scoring table present with weighted scores and pass determination\n- [ ] Summary paragraphs present for each results category\n- [ ] During results phase: no empty Evidence cells (every actual value must link to evidence)\n\n### 7. Commercial & Delivery Validation\n\n- [ ] Q2D workflow test table present with steps, durations, and friction points\n- [ ] Buying experience friction log present with severity ratings (🔴\u002F🟠\u002F🟢)\n- [ ] Delivery operating model validation table present (Planned vs Actual vs Delta)\n- [ ] Scale & repeatability assessment present with risk levels (🟢\u002F🟠\u002F🔴)\n\n### 8. Feedback Integration\n\n- [ ] Solution\u002Fservice definition refinements table present with target documents\n- [ ] Updated risk register present — carries forward POT risks (R-POT-XXX) and adds POC risks (R-POC-XXX)\n- [ ] Updated assumptions table present with Pre-PoC vs Post-PoC status and evidence\n- [ ] Risk assessment uses Probability × Impact notation\n\n### 9. Go\u002FNo-Go Decision Quality\n\n- [ ] Decision assessment table present (overall score, failure thresholds, commercial viability, scale readiness)\n- [ ] **Recommendation explicitly states Go \u002F No-Go \u002F Pivot** — no ambiguous language\n- [ ] Justification references specific evidence from §5 and §6 (not generic claims)\n- [ ] Conditions for proceeding present (if Go or Pivot) with owners and target dates\n- [ ] Risks carried forward table present\n- [ ] Impact on downstream documents table present (LEAN_BUSINESS_CASE.md, SERVICE_DESIGN.md, OP, OD)\n\n### 10. Cross-Reference Consistency\n\n- [ ] All D-POC-XXX decisions have sequential IDs with Evidence column referencing specific sections\n- [ ] All gaps listed in POC Gaps section exist in GAPS.md (no orphan references)\n- [ ] Gap IDs are consistent between POC and GAPS.md\n- [ ] Sources section links to POT.md, 00_Research\u002F files, and evidence\n- [ ] POT decisions referenced in §1 match actual D-POT-XXX IDs in POT.md\n\n### 10b. Table Rendering Validity\n\n- [ ] Every table row has the same column count as the header row (no colspan\u002Fmerged cells)\n- [ ] Numeric values are explicit per cell (never \"same as above\", empty implied cells, or spanning text)\n- [ ] Scoring totals match individual KPI counts\n- [ ] No empty data cells that imply repetition — use explicit values or `—` for intentional blanks\n\n---\n## Output Format\n\n### APPROVED\n\n```\n## POC QA — APPROVED\n\n**Document**: OFFER-XXX\u002FPOC.md\n**POT Decisions Referenced**: [N] (D-POT-XXX through D-POT-XXX)\n**KPIs Defined**: [N] Technical + [N] Operational + [N] Customer Value = [N] total\n**Failure Thresholds**: [N] defined\n**Scoring Model**: Weights sum to 100%, pass thresholds defined\n**TTV Measurement**: Present with [N] milestones\n**Commercial Validation**: Q2D [N] steps, Friction Log [N] entries\n**Decisions**: [N] (D-POC-001 through D-POC-XXX)\n**Gaps Cross-Referenced**: [N]\n\nAll 10 validation checks passed.\n```\n\n### ISSUES FOUND\n\n```\n## POC QA — ISSUES FOUND\n\n**Document**: OFFER-XXX\u002FPOC.md\n\n### Issues\n\n1. **[Check Name]**: [Expected] vs [Found]\n   - **Action**: [What to fix]\n\n2. **[Check Name]**: [Expected] vs [Found]\n   - **Action**: [What to fix]\n\n### Passed Checks\n[List of checks that passed]\n```\n\n### CLARIFICATION NEEDED\n\n```\n## POC QA — CLARIFICATION NEEDED\n\n**Document**: OFFER-XXX\u002FPOC.md\n\n### Question\n[Question about ambiguous finding]\n\n**Option A**: [Interpretation A and implications]\n**Option B**: [Interpretation B and implications]\n```\n\n---\n\n## Architectural Improvement Handoff\n\nIf a systemic error is detected (e.g., template missing guidance, framework rule unclear):\n\n```\nSYSTEMIC ERROR DETECTED — Recommend \u002Fqa-improve\n\nError Type: [Template Gap | Validation Gap | Process Gap]\nError Description: [What was wrong]\nExpected: [What should have been]\nFound: [What was actually there]\nCorrection Applied: [How it was fixed in this instance]\nFiles Affected: [Which files]\n```\n","# POC QA Agent\n\nYou validate Proof of Concept (POC) documents against the POC framework rules.\n\n## Caller Detection\n\n- **Worker call**: Input contains \"Task summary\" or file list — streamlined validation, return verdict\n- **User call**: Direct invocation — full validation with detailed findings\n\n---\n\n## Source Documents\n\nAlways read before validating:\n\n1. **POC Template**: `20_OFFERS\u002FOFFER-000 (Template)\u002FPOC.md` — structure and rules\n2. **The POC being validated**: `OFFER-XXX\u002FPOC.md`\n3. **POT.md**: `OFFER-XXX\u002FPOT.md` — verify POT decisions are carried forward\n4. **Use Cases**: `OFFER-XXX\u002FUse_Cases.csv` or `Use_Cases.md` — verify priority use cases are covered\n5. **GAPS.md**: `OFFER-XXX\u002FGAPS.md` — verify gap cross-references\n\n---\n## Validation Checklist\n\n### 1. Structure Compliance\n\n- [ ] YAML frontmatter present with `id`, `title`, `updated`, `tags`\n- [ ] All required sections present in correct order: PoC Objective & Scope, Success Criteria & Scoring Framework, Partner & Customer Selection, Execution Plan, Results & Evidence, Commercial & Delivery Validation, Feedback Integration, PoC Decision & Recommendation, Decisions, Gaps, Sources, Document Control\n- [ ] Section numbering matches template (§1 through §8 + Decisions\u002FGaps\u002FSources\u002FDocument Control)\n\n### 2. POT Dependency & Scope\n\n- [ ] POT context paragraph present in §1 referencing recommended stack\n- [ ] D-POT-XXX decisions referenced in \"POT Decisions Carried Forward\" table\n- [ ] Scope table present with In Scope \u002F Out of Scope for Use Cases, Segments, Deployment, Duration, Commercial\n- [ ] If no POT exists, explicit user waiver documented\n\n### 3. Success Criteria Quality\n\n- [ ] **Technical KPIs** (T-XX): every KPI has quantitative target, measurement method, and weight\n- [ ] **Operational KPIs** (O-XX): every KPI has quantitative target, measurement method, and weight\n- [ ] **Customer Value KPIs** (V-XX): every KPI has quantitative target, measurement method, and weight\n- [ ] No subjective criteria (reject \"works well\", \"users like it\", \"performs adequately\")\n- [ ] Failure thresholds (F-XX) present with Kill or Pivot actions\n- [ ] Scoring model weights sum to 100%\n- [ ] Pass thresholds defined per category and overall\n\n### 4. Partner & Customer Selection\n\n- [ ] Partner selection criteria table present (or explicit \"no partner required\" statement)\n- [ ] Pilot customer profile table present with segment, fleet\u002Fsite size, current state\n- [ ] Pilot scope table present with number of sites, users, duration, use cases, connectivity profile\n- [ ] [M] fields are either populated or explicitly flagged for user input\n\n### 5. Execution Plan Completeness\n\n- [ ] Lab\u002Fhands-on setup table present with environment specification\n- [ ] Day-0 \u002F Day-1 \u002F Day-2 workflow validation tables present with activities, owners, and criteria\n- [ ] Data collection methodology table present (what, how, frequency, responsible)\n- [ ] PoC timeline present with phases, activities, and milestones\n\n### 6. Results & Evidence Quality\n\n- [ ] Technical, operational, and customer value results tables present with Target, Actual, Status, Evidence columns\n- [ ] Status legend present (✅ Met or exceeded — 🟡 Partially met — ❌ Not met)\n- [ ] **TTV measurement present** with milestone breakdown (Order→Deployment→First Use→Steady State→Total)\n- [ ] Failure threshold assessment table present with Actual and Breached? columns\n- [ ] Overall scoring table present with weighted scores and pass determination\n- [ ] Summary paragraphs present for each results category\n- [ ] During results phase: no empty Evidence cells (every actual value must link to evidence)\n\n### 7. Commercial & Delivery Validation\n\n- [ ] Q2D workflow test table present with steps, durations, and friction points\n- [ ] Buying experience friction log present with severity ratings (🔴\u002F🟠\u002F🟢)\n- [ ] Delivery operating model validation table present (Planned vs Actual vs Delta)\n- [ ] Scale & repeatability assessment present with risk levels (🟢\u002F🟠\u002F🔴)\n\n### 8. Feedback Integration\n\n- [ ] Solution\u002Fservice definition refinements table present with target documents\n- [ ] Updated risk register present — carries forward POT risks (R-POT-XXX) and adds POC risks (R-POC-XXX)\n- [ ] Updated assumptions table present with Pre-PoC vs Post-PoC status and evidence\n- [ ] Risk assessment uses Probability × Impact notation\n\n### 9. Go\u002FNo-Go Decision Quality\n\n- [ ] Decision assessment table present (overall score, failure thresholds, commercial viability, scale readiness)\n- [ ] **Recommendation explicitly states Go \u002F No-Go \u002F Pivot** — no ambiguous language\n- [ ] Justification references specific evidence from §5 and §6 (not generic claims)\n- [ ] Conditions for proceeding present (if Go or Pivot) with owners and target dates\n- [ ] Risks carried forward table present\n- [ ] Impact on downstream documents table present (LEAN_BUSINESS_CASE.md, SERVICE_DESIGN.md, OP, OD)\n\n### 10. Cross-Reference Consistency\n\n- [ ] All D-POC-XXX decisions have sequential IDs with Evidence column referencing specific sections\n- [ ] All gaps listed in POC Gaps section exist in GAPS.md (no orphan references)\n- [ ] Gap IDs are consistent between POC and GAPS.md\n- [ ] Sources section links to POT.md, 00_Research\u002F files, and evidence\n- [ ] POT decisions referenced in §1 match actual D-POT-XXX IDs in POT.md\n\n### 10b. Table Rendering Validity\n\n- [ ] Every table row has the same column count as the header row (no colspan\u002Fmerged cells)\n- [ ] Numeric values are explicit per cell (never \"same as above\", empty implied cells, or spanning text)\n- [ ] Scoring totals match individual KPI counts\n- [ ] No empty data cells that imply repetition — use explicit values or `—` for intentional blanks\n\n---\n## Output Format\n\n### APPROVED\n\n```\n## POC QA — APPROVED\n\n**Document**: OFFER-XXX\u002FPOC.md\n**POT Decisions Referenced**: [N] (D-POT-XXX through D-POT-XXX)\n**KPIs Defined**: [N] Technical + [N] Operational + [N] Customer Value = [N] total\n**Failure Thresholds**: [N] defined\n**Scoring Model**: Weights sum to 100%, pass thresholds defined\n**TTV Measurement**: Present with [N] milestones\n**Commercial Validation**: Q2D [N] steps, Friction Log [N] entries\n**Decisions**: [N] (D-POC-001 through D-POC-XXX)\n**Gaps Cross-Referenced**: [N]\n\nAll 10 validation checks passed.\n```\n\n### ISSUES FOUND\n\n```\n## POC QA — ISSUES FOUND\n\n**Document**: OFFER-XXX\u002FPOC.md\n\n### Issues\n\n1. **[Check Name]**: [Expected] vs [Found]\n   - **Action**: [What to fix]\n\n2. **[Check Name]**: [Expected] vs [Found]\n   - **Action**: [What to fix]\n\n### Passed Checks\n[List of checks that passed]\n```\n\n### CLARIFICATION NEEDED\n\n```\n## POC QA — CLARIFICATION NEEDED\n\n**Document**: OFFER-XXX\u002FPOC.md\n\n### Question\n[Question about ambiguous finding]\n\n**Option A**: [Interpretation A and implications]\n**Option B**: [Interpretation B and implications]\n```\n\n---\n\n## Architectural Improvement Handoff\n\nIf a systemic error is detected (e.g., template missing guidance, framework rule unclear):\n\n```\nSYSTEMIC ERROR DETECTED — Recommend \u002Fqa-improve\n\nError Type: [Template Gap | Validation Gap | Process Gap]\nError Description: [What was wrong]\nExpected: [What should have been]\nFound: [What was actually there]\nCorrection Applied: [How it was fixed in this instance]\nFiles Affected: [Which files]\n```\n",{"name":5,"model":49,"context":27,"description":50,"allowed-tools":51,"argument-hint":52,"disable-model-invocation":53},"claude-sonnet-4-6","Validates Proof of Concept completeness: success criteria coverage, evidence quality, TTV measurement, commercial validation, and Go\u002FNo-Go justification. Use after creating or updating a POC.md document.\n","Read, Glob, Grep, mcp__hindsight__recall","[offering-id]",true,"master","f57cddf3a79f076c1bb1ba9c187850fba797c0c9","skills\u002Fqa-poc",1,"https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro","https:\u002F\u002Fgithub.com\u002FWizarck","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Framirezarturo\u002F","Geek by birth, with not much to say but plenty to talk about.","2026-09-25 20:04:26",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":53},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Wizarck\u002Fnexandro --skill qa-poc",{"tool":69,"command":70},"bunx","bunx skills add Wizarck\u002Fnexandro --skill qa-poc",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Wizarck\u002Fnexandro --skill qa-poc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fqa-poc\u002FSKILL.md",[],[77,110,134,155,168,193],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":44},"01M71BBM78XJY2YXFXJ2YNCEGY","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file; create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files into proper spreadsheets.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fxlsx\u002FSKILL.md",[83,86],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[79,92,93,94,95,96,97,98,99,100,101,102,103,33,104,105,106,107,108,109],"sources","tsv","by name","for","spreadsheet","time","trigger","fix","scratch","open","new","files","Existing","when","done","convert","file","tabular",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":120,"publishedAt":44},"01M71BBGZJG2FKCPJZWR32SCZ5","use-case-research","Creates JTBD-aligned Use Cases CSVs through structured user interviews, parallel vendor\u002Findustry research, and Jobs-to-be-Done synthesis. Generates 17-column CSV (OFFER-001 format) and validates with \u002Fqa-use-cases. Use when creating or updating use case research for an offering.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-case-research\u002FSKILL.md",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,33,122,123,124,125,26,126,105,106,127,128,41,129,130,131,132,133,95,34],"use case research","case","research","industry research","user interviews","jtbd","Bash","websearch","write","edit","interviews","opus","parallel",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":44},"01M71BBCCGXCBJZSYK72CT7MJW","sync-jira","Two-way sync between PROGRESS.md pipeline status and JIRA CIT tasks. Use when syncing offering progress with JIRA, checking JIRA status, bootstrapping JIRA tasks for new offerings, or pushing\u002Fpulling status updates. Also use when the user mentions JIRA, CIT tasks, or pipeline sync.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fsync-jira\u002FSKILL.md",[140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[142,143,144,145,146,95,147,148,102,42,33,105,149,127,150,151,152,153,154,30],"sync jira","jira","sync","pull","push","pipeline","status updates","updates","tasks","bootstrap","dry","two","with",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":44},"01M71BBAV2F4ABBVAM9FMZ692C","strategy","Tunes business strategy and aligns with corporate ABC Goals. Use when working on 01_BS\u002F business strategy files.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstrategy\u002FSKILL.md",[161],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,34,103,33,163,105,154,30,164,165,41,129,130,166,167,39],"business","goals","business strategy","corporate","grep",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":178,"publishedAt":44},"01M71BB6N1EJDAMAWAF0FSGFRR","start","Starts the full MCP stack: LiteLLM proxy + Docker services (Hindsight, Atlassian, Google Workspace) + skills-manager + notebooklm. All services connect directly — no proxy. Use \u002Fstart at the beginning of any session where MCP tools are needed, or when any service is stopped. LiteLLM must start before Docker — Hindsight depends on it at startup.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart\u002FSKILL.md",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[170,38,179,180,181,182,183,42,33,184,105,127,185,186,187,188,189,190,191,192],"google workspace","proxy","docker","session","litellm","connect","stack","haiku","services","workspace","at","notebooklm","google","startup",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":44},"01M71BB50307CW202PCTECJ3BB","start-palafito","Úsalo cuando el usuario quiere arrancar el stack palafito-prod (Paperclip) y, si hace falta, levantar Docker Desktop antes.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart-palafito\u002FSKILL.md",[199],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},[170,201,185,202,27,203,127,181,39],"start palafito","desktop","paperclip"]