elegant-reports

Generate beautifully designed PDF reports with a Nordic/Scandinavian aesthetic. Use when creating polished executive briefings, analysis reports, or presentation-style PDF outputs from markdown and HTML via Nutrient DWS.

Quality

76%

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/elegant-reports/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, actionable body with concrete commands, a sensible workflow with feedback loop, and good reference signaling. Its weaknesses are minor: a vague File Map lacking real file paths, a placeholder working-directory path, and slight fluff in the "When to Use" bullets.

Suggestions

Replace the File Map category descriptions with actual file paths (e.g., generate.js, references/nordic-design-research.md, scripts/smoke-test.js) so navigation to bundle files is concrete.

Inline the validation checks into the Workflow sequence as an explicit final checkpoint rather than isolating them in a separate section.

Tighten "When to Use" bullets by dropping the fluffy "reusable report template system that can be extended carefully" item or making it concrete.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and mostly lean, assuming Claude's competence without explaining basic concepts; minor fluff like "a reusable report template system that can be extended carefully" and a vague File Map could be trimmed.	4 / 5
Actionability	Quick Start provides copy-paste-ready commands ("node ./generate.js --list", the full generate invocation) plus a concrete frontmatter example, but the "cd /path/to/elegant-reports" placeholder and the absence of an HTML-output example leave minor gaps.	4 / 5
Workflow Clarity	The Workflow section gives a clear five-step sequence with an inspect-adjust-rerun feedback loop (steps 4-5), and a separate Validation checklist (run --list, npm test, verify artifact) covers verification; the validation is not inline within the workflow, so it falls just short of the top anchor.	4 / 5
Progressive Disclosure	Content is appropriately split with a clearly signaled one-level-deep reference ("The bundled Nordic design research note is the canonical reference... Read it only when you need deeper design rationale"), but the File Map lists vague categories rather than actual file paths, a minor navigation gap.	4 / 5
	Total	16 / 20 Passed

Description

78%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 strong, third-person description that clearly states both the capability and an explicit "Use when" trigger with concrete natural phrases. Its main weakness is specificity, since it centers on a single generate action rather than enumerating several concrete operations.

Suggestions

Add 1-2 more concrete actions (e.g., customize themes, extend templates) to lift specificity beyond a single core action.

Include common synonyms or file extensions (e.g., "PDFs", ".md") to broaden trigger-term coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	The description names the domain ("PDF reports with a Nordic/Scandinavian aesthetic") and one core action ("Generate") with input formats ("from markdown and HTML via Nutrient DWS"), but it lists only a single primary action rather than several specific concrete actions, so it is not comprehensive.	3 / 5
Completeness	It explicitly answers both "what" ("Generate beautifully designed PDF reports...") and "when" ("Use when creating polished executive briefings, analysis reports, or presentation-style PDF outputs...") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It includes natural phrases users would say — "polished executive briefings," "analysis reports," "presentation-style PDF outputs," "markdown and HTML" — but omits common synonyms like "PDFs" or file extensions, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The Nordic/Scandinavian aesthetic and Nutrient DWS qualifiers carve a clear niche, but the underlying "PDF reports from markdown" task could overlap with general report-generation skills, so it is mostly distinct with minor overlap risk.	4 / 5
	Total	16 / 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: jdrhyne/agent-skills
Path: skills/elegant-reports/SKILL.md
Commit: 439cd3a

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