typeset
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific typography-related actions and provides explicit trigger guidance with natural user language. The 'Use when...' clause is well-constructed with varied trigger terms. Minor weakness is potential overlap with broader design or styling skills, though the typography focus helps differentiate it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fixing font choices, hierarchy, sizing, weight, and readability. These are distinct, actionable typography concerns rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Improves typography by fixing font choices, hierarchy, sizing, weight, and readability') and when ('Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'fonts', 'type', 'readability', 'text hierarchy', 'sizing looks off', 'polished', 'intentional typography'. Good coverage of how users naturally describe typography issues. | 3 / 3 |
Distinctiveness Conflict Risk | Typography is a fairly specific niche, but could overlap with general design/styling skills or brand styling skills. Terms like 'polished' and 'readability' are somewhat broad and could trigger alongside other visual design skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured typography improvement skill with a clear workflow and good progressive disclosure to external references. Its main weaknesses are moderate verbosity from editorial commentary and parenthetical explanations, and the lack of concrete code examples showing actual CSS implementations. The actionability would benefit significantly from before/after code snippets rather than just listing properties and values in prose.
Suggestions
Add 1-2 concrete before/after CSS code examples showing a type scale implementation or a font pairing setup to make the guidance more executable.
Trim editorial commentary like the closing 'Remember' paragraph and inline explanations of concepts Claude already understands (e.g., why too many font families is bad) to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary editorial commentary (e.g., 'Good typography is invisible; bad typography is distracting', the closing 'Remember' paragraph) and explanatory asides that Claude already knows. The parenthetical explanations after many points add bulk, though some are genuinely useful constraints. | 2 / 3 |
Actionability | Provides specific CSS properties and values (e.g., `max-width: 65ch`, `font-display: swap`, line-height ranges, type scale ratios) which is good, but lacks any executable code examples showing before/after implementations. The guidance is concrete in terms of what to do but stops short of copy-paste ready code snippets. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced: mandatory preparation → assess current state → plan improvements → implement systematically → verify. The verification section serves as an explicit validation checkpoint with specific criteria to check. The assess-plan-implement-verify structure provides a natural feedback loop. | 3 / 3 |
Progressive Disclosure | The skill appropriately references external resources (the frontend-design skill, reference/typography.md) with clear signaling, keeping the main file as an actionable overview. References are one level deep and well-signaled. The content is well-structured with clear sections for progressive reading. | 3 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- pbakaus/impeccable
- Commit
db1add7
- 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.