business-operations-skills
Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook 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-
Profile →npx skills add alirezarezvani/claude-skills --skill business-operations-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Business Operations — Domain Orchestrator The 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. ## When to invoke | Symptom | Sub-skill to route to | |---|---| | "Where does the work spend most of its time waiting?" | `process-mapper` | | "Is this vendor delivering against the SLA?" | `vendor-management` | | "Do we have enough people to ship in Q3?" | `capacity-planner` | | "I need to brief the company on a re-org" | `internal-comms` | | "Write me a runbook for the incident response process" | `knowledge-ops` | | "Why is our software spend up 40% YoY?" | `procurement-optimizer` | ## Routing logic (deterministic) The orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question. ### Signal table | Signal class | Keywords | Sub-skill | |---|---|---| | **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process m
- When to invoke
- Routing logic (deterministic)
- Signal table
- Fallback
- Workflow (Matt Pocock grill discipline)
- Step 1 — Explore before asking
- Step 2 — If still ambiguous, ONE forcing question with a recommended answer
- Step 3 — Forking decision-tree walk (only if the inquiry crosses lanes)
- Step 4 — Invoke sub-skill in forked context
- Step 5 — Return digest with cited canon challenge
- Forcing-question library (grill-with-docs pattern)
- Assumptions
- Non-goals
- Distinct from
What does the business-operations-skills skill do?
Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook 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-
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill business-operations-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.