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-level-advisor (strategic, not operational).

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable orchestrator spec: deterministic routing logic, a forcing-question discipline with concrete templates, explicit workflow gates, and clear non-goals and anti-patterns. It is held back from top marks by mild verbosity in its process framing and the absence of formal validation/feedback loops or a richer bundle structure.

Suggestions

Tighten the 'Workflow (Matt Pocock grill discipline)' preamble and the forcing-question rationales — keep the citations but drop the meta-commentary about the pattern itself to improve conciseness.

Add an explicit fork-invocation example or syntax so the routing is fully copy-paste executable rather than implied.

Formalize the bottom 'References' section into clearly signaled one-level links (e.g., a 'See also' list with paths and one-line purposes) rather than two loose bullet points.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational (signal tables, deterministic thresholds, templates, anti-patterns) and the canon citations (Goldratt, Little's Law, Womack & Jones) serve the grill discipline rather than explaining concepts Claude already knows, though the 'Matt Pocock grill discipline' framing and verbose forcing-question rationales could be trimmed.	4 / 5
Actionability	Provides concrete, executable routing guidance — a keyword-to-sub-skill signal table, a two-signal threshold, a literal forcing-question template, and a specified digest format — with example grill questions covering each lane; absence of code is acceptable for an instruction-only orchestrator, with minor gaps in fork-invocation syntax.	4 / 5
Workflow Clarity	A clear five-step sequence (Explore → forcing question → forking decision-tree walk → invoke sub-skill → return digest) with explicit user-confirmation gates ('Never run a sub-skill until the lane-defining decision is locked', 'Each fork is an explicit user-confirmed step'); not a destructive/batch operation so the validation cap does not apply, though there is no formal error-recovery feedback loop.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, and references are one-level-deep and signaled (pointing to other skills and an implementation plan rather than nested bundle files, none of which exist here); the loose bottom 'References' section is a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit 'Use when' trigger guidance with numerous natural phrases, concrete enumeration of the six sub-domains, and clear differentiation from neighboring skills. The only minor weakness is that some listed items read as domain nouns rather than crisp actions, keeping specificity just below a perfect score.

Dimension	Reasoning	Score
Specificity	Lists six concrete operation domains (process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook authoring, procurement spend) plus orchestrator actions ('Forks context to route', 'returns a digest'), giving multiple specific actions with near-comprehensive coverage, though several items are domain nouns rather than pure verb-actions.	4 / 5
Completeness	Explicitly answers both 'what' ('Forks context to route to one of six BizOps sub-skills... and returns a digest') and 'when' ('Use when running, diagnosing, or designing internal business operations' plus concrete 'Triggers on' phrases), matching the anchor for clearly answering both.	5 / 5
Trigger Term Quality	The 'Triggers on' clause supplies eight natural user phrases ('where's the bottleneck', 'vendor health', 'internal SOP', 'all-hands deck', 'capacity for Q3', 'process mapping') spanning all six lanes — comprehensive coverage of phrases a user would actually say.	5 / 5
Distinctiveness Conflict Risk	It carves a clear internal-operations niche and explicitly names what it is NOT ('Distinct from business-growth (external sales motion) and c-level-advisor (strategic, not operational)'), minimizing conflict risk with adjacent skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: business-operations/skills/business-operations-skills/SKILL.md
Commit: 19392f7

Reviewed: ~14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.