api-flow-diagram-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-flow-diagram-creatorApi 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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with minimal useful information. It relies entirely on the skill name for context, provides no concrete actions or capabilities, and lacks any explicit trigger guidance. The duplicate trigger term suggests auto-generation without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Creates visual diagrams showing API request/response flows, endpoint relationships, and authentication sequences'
Include a 'Use when...' clause with natural trigger terms like 'API diagram', 'visualize endpoints', 'REST flow', 'API architecture diagram', 'sequence diagram for API'
Specify the output format or tool used (e.g., Mermaid, PlantUML, SVG) to distinguish from other diagramming skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Api Flow Diagram Creator') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what creating an API flow diagram actually involves. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities beyond the category label 'Visual Content'. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api flow diagram creator, api flow diagram creator'). Missing natural variations users would say like 'API diagram', 'flow chart', 'sequence diagram', 'endpoint visualization', or 'API architecture'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API flow diagram' is somewhat specific, the lack of detail means it could overlap with general diagramming skills, flowchart tools, or other visual content skills. The 'Visual Content skill category' label is too broad to differentiate. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely placeholder content with no actionable information about creating API flow diagrams. It lacks any concrete examples, Mermaid/diagram syntax, or actual guidance. The content could apply to virtually any skill by swapping the name, indicating it provides zero domain-specific value.
Suggestions
Add concrete Mermaid or PlantUML syntax examples showing how to create API flow diagrams with request/response sequences
Include a complete, executable example diagram showing a typical API flow (e.g., authentication flow, CRUD operations)
Define a clear workflow: 1) Identify endpoints, 2) Map request/response flow, 3) Generate diagram code, 4) Validate rendering
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific diagram creation techniques
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about API flow diagrams. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code examples, no diagram syntax, no specific commands. The skill describes what it does abstractly but never shows how to actually create an API flow diagram. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content merely lists vague capabilities without explaining any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources. No references to examples, templates, or syntax documentation are provided. | 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.