[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AZSWNWPRD7YM3GGCE7CADK":3,"skill-same:01M7AZSWNWPRD7YM3GGCE7CADK":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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M7AZSWNWPRD7YM3GGCE7CADK","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).","Bhomik04\u002Fava-","Bhomik04","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110253138?v=4","01M7AZ8PC968MDM5Y1W13JHHBN","bhomik goyal","01M7AZ8PDERKY1AFG9VZ8J0WSX",0,"MIT","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fbusiness-operations-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24,"author":34,"context":35,"license":15,"version":36,"description":7,"compatible_tools":37},[25,26,27,28,29,30,31,32,33],"bizops","operations","process","vendor","capacity","sop","procurement","coo","orchestrator","claude-code-skills","fork","2.8.0",[38,39,40,41,42,43],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","decebbc662d2b278167b2a17d949479cf4cad66d","skills\u002Fimported\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fbusiness-operations-skills","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-","https:\u002F\u002Fgithub.com\u002FBhomik04","2026-08-23 16:08:45",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Bhomik04\u002Fava- --skill business-operations-skills",{"tool":56,"command":57},"bunx","bunx skills add Bhomik04\u002Fava- --skill business-operations-skills",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Bhomik04\u002Fava- --skill business-operations-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fclaude-skills\u002Fbusiness-operations\u002Fskills\u002Fbusiness-operations-skills\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"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":19},"01M7B1YZ6EW9K9QQX1VYBXKKWH","spotify-dj","Intelligent music DJ that curates playlists, selects tracks based on mood, analyzes genres, and manages playback queues.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fspotify-dj\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B1YWTNAF22PTEWNDGXQD9G","software-engineer","Autonomous software engineering, AST refactoring, Git worktree isolation, and self-healing test execution.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fsoftware-engineer\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B1YS4HDDEFEJXBB8KW4T3K","obsidian-curator","Curates, organizes, links, and summarizes notes and research in the local Obsidian vault.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fobsidian-curator\u002FSKILL.md",[],[],{"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":92,"publishedAt":19},"01M7B1YPJYQGB10P4EQ4SFEBFM","document-analysis","Parses, reads, extracts data, and summarizes multi-format documents (PDF, DOCX, Markdown, Text).","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdocument-analysis\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7B1YJPE6J8PEWQRSRSHJ03C","docker-ops","Inspects, monitors, starts, stops, and diagnoses Docker containers and swarms via Named Pipe.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdocker-ops\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7B1YEG3JESA4JPJNMVM1556","deep-research","Conducts multi-step autonomous research, source cross-verification, and structured literature synthesis.","https:\u002F\u002Fgithub.com\u002FBhomik04\u002Fava-\u002Fblob\u002Fmain\u002Fskills\u002Fofficial\u002Fdeep-research\u002FSKILL.md",[],[]]