[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QB2REA5QZAC1E5KDW8T29Z":3,"skill-same:01M6QB2REA5QZAC1E5KDW8T29Z":85},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6QB2REA5QZAC1E5KDW8T29Z","business-operations-skills",null,"Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP\u002Frunbook authoring, procurement spend. Triggers on \"BizOps review\", \"where's the bottleneck\", \"vendor health\", \"internal SOP\", \"all-hands deck\", \"spend categorization\", \"capacity for Q3\", \"process mapping\". Forks context to route to one of six BizOps sub-skills (process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, procurement-optimizer) and returns a digest. Distinct from business-growth (external sales motion) and c-level-advisor (strategic, not operational).","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-operations-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"business operations skills","business","operations","vendor-management","comms","for","strategic","triggers","authoring","digest","capacity planning","motion","use","internal comms","bottleneck","context","planner","knowledge","procurement","gemini","2026-11-10 10:12:30",false,"---\nname: business-operations-skills\ndescription: Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP\u002Frunbook authoring, procurement spend. Triggers on \"BizOps review\", \"where's the bottleneck\", \"vendor health\", \"internal SOP\", \"all-hands deck\", \"spend categorization\", \"capacity for Q3\", \"process mapping\". Forks context to route to one of six BizOps sub-skills (process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, procurement-optimizer) and returns a digest. Distinct from business-growth (external sales motion) and c-level-advisor (strategic, not operational).\ncontext: fork\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [bizops, operations, process, vendor, capacity, sop, procurement, coo, orchestrator]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Business Operations — Domain Orchestrator\n\nThe BizOps surface is **internal**: how the company actually runs. This orchestrator forks its conversation context, routes your inquiry to one of six sub-skills, then returns a tight digest to the parent thread. The heavy ingestion (vendor catalogs, process interviews, multi-doc SOP intake) stays in the forked context.\n\n## When to invoke\n\n| Symptom | Sub-skill to route to |\n|---|---|\n| \"Where does the work spend most of its time waiting?\" | `process-mapper` |\n| \"Is this vendor delivering against the SLA?\" | `vendor-management` |\n| \"Do we have enough people to ship in Q3?\" | `capacity-planner` |\n| \"I need to brief the company on a re-org\" | `internal-comms` |\n| \"Write me a runbook for the incident response process\" | `knowledge-ops` |\n| \"Why is our software spend up 40% YoY?\" | `procurement-optimizer` |\n\n## Routing logic (deterministic)\n\nThe orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | `process-mapper` |\n| **VENDOR** | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | `vendor-management` |\n| **CAPACITY** | headcount, capacity, utilization, planning, hiring sequence, FTE | `capacity-planner` |\n| **COMMS** | all-hands, internal newsletter, announcement, change management, FAQ, town hall | `internal-comms` |\n| **KNOWLEDGE** | SOP, runbook, knowledge base, wiki, playbook, documentation, onboarding doc | `knowledge-ops` |\n| **PROCUREMENT** | spend, procurement, purchase, supplier rationalization, software audit, SaaS sprawl | `procurement-optimizer` |\n\nIf signals are mixed (e.g., \"vendor SLA + spend audit\"), run the **highest-confidence sub-skill first**, then chain into the second one in a follow-up forked turn.\n\n### Fallback\n\nIf no signal class scores ≥ 2, ask **one** clarifying question naming the two most likely candidates. Do NOT guess silently.\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the documented canon** (`references\u002F`).\n\n### Step 1 — Explore before asking\n\nBefore any clarifying question, check:\n- Does the user's working directory already contain a process map, vendor catalog, SOP, or org chart we can grep?\n- Does the inquiry already disambiguate the lane (e.g., \"vendor SLA review\" — that's `vendor-management`, no question needed)?\n- Is the lane unambiguous from filenames mentioned (`procurement-Q3.csv` → procurement)?\n\nIf the codebase resolves the lane, **route silently**. Don't ask.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle questions. Never default to \"what do you think?\". Always offer your recommendation.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Cone-sentence rationale from the signal table>]\n\n(Confirm, or override?)\n```\n\nWait for the user's response. **Then** route. Never guess silently after a turn that asked a question.\n\n### Step 3 — Forking decision-tree walk (only if the inquiry crosses lanes)\n\nIf the user's inquiry legitimately crosses two lanes (e.g., \"vendor SLA + spend audit\" = VENDOR + PROCUREMENT), walk the tree **depth-first**:\n\n1. Resolve the higher-confidence lane first → run that sub-skill in forked context → return digest\n2. Ask: \"Should we now run [second lane]? My recommendation: yes, because [dependency reason].\"\n3. Only after explicit user confirmation, run the second sub-skill\n\nDo NOT chain silently. Each fork is an explicit user-confirmed step.\n\n### Step 4 — Invoke sub-skill in forked context\n\nEach sub-skill is invoked with the original prompt + a digest of any structured inputs (file paths, JSON inputs). The fork keeps heavy ingestion (vendor catalog, process transcripts, SOP source documents) out of the parent context.\n\n### Step 5 — Return digest with cited canon challenge\n\nWhen the sub-skill completes, return a **≤ 200-word digest** to the parent thread:\n\n- What was analyzed\n- Top 3 findings (each anchored in a reference doc citation — e.g., \"Goldratt's Theory of Constraints: optimize the bottleneck, not the non-constraint\")\n- Top 3 next actions (named owners if possible)\n- Path to the artifact(s) produced\n- **One grill challenge** for the user, cited: \"Your value-add ratio is 12%. Lean canon (Womack & Jones 1996) classifies \u003C15% as waste-heavy. What's blocking process redesign — political, technical, or budget?\"\n\nThe parent agent can then ask follow-ups (each triggering new forked invocations).\n\n## Forcing-question library (grill-with-docs pattern)\n\nWhen the user has provided enough context to enter a lane, the orchestrator may grill them on the **decisions inside that lane** before invoking the sub-skill. One question per turn, each with a recommended answer + canon citation. Examples:\n\n- **PROCESS lane**: \"Before mapping: do you have measured cycle times per stage, or only estimates? Recommended: insist on measured data for the top-3 longest stages. Anti-pattern (Goldratt 1984): map estimates, optimize the wrong constraint.\"\n- **VENDOR lane**: \"Before scoring: what's your tier-1 criticality threshold — by spend ($X\u002Fyear), or by operational dependency (revenue-blocking if vendor fails)? Recommended: operational dependency. Anti-pattern (Gartner TPRM): spend-only tiering misses critical low-spend vendors like the HVAC vendor in the Target breach.\"\n- **CAPACITY lane**: \"Before modeling: are you planning for utilization or throughput? Recommended: throughput (Little's Law). Anti-pattern (DORA): planning for utilization > 80% destroys throughput via queueing.\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Assumptions\n\n1. The user is acting on behalf of an organization with ≥ 10 employees (smaller orgs don't need this surface).\n2. The user has access to the data the sub-skill needs (process docs, vendor list, spend export, etc.) — or accepts the skill's templated dummy data.\n3. The user wants **deterministic, repeatable analysis** over LLM-flavored prose. Every sub-skill ships stdlib-only Python tools.\n\n## Non-goals\n\n- Not a substitute for an ERP, vendor management platform (Vendr, Tropic), or capacity-planning SaaS (Float, Runn).\n- Does not store state across sessions — every invocation is self-contained.\n- Does not call external APIs from Python tools (stdlib only, by design).\n\n## Distinct from\n\n- **`business-growth\u002F*`** — that's the **external sales motion** (CSM, sales engineering, RevOps). BizOps is **internal**.\n- **`c-level-advisor\u002Fcoo-advisor`** — that's strategic COO judgment (\"should we restructure?\"). BizOps is tactical (\"here's the process map with bottlenecks\").\n- **`engineering\u002Fslo-architect`** — that's system reliability with SLO\u002FSLI\u002Ferror budgets. `process-mapper` is **business process** reliability, not system reliability.\n- **`engineering\u002Fllm-wiki`** — that's a **personal** PKM (Karpathy's pattern). `knowledge-ops` is **company-wide** SOP authoring.\n\n## Output artifacts\n\nEvery sub-skill produces at least one artifact (markdown, CSV, or JSON) saved to the user's working directory. The orchestrator surfaces the file path in the digest.\n\n## Anti-patterns (do not)\n\n- ❌ Run all 6 sub-skills \"to be thorough\" — pick one based on signal, return digest, let user chain\n- ❌ Auto-approve a vendor or process change — surface findings; the human decides\n- ❌ Edit production process docs without asking — write to a new file, propose the diff\n- ❌ Skip the digest step — parent context needs ≤ 200-word digest, not the full sub-skill output\n\n## References\n\n- See `c-level-advisor\u002Fcoo-advisor` for strategic COO framing\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fbizops-commercial-expansion-plan.md`\n","# Business Operations — Domain Orchestrator\n\nThe BizOps surface is **internal**: how the company actually runs. This orchestrator forks its conversation context, routes your inquiry to one of six sub-skills, then returns a tight digest to the parent thread. The heavy ingestion (vendor catalogs, process interviews, multi-doc SOP intake) stays in the forked context.\n\n## When to invoke\n\n| Symptom | Sub-skill to route to |\n|---|---|\n| \"Where does the work spend most of its time waiting?\" | `process-mapper` |\n| \"Is this vendor delivering against the SLA?\" | `vendor-management` |\n| \"Do we have enough people to ship in Q3?\" | `capacity-planner` |\n| \"I need to brief the company on a re-org\" | `internal-comms` |\n| \"Write me a runbook for the incident response process\" | `knowledge-ops` |\n| \"Why is our software spend up 40% YoY?\" | `procurement-optimizer` |\n\n## Routing logic (deterministic)\n\nThe orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | `process-mapper` |\n| **VENDOR** | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | `vendor-management` |\n| **CAPACITY** | headcount, capacity, utilization, planning, hiring sequence, FTE | `capacity-planner` |\n| **COMMS** | all-hands, internal newsletter, announcement, change management, FAQ, town hall | `internal-comms` |\n| **KNOWLEDGE** | SOP, runbook, knowledge base, wiki, playbook, documentation, onboarding doc | `knowledge-ops` |\n| **PROCUREMENT** | spend, procurement, purchase, supplier rationalization, software audit, SaaS sprawl | `procurement-optimizer` |\n\nIf signals are mixed (e.g., \"vendor SLA + spend audit\"), run the **highest-confidence sub-skill first**, then chain into the second one in a follow-up forked turn.\n\n### Fallback\n\nIf no signal class scores ≥ 2, ask **one** clarifying question naming the two most likely candidates. Do NOT guess silently.\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the documented canon** (`references\u002F`).\n\n### Step 1 — Explore before asking\n\nBefore any clarifying question, check:\n- Does the user's working directory already contain a process map, vendor catalog, SOP, or org chart we can grep?\n- Does the inquiry already disambiguate the lane (e.g., \"vendor SLA review\" — that's `vendor-management`, no question needed)?\n- Is the lane unambiguous from filenames mentioned (`procurement-Q3.csv` → procurement)?\n\nIf the codebase resolves the lane, **route silently**. Don't ask.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle questions. Never default to \"what do you think?\". Always offer your recommendation.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Cone-sentence rationale from the signal table>]\n\n(Confirm, or override?)\n```\n\nWait for the user's response. **Then** route. Never guess silently after a turn that asked a question.\n\n### Step 3 — Forking decision-tree walk (only if the inquiry crosses lanes)\n\nIf the user's inquiry legitimately crosses two lanes (e.g., \"vendor SLA + spend audit\" = VENDOR + PROCUREMENT), walk the tree **depth-first**:\n\n1. Resolve the higher-confidence lane first → run that sub-skill in forked context → return digest\n2. Ask: \"Should we now run [second lane]? My recommendation: yes, because [dependency reason].\"\n3. Only after explicit user confirmation, run the second sub-skill\n\nDo NOT chain silently. Each fork is an explicit user-confirmed step.\n\n### Step 4 — Invoke sub-skill in forked context\n\nEach sub-skill is invoked with the original prompt + a digest of any structured inputs (file paths, JSON inputs). The fork keeps heavy ingestion (vendor catalog, process transcripts, SOP source documents) out of the parent context.\n\n### Step 5 — Return digest with cited canon challenge\n\nWhen the sub-skill completes, return a **≤ 200-word digest** to the parent thread:\n\n- What was analyzed\n- Top 3 findings (each anchored in a reference doc citation — e.g., \"Goldratt's Theory of Constraints: optimize the bottleneck, not the non-constraint\")\n- Top 3 next actions (named owners if possible)\n- Path to the artifact(s) produced\n- **One grill challenge** for the user, cited: \"Your value-add ratio is 12%. Lean canon (Womack & Jones 1996) classifies \u003C15% as waste-heavy. What's blocking process redesign — political, technical, or budget?\"\n\nThe parent agent can then ask follow-ups (each triggering new forked invocations).\n\n## Forcing-question library (grill-with-docs pattern)\n\nWhen the user has provided enough context to enter a lane, the orchestrator may grill them on the **decisions inside that lane** before invoking the sub-skill. One question per turn, each with a recommended answer + canon citation. Examples:\n\n- **PROCESS lane**: \"Before mapping: do you have measured cycle times per stage, or only estimates? Recommended: insist on measured data for the top-3 longest stages. Anti-pattern (Goldratt 1984): map estimates, optimize the wrong constraint.\"\n- **VENDOR lane**: \"Before scoring: what's your tier-1 criticality threshold — by spend ($X\u002Fyear), or by operational dependency (revenue-blocking if vendor fails)? Recommended: operational dependency. Anti-pattern (Gartner TPRM): spend-only tiering misses critical low-spend vendors like the HVAC vendor in the Target breach.\"\n- **CAPACITY lane**: \"Before modeling: are you planning for utilization or throughput? Recommended: throughput (Little's Law). Anti-pattern (DORA): planning for utilization > 80% destroys throughput via queueing.\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Assumptions\n\n1. The user is acting on behalf of an organization with ≥ 10 employees (smaller orgs don't need this surface).\n2. The user has access to the data the sub-skill needs (process docs, vendor list, spend export, etc.) — or accepts the skill's templated dummy data.\n3. The user wants **deterministic, repeatable analysis** over LLM-flavored prose. Every sub-skill ships stdlib-only Python tools.\n\n## Non-goals\n\n- Not a substitute for an ERP, vendor management platform (Vendr, Tropic), or capacity-planning SaaS (Float, Runn).\n- Does not store state across sessions — every invocation is self-contained.\n- Does not call external APIs from Python tools (stdlib only, by design).\n\n## Distinct from\n\n- **`business-growth\u002F*`** — that's the **external sales motion** (CSM, sales engineering, RevOps). BizOps is **internal**.\n- **`c-level-advisor\u002Fcoo-advisor`** — that's strategic COO judgment (\"should we restructure?\"). BizOps is tactical (\"here's the process map with bottlenecks\").\n- **`engineering\u002Fslo-architect`** — that's system reliability with SLO\u002FSLI\u002Ferror budgets. `process-mapper` is **business process** reliability, not system reliability.\n- **`engineering\u002Fllm-wiki`** — that's a **personal** PKM (Karpathy's pattern). `knowledge-ops` is **company-wide** SOP authoring.\n\n## Output artifacts\n\nEvery sub-skill produces at least one artifact (markdown, CSV, or JSON) saved to the user's working directory. The orchestrator surfaces the file path in the digest.\n\n## Anti-patterns (do not)\n\n- ❌ Run all 6 sub-skills \"to be thorough\" — pick one based on signal, return digest, let user chain\n- ❌ Auto-approve a vendor or process change — surface findings; the human decides\n- ❌ Edit production process docs without asking — write to a new file, propose the diff\n- ❌ Skip the digest step — parent context needs ≤ 200-word digest, not the full sub-skill output\n\n## References\n\n- See `c-level-advisor\u002Fcoo-advisor` for strategic COO framing\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fbizops-commercial-expansion-plan.md`\n",{"name":5,"tags":44,"author":52,"context":53,"license":15,"version":54,"description":7,"compatible_tools":55},[45,21,46,47,48,49,37,50,51],"bizops","process","vendor","capacity","sop","coo","orchestrator","claude-code-skills","fork","2.8.0",[56,57,58,59,60,61],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fbusiness-operations-skills","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill business-operations-skills",{"tool":77,"command":78},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill business-operations-skills",{"tool":80,"command":81},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill business-operations-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbusiness-operations-skills\u002FSKILL.md",true,[],[86,117,141,168,192,215],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":39},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,24,114,115,116],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","browsing","request","youtube transcripts",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":39},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[124,125,126,127,102,128,129,130,131,132,133,134,135,136,31,137,138,139,140,24],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","platform","grow","posting","competitive",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":39},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",[151,135,152,153,154,155,156,157,31,158,159,62,160,161,162,163,164,165,166,167],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"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":174,"publishedAt":39},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[175,176,177,38,178,179,180,181,182,31,183,109,184,185,186,187,188,189,190,191],"wrap up","up","wrap","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":39},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[198],{"categoryNo":148,"categoryName":149,"taxonomyType":95,"taxonomyTypeDesc":96},[200,201,202,203,204,153,179,205,206,207,208,209,135,34,108,210,211,212,213,214],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","across","fresh","scripts","judge","claude code workflow",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":39},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[222,223,224,225,226,227,228,229,230,208,231,232,233,234,235,236,110,237,238,191],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]