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 substantive information about capabilities or usage triggers. It fails to help Claude distinguish when to select this skill, offering no concrete actions, no natural trigger terms, and no explicit 'when to use' guidance.
Suggestions
Add 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 template with no actual instructional content. It repeats the phrase 'api flow diagram creator' numerous times without ever providing concrete guidance, code examples (e.g., Mermaid syntax for API flows), or any actionable workflow. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of API flow diagrams using Mermaid or similar syntax, showing request/response flows between services.
Define a clear step-by-step workflow: identify endpoints → map request/response flows → generate diagram code → validate rendering.
Remove all boilerplate filler (trigger descriptions, vague capability lists) and replace with actual diagramming patterns and best practices.
Include at least one complete input/output example showing an API specification transformed into a rendered flow diagram.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the skill name excessively, and contains no substantive information about how to actually create API flow diagrams. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no diagram syntax (e.g., Mermaid), no examples of actual API flow diagrams. Every bullet is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequencing, and no validation checkpoints for creating API flow diagrams. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured sections with real content, and no bundle files to support it. | 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.