CtrlK
BlogDocsLog inGet started
Tessl Logo

documentary-brutalist-agency

Create or redesign creative agency, production studio, architecture, culture, and portfolio websites with billboard typography, hard black-and-white chapters, exposed grids, documentary imagery, irregular collages, restrained parallax, brutalist navigation, and accessible FAQ controls.

63

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/documentary-brutalist-agency/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written, opinionated design skill: concrete numeric constraints, a clear page-assembly sequence, explicit accessibility and validation checklists, and zero filler. The only gaps are the absence of any ready-to-use code patterns for the harder implementation details and a validation section without an explicit fix-and-retry loop.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — every line is a design decision ('Pair one compressed display face with one neutral grotesk', 'cap parallax below 5%', 'Use 160–220ms for controls'). No concepts Claude already knows are re-explained and there is no padding. This matches the 'every token earns its place' anchor; not a 4 because there is nothing to trim.

5 / 5

Actionability

The guidance is unusually concrete for an instruction-only skill: numeric timing ranges (160–220ms, 500–760ms), a parallax cap ('below 5%'), named breakpoints ('320px, tablet, desktop, and 200% zoom'), and specific mechanisms ('CSS Grid', 'native details/summary', 'aria-expanded', 'DOM order'). Per the scoring notes, absence of code is not penalized for instruction-only skills, but there are no ready-to-adapt markup/CSS snippets for the trickiest pieces (collage grid, disclosure pattern), which keeps it short of fully executable guidance.

4 / 5

Workflow Clarity

'Establish the Story' gives a clear numbered 1–6 page sequence, followed by logically ordered implementation sections and a dedicated 'Validate' section with an explicit checklist (DOM-order read with CSS/motion disabled, keyboard/touch testing, 320px/200% zoom checks, alt text and failed-media verification). It is not a 5 because there is no feedback loop — validation is listed but no 'fix and re-validate' recovery guidance; it is well above a 3 because checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the skill is self-contained with clean, navigable section headers in a sensible order (Story → Visual System → Compose → Implement → Motion → Validate → Avoid), and the 'Avoid' section smartly encodes anti-patterns. It falls just short of 5 because the body is ~80 lines — above the under-50-line single-file guideline — and a couple of denser sections (collage implementation, menu/FAQ accessibility) could be split into references if the skill grows.

4 / 5

Total

17

/

20

Passed

Description

66%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 highly specific, well-scoped description with strong natural trigger vocabulary and a clear niche. Its main weakness is the complete absence of a 'when to use' clause, which caps completeness and slightly weakens trigger discoverability.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or redesigning creative agency, production studio, architecture, culture, or portfolio websites, or when the user mentions brutalist or documentary-style web design.'

Include a few more natural synonyms users might say, such as 'design firm', 'photography portfolio', or 'landing page', to broaden trigger coverage.

Tighten the long attribute list slightly and spend the saved tokens on the 'Use when' guidance rather than additional design vocabulary.

DimensionReasoningScore

Specificity

The description lists several concrete deliverable elements — 'billboard typography, hard black-and-white chapters, exposed grids, documentary imagery, irregular collages, restrained parallax, brutalist navigation, and accessible FAQ controls' — paired with the concrete actions 'Create or redesign ... websites'. It stops short of a 5 because the only action verbs are create/redesign; the rest are design attributes rather than multiple distinct actions.

4 / 5

Completeness

The 'what' is explicit and concrete (build/redesign agency-style websites with the listed design system), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3. Not a 2 because the 'what' is clear and comprehensive, not vague.

3 / 5

Trigger Term Quality

Natural user phrases are present: 'creative agency, production studio, architecture, culture, and portfolio websites', 'brutalist navigation', 'FAQ', 'redesign'. A user asking for an agency or portfolio site would plausibly say these. It misses a few common synonyms ('design a website', 'studio site', 'landing page') and any 'Use when' phrasing that users might echo.

4 / 5

Distinctiveness Conflict Risk

The 'documentary brutalist agency' niche is distinctive with specific design vocabulary (billboard typography, exposed grids, pale proof surfaces), making confusion with unrelated skills unlikely. It falls short of 5 because 'create or redesign ... websites' is broad and could overlap with general web-design or other visual-design skills.

4 / 5

Total

15

/

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.

Validation — 16 / 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.