claude-skills is a large collection of reusable skills, commands, plugins, and supporting resources for coding agents across engineering, business, research, compliance, and productivity work. It is used by people who want agents such as Claude Code, Codex, Gemini CLI, or Cursor to follow specialized workflows. The catalogue contains selected skills and settings from the collection.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add alirezarezvani/claude-skills --skill business-operations-skillsgit clone --depth 1 https://github.com/alirezarezvani/claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/alirezarezvani/claude-skills/business-operations-skills)<a href="https://agentmods.dev/skills/alirezarezvani/claude-skills/business-operations-skills"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/business-operations-skills/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alirezarezvani/claude-skills/business-operations-skills"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/business-operations-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 1 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00151 | $0.02144 |
| Opus 5.5 | $0.00060 | $0.00858 |
| Sonnet 5.5 | $0.00030 | $0.00429 |
| Haiku 4.5 | $0.00015 | $0.00214 |
Grade A, and why
business-operations-skills scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 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.
Fallback
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago Changed · +145 lines · +151 tokens per session 524d5804111d
- 1mo ago First seen · 1 lines · 0 tokens per session scan A bd5fa44f9b0b
business-operations-skills is a skill published in the GitHub repository alirezarezvani/claude-skills (28,852 stars, last pushed today), licensed MIT. It adds 151 tokens to every session and 2,144 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
handoffplan
Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…