digital-eguide

A two-spread digital e-guide preview — page 1 is a cover (display title, author, "What's inside" stats, table of contents teaser); page 2 is a spread (lesson body with pull-quote and a step list). Lifestyle / creator brand tone. Use when the brief asks for an "e-guide", "digital guide", "lookbook", "lead magnet", "creator guide", "playbook", "PDF guide", or "电子指南".

Quality

92%

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

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

An exemplary instruction-only skill body: concise, densely concrete (exact copy, dimensions, tokens, and output contract), with a well-sequenced workflow and an explicit self-check. The only improvement would be adding recovery guidance to the self-check step so failed checks have a defined remediation path.

Suggestions

Extend the self-check step with a remediation loop (e.g., 'If any check fails, adjust the tokens/layout and re-verify before emitting') to close the workflow_clarity validation gap.

Clarify where the 'active DESIGN.md (injected above)' comes from and what to do if it is absent, so step 1 does not stall when the design system is missing.

Dimension	Reasoning	Score
Conciseness	Lean and directive throughout — no explanation of concepts Claude already knows; every line is an instruction ('Pick a serif display token...', 'Pages are 600×860 paper-tone cards with 6px shadow...'). Nothing reads as padding, and each token earns its place.	5 / 5
Actionability	Highly concrete guidance for an instruction-only skill: exact copy examples ('Eyebrow ("STYLE & FORMAT GUIDE FOR CREATORS")', '"16 PRINCIPLES OF STYLE", "38 DOS & DON'TS"'), precise layout values (600×860 cards, 6px shadow, ±0.6deg rotation), required data attributes, and a literal output-contract template with the artifact tag. Claude knows exactly what to build.	5 / 5
Workflow Clarity	A clear five-step sequence (read DESIGN.md → pick topic/author → layout → write → self-check) with an explicit self-check checklist covering hierarchy, italic accent, and mono usage. It falls short of 5 because the self-check is a one-shot assertion with no feedback loop — nothing tells Claude what to do when a check fails — leaving a minor validation gap.	4 / 5
Progressive Disclosure	The skill is a short, single-purpose document with no bundle files (no references/, scripts/, or assets/ exist), and it is appropriately self-contained: two well-organized sections (Workflow, Output contract) with no content that belongs in a separate file. Under the simple-skill guidance, well-organized sections with no need for external references earn the top score.	5 / 5
	Total	19 / 20 Passed

Description

91%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 description: concrete structural detail about the deliverable, an explicit 'Use when...' clause with a rich set of natural trigger terms including non-English variants, and a clearly bounded niche. The only weaknesses are structural description in place of action verbs and a couple of broad trigger terms with mild overlap risk.

Dimension	Reasoning	Score
Specificity	The description lists several concrete deliverable components — 'display title, author, "What's inside" stats, table of contents teaser' and 'lesson body with pull-quote and a step list' — giving a specific picture of what is produced. It falls short of a 5 because it describes the artifact's structure rather than naming multiple discrete actions (e.g., 'designs/generates'), leaving minor coverage gaps in what the skill actively does.	4 / 5
Completeness	It explicitly answers both questions: what ('A two-spread digital e-guide preview — page 1 is a cover...; page 2 is a spread...') and when ('Use when the brief asks for an "e-guide", "digital guide"...') with concrete trigger phrases. This matches the top anchor directly.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and multilingual variants: 'e-guide', 'digital guide', 'lookbook', 'lead magnet', 'creator guide', 'playbook', 'PDF guide', and '电子指南'. These are phrases a user would naturally say when asking for this deliverable.	5 / 5
Distinctiveness Conflict Risk	The niche (a two-spread e-guide/lookbook preview) is mostly distinct and the triggers are specific to lead-magnet style deliverables. Minor overlap risk comes from broad terms like 'playbook' and 'lookbook', which could also appear in briefs for other design or documentation skills.	4 / 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: nexu-io/open-design
Path: design-templates/digital-eguide/SKILL.md
Commit: 1b47e60

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