Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →alirezarezvani/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, procu
Passed 13 of 22 test cases with the skill, and 3 of 22 without it.
and 14 more in the full report
11 fixed3 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Provide an operational review digest of our internal escalation runbook.
| Checked | Without skill | With skill |
|---|---|---|
| Limits the summary digest to 200 words or fewer. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
| 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 |
The orchestrator classifies the inquiry by signals detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question.
| Signal class | Keywords | Sub-skill |
|---|---|---|
| PROCESS | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | process-mapper |
| VENDOR | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | vendor-management |
| CAPACITY | headcount, capacity, utilization, planning, hiring sequence, FTE | capacity-planner |
| COMMS | all-hands, internal newsletter, announcement, change management, FAQ, town hall | internal-comms |
| KNOWLEDGE | SOP, runbook, knowledge base, wiki, playbook, documentation, onboarding doc | knowledge-ops |
| PROCUREMENT | spend, procurement, purchase, supplier rationalization, software audit, SaaS sprawl | procurement-optimizer |
If 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.
If no signal class scores ≥ 2, ask one clarifying question naming the two most likely candidates. Do NOT guess silently.
Derived 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/).
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.