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 placeholder that restates the skill name and category without providing any substantive information about what the skill does or when it should be used. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates multi-step approval workflows with configurable approval chains, escalation rules, conditional routing, and notification templates.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about approval processes, sign-off workflows, authorization chains, approval routing, or needs to automate document/request approvals.'
Include natural keyword variations users might say, such as 'approval process', 'sign-off', 'authorization workflow', 'approval chain', 'request approval', 'multi-level approval'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Approval Workflow Generator') and its category ('Business Automation') but lists no concrete actions like creating approval chains, routing rules, escalation paths, or notification setup. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line is just a duplicate of the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('approval workflow generator'). No natural user language variations like 'approval process', 'sign-off workflow', 'approval chain', or 'routing approvals' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'approval workflow' is somewhat specific and narrows the domain, but the lack of concrete actions or scope means it could overlap with general business automation or workflow 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 describes itself in abstract, repetitive terms without providing any actual instructions, code examples, workflow steps, or concrete guidance for generating approval workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code or configuration examples showing how to define an approval workflow (e.g., a JSON/YAML schema for approval stages, routing rules, and escalation paths).
Define a clear multi-step workflow: 1) gather requirements, 2) generate workflow definition, 3) validate the workflow, 4) deploy/test—with explicit validation checkpoints at each stage.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actionable content Claude can execute.
Include at least one complete input/output example showing a user request and the resulting 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 information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of actual workflow generation. The 'capabilities' section lists abstract promises rather than executable guidance. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. For a skill called 'Approval Workflow Generator,' there is no description of how to actually generate, configure, or validate an approval workflow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no separation of concerns. There is nothing to progressively disclose because there is no substantive content. | 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
3e83543
- 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.