process-mapper

Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.

Quality

89%

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

78%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.

A well-structured, actionable skill body with strong progressive disclosure and a clear sequenced workflow. The main weakness is mild verbosity from restated theory and threshold duplication, plus the lack of a complete worked end-to-end example.

Suggestions

Consolidate the cycle-time verdict thresholds (VA% > 25% / 10–25% / < 10%) into one location instead of repeating them in both the Workflow and Scripts sections.

Trim the inline canon citations in the forcing-question library (Goldratt 1984, Rother & Shook, etc.) since the full Lean/Six Sigma canon already lives in references/lean_six_sigma_canon.md.

Add a single end-to-end quick example that runs a sample input JSON through process_documenter.py, bottleneck_detector.py, and cycle_time_analyzer.py with expected output snippets.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but restates Lean/Theory-of-Constraints theory inline (e.g., the forcing-question canon citations) and repeats the cycle-time thresholds across the Workflow and Scripts sections.	4 / 5
Actionability	Concrete script flags (--sample, --profile saas/services/manufacturing/healthcare) and detection thresholds (P50 > 2× mean, wait% > 40%, rework% > 15%) are executable, with a copy-paste quick example; the minor gap is no full end-to-end worked example with a real input file run through all three scripts.	4 / 5
Workflow Clarity	A clear five-step sequence (Intake→Map→Measure→Detect→Recommend) with forcing-question gates and verdict thresholds, plus an instrument-first validation gate in Assumption #1; lacks an explicit validate→fix→retry feedback loop, but the task is analytical rather than destructive.	4 / 5
Progressive Disclosure	The body is a well-sectioned overview with one-level-deep, clearly signaled references; all referenced files exist and content is appropriately split (canon in references/, template in assets/, logic in scripts/).	5 / 5
	Total	17 / 20 Passed

Description

100%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.

A strong, specific description that answers what and when with concrete trigger phrases and explicit distinctiveness guidance. No meaningful gaps to address.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'document an end-to-end business process', 'measure cycle times by stage', 'produce a process map, a ranked bottleneck list… and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput)' — with comprehensive coverage and no gaps.	5 / 5
Completeness	An explicit 'Use when…' clause gives concrete trigger guidance, and the 'what' is fully specified (process map, ranked bottleneck list, cycle-time analysis), satisfying both halves clearly.	5 / 5
Trigger Term Quality	Natural phrases a BizOps lead would say ('bottleneck', 'cycle times', 'procurement', 'employee onboarding', 'claims adjudication', 'BPMN', 'value-add ratio') are present with synonyms and domain variations.	5 / 5
Distinctiveness Conflict Risk	An explicit 'Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work' clause carves out a clear internal-operations niche with minimal conflict risk.	5 / 5
	Total	20 / 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/process-mapper/SKILL.md
Commit: 19392f7

Reviewed: ~13 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.