Guide · Agent skill
How to use the Business Operations Orchestrator agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Business Operations Orchestrator is an agent skill, a packaged set of instructions that changes how an AI agent handles a type of work. This one covers internal business operations: process bottlenecks, vendor health, capacity planning, internal announcements, SOP and runbook writing, and procurement spend. This guide explains what the skill does, how to install it, how to phrase requests so it activates, and what to expect back.
Business Operations Orchestratoralirezarezvani/claude-skills · MIT Download the skill Quick start
- 1Download the ZIP. Get the business-operations-skills ZIP from this directory page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into .claude/skills/ in a project folder.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Describe your operations problem. State the problem in plain language, naming any files or deadlines, such as a Q3 capacity question or a vendor SLA.
- 5Answer the one clarifying question if asked. If the request is ambiguous, the agent will name two candidate lanes and recommend one. Confirm or override it.
- 6Review the digest. Check the findings, next actions and challenge question, then decide whether to run a follow-up lane.
What the skill makes the agent do
The skill turns the agent into a router for internal operations work. When your request fits internal operations, the agent picks one of six specialist sub-skills: process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, or procurement-optimizer.
The skill runs its work in a forked context, meaning a separate working context, so heavy material such as vendor catalogs, process interviews or SOP source documents stays out of your main conversation. The parent conversation then receives a digest of no more than about 200 words, with top findings, next actions, the path to any artifacts produced, and one challenge question.
- Process: bottlenecks, cycle time, handoffs, process maps
- Vendors: SLA delivery, contracts, renewals, third-party risk
- Capacity: headcount, utilization, hiring sequence, FTE planning
- Internal comms: all-hands, announcements, change management, FAQs
- Knowledge: SOPs, runbooks, playbooks, onboarding docs
- Procurement: spend categorization, software audits, SaaS sprawl
Install the skill from ZIP or the Claude apps
Option one: download the ZIP from this directory page and unzip it into your personal skills folder, ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill only for that project.
Option two: in the Claude apps, open Settings, go to Capabilities, then Skills, and upload the skill there.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills, then upload
~/.claude/skills/Trigger the skill with natural requests
You do not need a special command. Describe the operations problem in plain language. The skill's description lists trigger phrases such as 'BizOps review', 'where's the bottleneck', 'vendor health', 'internal SOP', 'all-hands deck', 'spend categorization', 'capacity for Q3' and 'process mapping'.
Name the artifacts you have when you can, such as a file called procurement-Q3.csv. The skill treats clear filenames and wording as routing signals, so it can often choose a lane without asking anything.
- Clear: 'Is this vendor delivering against the SLA? Here is the contract summary.'
- Clear: 'Write me a runbook for the incident response process.'
- Clear: 'Why is our software spend up this year? Here is the export.'
- Vague: 'Help with operations.' The agent will ask one question before routing.
Understand how routing and clarifying questions work
The skill classifies your request by signals in the prompt. Two matching signals give a confident route. If only one signal matches, or no lane reaches two, the agent asks one clarifying question that names the two most likely candidates and gives a recommended answer. It is designed not to guess silently.
If a request crosses two lanes, such as a vendor SLA review plus a spend audit, the agent runs the higher-confidence sub-skill first and asks your permission before running the second.
Expect challenge questions grounded in management literature
Before some analyses, the skill may ask a single forcing question with a recommended answer. Examples from its instructions include asking whether you have measured cycle times or only estimates before process mapping, and whether vendor tiering should use spend or operational dependency. The skill cites canon such as Goldratt's Theory of Constraints, Little's Law, Womack and Jones, and Gartner TPRM.
The skill file names these sources, but the reference documents it points to were not included in the material reviewed, so the depth of those citations could not be checked.
Requirements and safety notes
The listing states that the skill requires nothing beyond the agent itself, runs no scripts and uses no network. The skill file says it assumes an organization with at least 10 employees and that you either have the data or accept templated dummy data.
The skill file also says its sub-skills ship stdlib-only Python tools. That conflicts with the 'runs scripts: no' listing, and the sub-skill files were not available to check, so review any scripts yourself before relying on them. The skill is operational analysis only. It is not legal review, so have a qualified professional check vendor contracts.
- Confirm the skill runs no scripts before you rely on it, given the conflicting note
- Keep sensitive vendor or spend data within the policies your organization sets
- Treat outputs as analysis to verify, not as legal or contract advice
Tips for better results
Give the skill measured data where you have it. Its guidance favors measured cycle times over estimates. The skill does not store state across sessions, so paste or reference the context you need in each new conversation.
For SaaS and procurement reviews, keep the same export format between runs so results are comparable.
- Provide the top three longest process stages with measured times if available
- Say whether vendor criticality is about spend or about revenue impact if the vendor fails
- Ask for one lane at a time when you have several problems
What people use it for
- Finding where work waits longest in an approval process by mapping stages and handoffs
- Checking whether a vendor is meeting its SLA before a renewal conversation
- Drafting an SOP or incident runbook from a rough description of the process
- Categorizing a software spend export to find overlapping SaaS subscriptions
Frequently asked questions
How do I install the business-operations-skills agent skill?
Download the ZIP from this directory page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps you can instead go to Settings → Capabilities → Skills and upload it there.
Is the Business Operations Orchestrator skill free to use?
The skill is licensed under MIT, as stated on its listing. This guide does not state any price, so check the directory page for the current terms.
What does the business-operations-skills requirements list say?
The listing says it requires nothing beyond the agent, runs no scripts and uses no network. The skill file says it assumes an organization with at least 10 employees.
How is this different from business-growth or c-level-advisor?
The skill's own file says business-growth covers the external sales motion, while this skill is internal. c-level-advisor covers strategic COO judgment such as whether to restructure, while this skill is tactical, such as producing a process map with bottlenecks.
What tools do people use instead of this skill?
The skill's file says it is not a substitute for an ERP, a vendor management platform such as Vendr or Tropic, or a capacity-planning tool such as Float or Runn. Those tools may suit ongoing system-of-record work better than an agent skill.
Why does the agent ask a question instead of answering my request?
When your request matches only one signal or no lane reaches two matching signals, the skill asks one clarifying question with a recommended answer. This is by design, so the analysis is not based on a silent guess. Naming the files or context you have usually avoids the question.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits operations managers, COOs and teams who write SOPs or review SaaS spend and want a consistent, structured workflow inside their agent. It is less suited to external sales or growth strategy, to legal or contract decisions, or to anyone who needs the full behaviour of the six sub-skills verified, since only SKILL.md was available for review.
Download the skill