CtrlK
BlogDocsLog inGet started
Tessl Logo

book-serif-index

Create an archival book-reader design system with serif-led pages, mono index navigation, aged paper surfaces, margin notes, and a premium catalog frame.

45

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/book-serif-index/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-organized and appropriately concise for a short design-direction skill, but it lacks concrete, executable specifications and leaves the Workflow section empty, which weakens actionability and workflow clarity. Adding concrete design tokens/specs and filling in the workflow would lift the weaker dimensions.

Suggestions

Fill the empty "## Workflow" section with a short sequenced process (e.g., establish shell → build book surface → add index navigation → layer editorial details → tune), even if validation isn't required.

Add concrete, executable specifics — sample color values, font stacks, spacing tokens, or CSS snippets — so the direction can be implemented rather than only described.

De-duplicate the repeated serif/mono and paper-texture guidance across Visual target, Implementation guidance, and Recommended patterns to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is directive and avoids explaining concepts Claude already knows, but several ideas (serif body + mono labels, paper texture/shadows, index navigation) recur across Visual target, Implementation guidance, and Recommended patterns, creating moderate redundancy that could be tightened.

3 / 5

Actionability

While code is appropriately absent for an instruction-only design skill, the guidance stays at a qualitative level ("aged paper tones, subtle texture, crease shadows", "motion should stay calm and literary") with no concrete tokens, color values, font stacks, or component specs, leaving the actual execution underspecified.

2 / 5

Workflow Clarity

The "## Workflow" section is present but empty, so no sequenced steps or checkpoints are given; the sectioned guidance implies only a rough order of concerns rather than a defined process.

2 / 5

Progressive Disclosure

The skill is under 50 lines with no external references and is organized into clearly labeled, single-level sections, meeting the rubric's exception that well-organized short skills can score 5 without separate files.

5 / 5

Total

12

/

20

Passed

Description

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

The description is specific about the design direction and reasonably distinct, but it omits an explicit trigger ("Use when") clause and relies on design jargon rather than natural user phrasing, capping completeness and trigger-term quality. Adding a concrete "Use when..." clause with user-natural terms would meaningfully raise the score.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when the interface should feel like a curated archival reader, manuscript viewer, or premium literary catalog."

Replace designer jargon ("serif-led pages", "mono index navigation") with at least some terms users actually say, such as "book reader", "manuscript viewer", "editorial/archive interface".

Broaden the single "Create" verb into a couple of concrete actions (e.g., "Create and style an archival book-reader design system...") to strengthen specificity.

DimensionReasoningScore

Specificity

The description names the domain and several concrete compositional elements ("serif-led pages, mono index navigation, aged paper surfaces, margin notes, and a premium catalog frame"), but relies on a single action verb ("Create") rather than multiple concrete actions, so it sits just below the comprehensive anchor.

4 / 5

Completeness

It gives a clear "what" (create an archival book-reader design system) but contains no explicit "when"/"Use when" clause in the description field; per the rubric, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

The terms used ("serif-led pages", "mono index navigation", "aged paper surfaces") are designer jargon rather than phrases a user would naturally say when requesting this skill, and it lacks common synonyms or natural trigger phrases found in the body (e.g., "manuscript viewer", "editorial").

2 / 5

Distinctiveness Conflict Risk

The "archival book-reader design system" niche with these specific elements is mostly distinct with only minor overlap risk against other design-system skills, fitting just below the clear-niche anchor.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.