architecture-diagram

Dark-themed SVG architecture/cloud/infra diagrams as HTML.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/creative/architecture-diagram/SKILL.md

Quality

Content

75%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.

A well-structured, highly actionable skill body that front-loads a concrete design system and points to a template for the full structure. Its main weakness is that the referenced template file is not shipped in the bundle, so the progressive-disclosure pointer partially dangles.

Suggestions

Ship the referenced templates/template.html in a bundle directory so the skill_view pointer resolves to a real file.

Add one complete end-to-end generated HTML example to make the actionability fully copy-paste ready.

Tighten the Workflow section or fold the preview/open commands into it to remove the slightly obvious step descriptions.

Dimension	Reasoning	Score
Conciseness	The body is dense and useful — exact rgba/hex palette, typography sizes, SVG grid snippet, masking technique — with little padding and no over-explanation of SVG/HTML basics; only the Workflow section is slightly obvious.	4 / 5
Actionability	Concrete, copy-ready detail throughout (color table, stroke widths, spacing values, arrow rules, info-card HTML), giving clear building blocks; a full end-to-end worked example would close the minor gap.	4 / 5
Workflow Clarity	The four-step sequence (describe → generate → save with write_file → open) is clear and well-suited to a simple generation skill; no validation checkpoint is needed since the task is non-destructive.	4 / 5
Progressive Disclosure	Well-organized sections keep essential quick-reference detail inline and point to a single one-level template reference; however the referenced templates/template.html is not present in any bundle directory, a minor broken-reference gap.	4 / 5
	Total	16 / 20 Passed

Description

56%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.

A concise, distinctive description that names the domain and output format well, but it omits any 'Use when...' trigger guidance and lacks explicit action verbs. Adding a trigger clause and a concrete verb would lift it from adequate to strong.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for architecture, cloud, or infrastructure diagrams.'

Lead with a concrete action verb such as 'Generate' or 'Create' rather than only naming the artifact.

Include a couple of natural synonyms ('infrastructure', 'topology', 'system diagram') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('architecture/cloud/infra diagrams') and the output format ('as HTML') but contains no action verbs — it describes an artifact rather than concrete actions like 'generate' or 'create'.	2 / 5
Completeness	It gives a clear 'what' (dark-themed SVG diagrams as HTML) but no 'when'/'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'architecture', 'cloud', 'infra', 'diagrams' are natural terms users would say, with good coverage; a few synonyms (e.g. 'infrastructure', 'topology') are missing.	4 / 5
Distinctiveness Conflict Risk	The dark-themed tech/infra-diagram niche is mostly distinct with only minor overlap risk against closely related skills like concept-diagrams or excalidraw.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/creative/architecture-diagram/SKILL.md
Commit: fcbd107

Reviewed: 2 days 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.