workflow-optimizer
Expert process improvement specialist focused on analyzing, optimizing, and automating workflows across all business functions for maximum productivity and efficiency
36
21%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./testing-workflow-optimizer/skills/SKILL.mdQuality
Discovery
14%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 description reads like a generic consultant tagline rather than a functional skill description. It relies heavily on buzzwords ('maximum productivity and efficiency', 'expert process improvement specialist') without specifying concrete actions, deliverables, or trigger conditions. It would be nearly impossible for Claude to reliably select this skill over others in a multi-skill environment.
Suggestions
Add a 'Use when...' clause with specific trigger scenarios, e.g., 'Use when the user asks to map a business process, identify workflow bottlenecks, create SOPs, or automate repetitive tasks.'
Replace vague language with concrete actions and deliverables, e.g., 'Creates process flow diagrams, identifies bottlenecks in workflows, designs automation sequences, and writes standard operating procedures.'
Narrow the scope or specify the domain to reduce conflict risk — 'across all business functions' is too broad. Consider specifying the types of workflows or industries, or at least the output formats (e.g., flowcharts, checklists, automation scripts).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, buzzword-heavy language like 'analyzing, optimizing, and automating workflows' and 'maximum productivity and efficiency' without listing any concrete actions. No specific deliverables or operations are mentioned. | 1 / 3 |
Completeness | The description vaguely addresses 'what' (analyzing/optimizing/automating workflows) but has no explicit 'when' clause or trigger guidance. The phrase 'across all business functions' is overly broad and provides no selection criteria. Missing a 'Use when...' clause caps this at 2, and the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'process improvement', 'workflows', 'automating', and 'optimizing' that users might mention, but lacks specific variations or concrete terms (e.g., 'bottleneck analysis', 'SOP', 'flowchart', 'lean', 'six sigma', 'automation scripts'). | 2 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'all business functions' and 'workflows' could overlap with virtually any business-oriented skill. There is nothing that carves out a distinct niche or differentiates it from general consulting, project management, or automation skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a verbose persona/role-play document rather than an actionable skill. It spends most of its token budget on personality traits, generic consulting methodology descriptions, and a large Python class that serves as a textbook example rather than practical tooling. The content explains many concepts Claude already knows and lacks the concrete, specific guidance needed to actually optimize a workflow.
Suggestions
Cut the content by 70%+ by removing personality/identity sections, concepts Claude already knows (Lean, Six Sigma definitions, what RPA is), and the 'Success Metrics' and 'Advanced Capabilities' sections that add no actionable value.
Replace the generic Python framework with a concise, specific workflow analysis checklist or decision tree that Claude can directly apply when a user asks for process optimization.
Split the deliverable template and any detailed methodology into separate referenced files to improve progressive disclosure.
Add explicit validation checkpoints to the workflow process, such as 'Verify baseline metrics with stakeholder before proceeding to optimization design' and 'Validate automation ROI assumptions before implementation planning.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Explains concepts Claude already knows (Lean, Six Sigma, what RPA is, what bottlenecks are). The massive Python class is a generic textbook example that doesn't provide project-specific value. Sections like 'Your Identity & Memory', 'Communication Style', and 'Learning & Memory' are padded personality descriptions that waste tokens. | 1 / 3 |
Actionability | The Python code example is technically executable but is a generic framework rather than actionable guidance for a specific task. The workflow steps and deliverable template provide some structure, but they read more like abstract consulting methodology descriptions than concrete instructions Claude can act on. No specific tool commands or integration examples are given. | 2 / 3 |
Workflow Clarity | The 4-step workflow process is listed with reasonable sequencing, but lacks explicit validation checkpoints or feedback loops. There's no 'if X fails, do Y' guidance. The steps are high-level descriptions rather than actionable sequences with verification points. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. The massive Python code block, deliverable template, advanced capabilities, success metrics, and communication style are all crammed into a single file with no references to external documents. Content that could be split (e.g., the Python framework, the report template, advanced capabilities) is all presented inline. | 1 / 3 |
Total | 6 / 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 | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- Reviewed
Table of Contents
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.