technical-diagram-analyzer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill technical-diagram-analyzerTechnical Diagram Analyzer - Auto-activating skill for Visual Content. Triggers on: technical diagram analyzer, technical diagram analyzer Part of the Visual Content skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The repetition of the skill name as trigger terms and the boilerplate category mention provide no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes technical diagrams to extract components, relationships, and data flows. Interprets flowcharts, architecture diagrams, UML, circuit schematics, and network topologies.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user shares a technical diagram, flowchart, architecture diagram, UML diagram, schematic, or asks to explain/analyze visual technical documentation.'
Add file format triggers if applicable, such as 'diagram image', '.svg', '.png diagrams', or mentions of specific diagram tools like 'Visio', 'Lucidchart', 'draw.io'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Technical Diagram Analyzer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of analyzing, extracting, interpreting, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the skill name and category without explaining capabilities or providing explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'technical diagram analyzer' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'flowchart', 'architecture diagram', 'UML', 'schematic', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'technical diagram' is somewhat specific compared to generic 'documents' or 'images', the lack of detail about what types of diagrams or what analysis is performed could cause overlap with other visual analysis skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no substantive content. It describes what a technical diagram analyzer skill should do without providing any actual instructions, code, examples, or workflows. The entire content is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete examples of technical diagram analysis, such as how to interpret flowcharts, sequence diagrams, or architecture diagrams with specific visual patterns to identify
Include executable code or specific commands for diagram processing tools (e.g., using Mermaid, PlantUML, or image analysis libraries)
Define a clear workflow for analyzing diagrams: what to look for first, how to extract information, how to validate interpretations
Replace generic capability claims with actual techniques and methods for diagram analysis, such as identifying components, relationships, and data flows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually analyze technical diagrams. The content describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for analyzing technical diagrams. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no meaningful structure. There are no references to detailed materials, no examples, and no actual content to organize or disclose progressively. | 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.