markdown-viewer

Create rich diagrams, data visualizations, technical architecture views, and editorial content cards directly in Markdown using the Markdown Viewer Agent Skills pack. Use for Mermaid-like diagram requests, PlantUML architecture diagrams, Vega charts, JSON Canvas maps, infographics, UML, cloud/network/security/data/IoT diagrams, and polished Markdown documentation visuals.

Quality

87%

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

85%Weight 40%Scale 1-3

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

A well-structured router skill: concise, clearly sequenced with a validation checkpoint, and cleanly organized. Its main gap is actionability — it routes to renderers and fence names but provides no complete example artifact, leaning on upstream skills for actual syntax.

Suggestions

Add one small end-to-end example per major renderer family (e.g., a complete `plantuml` block and a minimal `vega-lite` JSON block) so output is copy-paste ready without reading upstream docs.

Rephrase the description in third person ('Creates rich diagrams...') to satisfy the voice rule and recover the specificity point.

Tighten the introductory paragraph, which mildly restates the description's scope already covered in frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive — a selection table, fence mappings, and a numbered workflow — with no padding explaining concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Concrete routing guidance (goal→renderer table, exact fence names, `npx skills add` command) but no complete executable example artifact, and syntax is deferred to the upstream SKILL.md rather than shown copy-paste ready.	2 / 3
Workflow Clarity	A clear six-step sequence with an explicit validation checkpoint (step 5: 'Check syntax before delivery: matching fences, valid JSON/YAML...'); this is non-destructive so a retry feedback loop is not required.	3 / 3
Progressive Disclosure	Well-organized into focused sections with the only external reference (upstream SKILL.md) clearly signaled and one level deep; no bundle files present to misroute.	3 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 strong, trigger-rich description that clearly scopes a Markdown-native visualization skill and enumerates many concrete output types. Its only weakness is the imperative 'Create' voice rather than third person, which costs it a specificity point.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create rich diagrams, data visualizations, technical architecture views, and editorial content cards'), which is anchor-3 caliber, but the imperative 'Create' voice is not third person, triggering the rubric's −1 specificity penalty.	2 / 3
Completeness	Clearly states what ('Create rich diagrams... directly in Markdown') and an explicit when ('Use for Mermaid-like diagram requests...'), satisfying both halves of the completeness anchor.	3 / 3
Trigger Term Quality	Strong coverage of natural user terms — 'Mermaid-like diagram requests, PlantUML architecture diagrams, Vega charts, JSON Canvas maps, infographics, UML, cloud/network/security/data/IoT diagrams' — matching what a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Markdown-native-visual niche via named renderers (Vega, PlantUML, JSON Canvas) is distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: EKKOLearnAI/hermes-studio
Path: packages/skills/markdown-viewer/SKILL.md
Commit: 33c342e

Reviewed: 10 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.