api-flow-diagram-creator
Api Flow Diagram Creator - Auto-activating skill for Visual Content. Triggers on: api flow diagram creator, api flow diagram creator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/api-flow-diagram-creator/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 meaningful information about capabilities, actions, or trigger conditions. It fails to help Claude distinguish when to select this skill, offering no concrete actions, no 'Use when' guidance, and only a duplicated trigger term.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates visual diagrams showing API request/response flows, endpoint interactions, authentication sequences, and data flow between services.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to visualize API flows, create sequence diagrams for REST endpoints, map microservice interactions, or diagram request/response patterns.'
Include common keyword variations users might say, such as 'API diagram', 'sequence diagram', 'endpoint flow', 'REST flow chart', 'microservice diagram', 'API architecture visualization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Api Flow Diagram Creator') and its category ('Visual Content') but does not describe any concrete actions like 'generates sequence diagrams', 'maps API endpoints', or 'visualizes request/response flows'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('api flow diagram creator'). It lacks natural user phrases like 'API diagram', 'flow chart', 'sequence diagram', 'endpoint visualization', 'REST flow', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'api flow diagram' is somewhat specific to a niche (API flow diagrams vs. general diagrams), but the lack of detail means it could overlap with general diagramming or visualization skills without clear 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 an empty shell with no actual content. It consists entirely of auto-generated boilerplate that restates the skill name in various ways without providing any actionable guidance, code examples (e.g., Mermaid diagram syntax for API flows), or workflow steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of API flow diagrams using Mermaid or similar syntax (e.g., a sequence diagram showing request/response flow between client, API gateway, and backend services).
Define a clear workflow: 1) Identify API endpoints and actors, 2) Choose diagram type (sequence, flowchart), 3) Write diagram code, 4) Validate rendering.
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) that merely restate the skill name and replace with actual instructional content.
Include at least one complete, copy-paste-ready Mermaid code block showing a typical API flow diagram with annotations explaining the pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It repeatedly restates the skill name without providing any actual instructions, code, or domain-specific knowledge. Every section explains things Claude already knows or could infer from the title. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of diagram syntax (e.g., Mermaid), no specific steps for creating API flow diagrams. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequencing, and no validation checkpoints. The 'Capabilities' section vaguely mentions 'step-by-step guidance' and 'validates outputs' but provides neither. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic placeholder with no meaningful structure. There are no references to detailed files, no examples, and no navigation to deeper content. The sections that exist contain no substantive information. | 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
b8a3b3e
- 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.