Agent skill · Audited from source
critique-typography
skill · owl-listener/designer-skillsMIT licenceAudited 13 Nov 2026 · source 353bfcf4d7fc
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 353bfcf4d7fc and found no filesystem, network or shell access and no hard-coded secrets. What it does: Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use `typography-scale` (ui-design).
Cite
Cite this page
ModelsAtlas. “critique-typography (owl-listener/designer-skills)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/owl-listener/critique-typography
Trust audit
Audit 0.4.1 · source read 13 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 353bfcf4d7fc · 13 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherowl-listener GitHub userOwner of the repository this skill is read from
- Source folderowl-listener/designer-skills/visual-critique/skills/critique-typographyThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict353bfcf4d7fcA new audit runs when the source changes
- Repository statusNot archivedLast push 68 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use `typography-scale` (ui-design).
--- name: critique-typography description: Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use `typography-scale` (ui-design). --- # Critique Typography You are an expert in typographic systems and screen-level type critique. ## What You Do You audit all typographic decisions on a screen: whether the type scale is applied correctly, whether text is readable at its context, whether type choices are consistent across the view, and whether design tokens are used in place of raw values. You flag problems and provide specific fixes. ## Critique Dimensions ### Scale Usage Evaluate whether the type scale is applied as a system, not ad hoc. - Are only defined scale steps used (e.g., display, h1–h4, body-lg, body-sm, caption)? - Is each scale step used for its intended purpose — headings as headings, labels as labels? - Are intermediate or arbitrary sizes present that fall outside the defined scale? - Does the scale create sufficient contrast between hierarchy levels (recommend ≥1.25× ratio per step)? ### Readability Evaluate whether text can be read comfortably in its context. - Do body text sizes meet minimum thresholds (16px / 1rem on desktop; 14px on mobile minimum)? - Is line-height set for the content type: tighter for headings (1.1–1.3), looser for body (1.4–1.6)? - Is line length (measure) within 45–75 characters for body copy? - Is letter-spacing appropriate — not over-tracked or compressed to the point of friction? - Is contrast ratio between text and background WCAG AA compliant (4.5:1 body, 3:1 large text)? ### Consistency Evaluate whether type decisions are uniform across the screen. - Do semantically equivalent elements (e.g., all card titles, all form labels) use the same type style? - Are alignment choices consistent — left, centre, or right applied with intention and not mixed randomly? - Are font weights used consistently and not randomly varied (e.g., some labels bold, others regular)? - Are there orphaned styles — one-off type treatments not used elsewhere? ### Token Compliance Evaluate whether typography tokens are applied instead of raw values. - Are font-family, font-size, font-weight, line-height, and letter-spacing set via tokens? - Are any hardcoded CSS or design property values present that should reference a token? - List every non-compliant value with its correct token name. ## Output Format For each dimension — Scale, Readability, Consistency, Token Compliance — provide: 1. **Observation** — what you see (neutral, factual) 2. **Problem** — what is broken and why it matters 3. **Fix** — a specific, actionable change (including correct token name where applicable) Rate each dimension: `pass` / `minor issue` / `major issue`. ## Common Failure Patterns - Scale drift — designers nudging sizes by 1–2px instead of moving to the next defined step - Line-height mismatches — display sizes with body line-height and vice versa - Alignment mixing — centred headings above left-aligned body text without intentional justification - Hardcoded font-size values in components because the token was not found or not updated - Over-use of bold — more than two weight levels active on a single screen dilutes contrast
Excerpt, first 3,293 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 353bfcf
git clone https://github.com/owl-listener/designer-skills git -C designer-skills checkout 353bfcf4d7fc
The author documents no install command, so this uses the repository directly. Our verdict covers commit 353bfcf4d7fc only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
353bfcf4d7fc
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/owl-listener/critique-typography/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All design & front-end skills →owl-listener/designer-skills
Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.
owl-listener/designer-skills
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).
owl-listener/designer-skills
Critique a rendered screen's composition — balance, whitespace, rhythm, and gestalt grouping. Use when a layout feels off but hierarchy is fine. For emphasis and eye flow specifically, use `critique-visual-hierarchy`.
owl-listener/designer-skills
Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use…
owl-listener/designer-skills
Critique a rendered screen against mood.md, voice.md, and tokens.md. Use when those brand files exist and you are checking compliance. For defining the visual language itself, use `illustration-style` (ui-design).
owl-listener/designer-skills
Critique a rendered screen's colour — contrast ratios, palette coherence, and semantic meaning. Use when reviewing one screen. For a product-wide WCAG audit use `accessibility-audit` (design-systems); for building the…
Add this badge to your README
[](https://modelsatlas.com/skills/owl-listener/critique-typography/)
<a href="https://modelsatlas.com/skills/owl-listener/critique-typography/"><img src="https://modelsatlas.com/skills/owl-listener/critique-typography/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about critique-typography
What does the critique-typography skill do?
Is critique-typography safe to install?
What can critique-typography access on my machine?
How current is this page?
Sources
- github.com/owl-listener/designer-skills/tree/main/visual-critiqu — the audited source at commit 353bfcf4d7fc and every finding aboveObserved · 13 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the critique-typography skill do?
- Is critique-typography safe to install?
- What can critique-typography access on my machine?