architecture-diagram

Create a professional, dark-themed software/system architecture diagram as a single self-contained HTML file with inline SVG. Use when asked to visualize system components, layers, services, or how parts of a codebase fit together.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tightly written, single-purpose generation spec with concrete colors, dimensions, and layout rules and no padding. It could be nudged higher on actionability by including a minimal HTML/SVG skeleton template alongside the attribute list.

Suggestions

Include a minimal copy-paste-ready HTML boilerplate with the <svg> skeleton, <defs> arrowhead marker, and one example component box so the spec maps directly to runnable output.

Add a brief 'Verify' step reminding the renderer to confirm the file opens directly in a browser and boxes do not overlap, which would make the output contract explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean — exact hex codes, rgba fills, stroke colors, px sizes, and layout rules with no padding or explanation of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.	5 / 5
Actionability	Provides highly concrete, executable specifications (e.g. 'rounded rects (rx="6"), 1.5px stroke', 'Background #020617', 'draw connecting arrows before boxes') that an instruction-only skill needs. It stays at 4 rather than 5 because it gives attributes rather than a copy-paste-ready HTML/SVG skeleton covering common cases.	4 / 5
Workflow Clarity	This is a simple, single-purpose, non-destructive skill and the single action is unambiguous — produce one self-contained HTML document meeting the stated design and layout specs — across clearly organized sections. The simple-skill exception applies, so the absence of explicit multi-step checkpoints does not lower the score.	5 / 5
Progressive Disclosure	The skill is under 50 lines, has no need for external references (none are bundled), and is organized into well-signaled sections (Visual design system, Layout rules, Output). Per the simple-skills guidance, this earns the top score with just well-organized sections.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, third-person, and explicitly covers both what the skill produces and when to use it, with concrete natural-language triggers. Its only weakness is that it describes one primary action with attributes rather than a menu of distinct actions.

Dimension	Reasoning	Score
Specificity	Names a concrete deliverable — 'a single self-contained HTML file with inline SVG' that is 'professional, dark-themed' — with specific attributes, though it is essentially one action rather than multiple distinct actions. It sits above a 3 because the deliverable characteristics are concrete, but not a 5 because it does not enumerate multiple discrete actions.	4 / 5
Completeness	Explicitly answers both 'what' ('Create a professional, dark-themed ... architecture diagram as a single self-contained HTML file with inline SVG') and 'when' ('Use when asked to visualize system components, layers, services, or how parts of a codebase fit together') with concrete trigger phrases. It clearly matches the top anchor rather than the 4 anchor, whose 'when' is only weakly specified.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say — 'visualize system components, layers, services, or how parts of a codebase fit together' — giving good keyword coverage. It falls short of 5 because common synonyms like 'system design' or file-format terms are absent from the description itself.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — self-contained HTML+SVG architecture diagrams — with distinct triggers unlikely to fire for unrelated skills. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor better than the 4 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: AgentEra/Agently
Path: examples/skills_executor/skills/architecture-diagram/SKILL.md
Commit: 5ecfa97

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.