approval-workflow-generator
Approval Workflow Generator - Auto-activating skill for Business Automation. Triggers on: approval workflow generator, approval workflow generator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/approval-workflow-generator/SKILL.mdQuality
Discovery
7%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 is essentially a template placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other auto-generated business automation skill stubs.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates multi-step approval workflows with configurable routing rules, escalation paths, and notification templates.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks about creating approval processes, sign-off chains, authorization flows, or review routing for business operations.'
Include diverse natural trigger terms users would actually say, such as 'approval process', 'sign-off workflow', 'review chain', 'authorization steps', 'approval routing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Business Automation') and a tool name ('Approval Workflow Generator') but does not describe any concrete actions. There are no specific capabilities listed such as 'creates multi-step approval chains', 'configures routing rules', or 'generates notification templates'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and the 'when' clause is just a redundant trigger phrase rather than meaningful guidance. There is no explicit 'Use when...' clause with real trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'approval workflow generator' repeated twice. It misses natural variations users would say like 'approval process', 'sign-off workflow', 'review chain', 'approval routing', 'authorization flow', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'approval workflow' is somewhat specific and narrows the domain compared to generic 'business automation', but the lack of concrete actions and the broad category label could cause overlap with other workflow or automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no substantive content. It contains only meta-descriptions and trigger phrases but provides zero actionable guidance on how to actually generate approval workflows. It fails on every dimension because it teaches Claude nothing it doesn't already know and provides no concrete instructions, code, or examples.
Suggestions
Add concrete, executable code examples showing how to define and generate an approval workflow (e.g., a JSON/YAML schema for workflow steps, approvers, escalation rules).
Define a clear multi-step workflow: 1) gather requirements, 2) generate workflow definition, 3) validate the workflow, 4) output the result—with explicit validation checkpoints.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that only restate the skill name and replace them with actual implementation guidance.
Include at least one complete input/output example showing a user request and the corresponding generated approval workflow configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete steps, no examples of workflow definitions, no schemas. It only describes what the skill could do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. For a skill about generating approval workflows, there are no sequences, no validation checkpoints, and no process descriptions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to reference either. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.