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

79

Quality

100%

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

100%

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 tight, actionable instruction set with a clear numbered workflow, concrete design specs, an explicit self-check checkpoint, and a precise output contract. It assumes Claude's competence, avoids concept re-explanation, and is appropriately self-contained without unnecessary file references.

DimensionReasoningScore

Conciseness

Lean and directive throughout — e.g. "600×860 paper-tone cards with 6px shadow, slight rotation opposing each other (±0.6deg)" — assumes competence and never explains concepts Claude knows, matching the lean-and-efficient anchor rather than the padded anchor at 2.

3 / 3

Actionability

Gives concrete, copy-paste-ready guidance including exact dimensions, rotation values, data-od-id targets, and a precise output-contract artifact block; it is specific instruction rather than the abstract 'describe rather than instruct' anchor at 1.

3 / 3

Workflow Clarity

A clear five-step sequence (Read DESIGN.md → Pick topic → Layout → Write → Self-check) with an explicit self-check checklist validating hierarchy, italic accent, and mono usage; this is not the listed-steps-without-checkpoints anchor at 2.

3 / 3

Progressive Disclosure

A self-contained, well-sectioned body (Workflow, Output contract, Self-check) with no bundle files and no nested references; per the simple-skill guidance this earns a 3 for well-organized structure, rather than the monolithic/nested anchor at 1.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person description that states concrete capabilities and provides explicit 'Use when' triggers with good natural-language term coverage. It clearly delineates a distinct niche and answers both what and when, with no over-claims or fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — "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)" — matching the multiple-specific-actions anchor rather than the partial domain-only anchor at 2.

3 / 3

Completeness

Explicitly answers both what (two-spread preview with named elements) and when ("Use when the brief asks for an 'e-guide'...") with explicit triggers, satisfying the both-what-and-when anchor; it is not the missing-when anchor at 2.

3 / 3

Trigger Term Quality

Covers natural terms users would say — "e-guide", "digital guide", "lookbook", "lead magnet", "creator guide", "playbook", "PDF guide", "电子指南" — broad real-phrase coverage, not the sparse single-term anchor at 2.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (digital e-guide previews) with distinct lifestyle-creator triggers, unlikely to fire for unrelated skills; far from the generic "helps with code and documents" anchor at 1.

3 / 3

Total

12

/

12

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.

Validation15 / 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.