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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill approval-workflow-generator36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/approval-workflow-generator/SKILL.mdDiscovery
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 severely underdeveloped, functioning more as a placeholder than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The only distinguishing element is the 'approval workflow' domain, but without specifics, Claude cannot reliably select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates multi-step approval chains, configures approval thresholds, routes requests to appropriate approvers, and sets up escalation rules.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions approval processes, sign-off workflows, authorization chains, request routing, or needs to automate document/request approvals.'
Add varied trigger terms users would naturally say: 'approval process', 'sign-off', 'authorization workflow', 'request approval', 'approval chain', 'escalation rules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Approval Workflow Generator') and its category ('Business Automation') without describing any concrete actions. No specific capabilities like 'creates approval chains', 'routes requests', or 'configures escalation rules' are mentioned. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or explicit trigger guidance). Only category membership is stated. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('approval workflow generator, approval workflow generator'). No natural user language variations like 'approval process', 'sign-off workflow', 'request approval', or 'authorization flow' are included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'approval workflow' is somewhat specific to a domain, the lack of concrete actions and the generic 'Business Automation' category could cause overlap with other automation-related skills. The repeated trigger term provides minimal differentiation. | 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 a generic placeholder template with no actual content about approval workflow generation. It lacks any concrete guidance, code examples, workflow definitions, or specific instructions. The content describes what the skill claims to do rather than actually teaching Claude how to do it.
Suggestions
Add concrete code examples showing how to define an approval workflow (e.g., JSON schema for workflow definition, routing rules, approver configuration)
Include a step-by-step workflow for creating an approval process: define stages → set approvers → configure escalation → add notifications → validate workflow
Provide specific examples of approval workflow patterns (sequential approval, parallel approval, conditional routing) with executable configurations
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual implementation details
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need and add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate an approval workflow or what one looks like. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. For a skill about generating approval workflows, there should be clear steps for defining approvers, routing logic, escalation rules, etc. Instead, it only lists vague 'capabilities' with no sequence or validation. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no structure for discovery. No references to detailed documentation, examples, or related files. The 'Related Skills' section mentions a category but provides no actual links or navigation. | 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 | |
- 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.