resume-modern

Modern minimal resume, single A4 page, ready for print or PDF export.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/resume-modern/SKILL.md

Quality

Content

72%

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

The body is a lean, well-organized single-purpose template spec with concrete Tailwind guidance, scoring well on conciseness and structure. It is held back by the lack of a complete executable example and an explicit verification that the result fits one A4 page.

Suggestions

Provide a minimal complete HTML skeleton (head + the two-column body) so the template is copy-paste executable rather than a spec to reassemble.

Add a verification step for the core constraint, e.g. 'Open print preview and confirm the resume fits a single A4 page; if it overflows, reduce bullet count or spacing before exporting PDF.'

Include a concrete @media print snippet (not just the instruction to add one) so the print/PDF export behavior is unambiguous.

Dimension	Reasoning	Score
Conciseness	Seven tight bullets each carry concrete, non-redundant instruction (e.g. 'w-[210mm] min-h-[297mm] mx-auto', 'text-4xl', '黑白灰 + 1 个 accent'); there is no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Concrete Tailwind utility classes and exact dimensions are provided throughout, but there is no complete, copy-paste-ready HTML scaffold or full example file, so the guidance is actionable yet incomplete rather than fully executable.	2 / 3
Workflow Clarity	This is a simple single-task skill so a multi-step sequence is not strictly required, but the headline constraint 'single A4 page' has no verification step (e.g. check content fits one page / print-preview), leaving the key success criterion unchecked.	2 / 3
Progressive Disclosure	The skill is under 50 lines, has no external bundle files requiring references, and is organized as a focused bulleted spec, which meets the rubric's bar for a 3 on small skills with no need for external references.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 conveys a clear, distinctive product niche and is reasonably concise, but it reads as an artifact descriptor rather than action-oriented guidance and omits any explicit 'Use when' trigger. Adding concrete actions and a trigger clause would lift specificity and completeness.

Suggestions

Rewrite as concrete third-person actions, e.g. 'Generates a modern minimal single-page A4 resume from the user's content, ready for print or PDF export.'

Add an explicit trigger clause: 'Use when the user asks for a resume, CV, or single-page A4 document for print or PDF export.'

Include common keyword variations (CV, curriculum vitae, job application) so the description matches how users actually ask.

Dimension	Reasoning	Score
Specificity	Quotes 'Modern minimal resume, single A4 page, ready for print or PDF export' name the domain and an output action (print/PDF export), but do not enumerate multiple concrete actions like a score-3 example would; it is more a product descriptor than an action list.	2 / 3
Completeness	It clearly states what the skill produces, but there is no 'Use when...' clause or equivalent explicit trigger for when Claude should use it, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms 'resume', 'print', 'PDF export' appear, but common variations a user might say ('CV', 'job application', 'curriculum vitae') are absent, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	'Modern minimal resume, single A4 page' carves out a clear niche (single-page resumes) that is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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: nexu-io/open-design
Path: skills/resume-modern/SKILL.md
Commit: a2ba3ee

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