technical-diagram-analyzer
Technical Diagram Analyzer - Auto-activating skill for Visual Content. Triggers on: technical diagram analyzer, technical diagram analyzer Part of the Visual Content skill category.
34
0%
Does it follow best practices?
Impact
100%
1.01xAverage 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/technical-diagram-analyzer/SKILL.mdQuality
Discovery
0%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 with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, provides no guidance on when to activate, and is indistinguishable from other visual or diagram-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes technical diagrams including flowcharts, UML diagrams, architecture diagrams, and schematics to extract components, relationships, and data flows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user shares a technical diagram, flowchart, UML diagram, network topology, or schematic and asks for explanation, analysis, or extraction of information.'
Remove the duplicate trigger term and expand with natural variations users would actually say, such as 'diagram', 'flowchart', 'architecture diagram', 'UML', 'schematic', 'explain this diagram', 'what does this diagram show'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Technical Diagram Analyzer') but provides no concrete actions. There is no mention of what it actually does—no verbs like 'extract', 'interpret', 'annotate', or 'convert'. 'Visual Content' is vague. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'technical diagram analyzer' repeated twice, which is not a phrase users would naturally say. Missing natural terms like 'flowchart', 'architecture diagram', 'UML', 'schematic', 'diagram analysis', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish from any other image analysis or visual content skill. 'Visual Content skill category' is generic and would overlap with many potential skills. | 1 / 3 |
Total | 4 / 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/placeholder with no actual content. It repeatedly references 'technical diagram analyzer' without ever defining what that means, how to do it, or providing any actionable guidance. Every section is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable examples of diagram analysis — e.g., how to parse Mermaid diagrams, extract information from SVGs, or analyze chart structures with specific code snippets.
Define an actual workflow with clear steps: e.g., 1) Identify diagram type, 2) Extract elements, 3) Analyze relationships, 4) Generate summary — with validation at each step.
Remove all boilerplate text ('This skill provides automated assistance...') and replace with lean, actionable instructions that assume Claude's competence.
Add references to specific tools, libraries, or formats (Mermaid, PlantUML, D3.js, SVG parsing) with concrete code examples for each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'technical diagram analyzer' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no commands, no examples, and no executable instructions. Every section is vague and abstract, describing what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured content hierarchy, and no navigation aids. The content is a flat, repetitive placeholder with no meaningful organization or pointers to deeper material. | 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.