approval-workflow-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill approval-workflow-generatorApproval Workflow Generator - Auto-activating skill for Business Automation. Triggers on: approval workflow generator, approval workflow generator Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 users would say, e.g., 'Use when the user mentions approval processes, sign-off workflows, authorization chains, request routing, or needs to set up manager approvals.'
Remove the duplicate trigger term and expand with variations like 'approval process', 'sign-off flow', 'authorization workflow', 'request approval system'.
| 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%This skill is an empty template that provides no actual guidance on generating approval workflows. It consists entirely of generic boilerplate text that could apply to any skill, with no concrete examples, code, workflow steps, or actionable instructions. The skill fails to teach Claude anything about approval workflow generation.
Suggestions
Add concrete code examples showing how to define approval workflow structures (e.g., JSON/YAML schema for workflow definition, state machine patterns)
Include a step-by-step workflow for generating approval processes: define approvers → set conditions → configure notifications → validate workflow → deploy
Provide specific examples of approval workflow patterns (sequential approval, parallel approval, conditional routing, escalation rules)
Add validation checkpoints and common pitfalls to avoid when generating approval workflows (e.g., circular dependencies, missing fallback approvers)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually generate an approval workflow. Zero executable content. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. For a skill about generating approval workflows, there's no sequence, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. No references to detailed documentation, examples, or related files. The sections present are organizational theater without substance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.