CtrlK
BlogDocsLog inGet started
Tessl Logo

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 "电子指南".

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 lean, highly actionable skill body: every step is concrete, the output contract is exact, and the embedded self-check provides a validation checkpoint. The only refinement would be pairing the self-check with brief fix guidance for failed checks.

Suggestions

Add one line to step 5 telling Claude what to adjust when a check fails (e.g., 'if the hierarchy reads flat, bump the display title size one token and re-verify').

DimensionReasoningScore

Conciseness

Lean and efficient throughout: no concept explanations, and every line is either an instruction or a concrete spec (600×860 cards, 6px shadow, ±0.6deg rotation), fully assuming Claude's competence.

5 / 5

Actionability

Fully actionable for an instruction-only skill: exact page structure, example copy ('01 Pick the rule', '02 Drop the filler'), dimension specs, data-od-id hooks, and a copy-ready artifact template in the output contract.

5 / 5

Workflow Clarity

A clear 5-step sequence with an explicit self-check checklist (step 5), but there is no error-recovery loop telling Claude what to change if a self-check item fails — the minor validation gap that keeps it below anchor 5.

4 / 5

Progressive Disclosure

A short single-purpose skill with no bundle files and no need for external references; sections (Workflow, Output contract) are well organized and nothing inlined belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

83%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, third-person, and explicit about both capability and trigger conditions, with a broad set of natural trigger terms. The only gaps are the unstated output format and a couple of natural synonyms that live in the triggers list rather than the description text.

Suggestions

Mention the output medium in the description (e.g., 'as a single HTML artifact') so the 'what' is fully concrete.

Fold 'ebook' and '电子书' from the triggers list into the description's 'Use when' clause for fuller natural-term coverage.

DimensionReasoningScore

Specificity

The description enumerates several concrete components ('display title, author, "What's inside" stats, table of contents teaser'; 'lesson body with pull-quote and a step list'), but never states the output medium (a single HTML artifact), leaving a minor coverage gap versus the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both 'what' (a two-spread e-guide preview with enumerated page contents) and 'when' ('Use when the brief asks for an "e-guide", "digital guide", ...') with concrete trigger phrases — a direct match to the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage with synonyms and a non-English term ('e-guide', 'digital guide', 'lookbook', 'lead magnet', 'creator guide', 'playbook', 'PDF guide', '电子指南'), but common variants such as 'ebook' appear only in the triggers frontmatter, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

A clear niche (creator/lifestyle digital-guide design) with distinct triggers, but broad terms like 'playbook' and 'lookbook' carry minor overlap risk with sibling design skills, so it is not the minimal-conflict anchor.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.