Analyzes, redesigns, and automates business workflows to eliminate bottlenecks and improve efficiency. Creates process flow diagrams, identifies root-cause inefficiencies, writes standard operating procedures (SOPs), designs automation sequences, and produces implementation roadmaps with ROI estimates. Use when the user asks to map a business process, audit a workflow for inefficiencies, identify bottlenecks or handoff failures, create SOPs or checklists, design automation for repetitive tasks, apply Lean or Six Sigma techniques, or build a phased process improvement plan.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities, provides comprehensive trigger terms covering natural user language, and includes an explicit 'Use when...' clause with multiple concrete scenarios. The description is well-structured, uses third person voice throughout, and carves out a distinct niche in business process optimization that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzes/redesigns/automates workflows, creates process flow diagrams, identifies root-cause inefficiencies, writes SOPs, designs automation sequences, and produces implementation roadmaps with ROI estimates. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyzes workflows, creates diagrams, writes SOPs, designs automation, produces roadmaps) and 'when' with an explicit 'Use when...' clause listing seven specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'business process', 'workflow', 'bottlenecks', 'SOPs', 'checklists', 'automation', 'Lean', 'Six Sigma', 'process improvement plan', 'handoff failures'. These are terms practitioners and managers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around business process optimization with distinct triggers like 'Lean', 'Six Sigma', 'SOPs', 'workflow audit', and 'bottleneck' analysis that are unlikely to conflict with other skills such as general project management or coding automation. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides clear multi-step workflow guidance with explicit checkpoints, concrete decision criteria with specific thresholds, and appropriate progressive disclosure to supporting files. The main weakness is minor verbosity — some sections explain concepts or communication norms that Claude already understands, and the TIMWOOD expansion could be trimmed. Overall, it's a high-quality instructional skill that would effectively guide Claude through business process optimization.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and well-structured, but includes some unnecessary elaboration (e.g., spelling out TIMWOOD categories, the communication defaults section restates things Claude already knows about good analytical communication). Some tightening is possible without losing clarity. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: a specific decision tree for diagnosis, explicit threshold values (error rate >5%, automation potential >70%), a phased implementation matrix with time horizons, default improvement targets with percentages, and clear deliverable requirements. While there's no executable code, this is an instruction-only skill where the guidance is specific and directly usable. | 3 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced with explicit validation checkpoints at Steps 1, 3, and 4 (confirm baseline metrics, review future-state design, validate ROI assumptions). Each checkpoint includes feedback loops — e.g., 'If data is unavailable, use conservative estimates and flag assumptions.' The decision tree in Step 2 provides clear branching logic for diagnosis. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to AUTOMATION_GUIDE.md for detailed tooling mappings and TEMPLATE.md for the output structure. The main content stays at the right level of detail while deferring specifics appropriately. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
010799b
Table of Contents
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.