CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quieter

Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.

66

Quality

83%

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

75%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 well-structured, actionable instruction skill: it moves through a coherent assess → plan → refine → verify workflow with unusually concrete numeric heuristics for each refinement dimension and useful guardrails in the NEVER list. Weaknesses are minor: a few motivational asides, some abstract planning bullets, and no explicit verify-and-iterate feedback loop after the quality check.

Suggestions

Trim the rhetorical asides ("Great quiet design is harder than great bold design", "Quiet design is confident design...", "Think luxury, not laziness") — they pad token cost without changing what Claude does.

Add an explicit feedback loop after 'Verify Quality': if any check fails (e.g., the design now feels generic or unusable), state what to revert or re-adjust and re-check, rather than ending at the questions.

Make the 'Plan Refinement' bullets concrete like the Refine section — e.g., name the decision criteria for which elements stay bold, instead of 'Which elements should stay bold (very few)'.

DimensionReasoningScore

Conciseness

The body is dense with actionable heuristics Claude would not articulate on its own ("70-85% saturation", "900 → 600, 700 → 500", "10-20px instead of 40px", "ease-out-quart", "10% rule") and doesn't explain basics Claude knows. A few rhetorical asides could be trimmed ("Great quiet design is harder than great bold design", "Quiet design is confident design. It doesn't need to shout."), which fits anchor 4 (efficient, minor instances that could be trimmed); not 5 due to those motivational flourishes, and not 3 since padding is minor rather than whole unnecessary explanations.

4 / 5

Actionability

Guidance is mostly concrete and directly executable for a design-instruction skill: specific saturation ranges, font-weight mappings, animation distances, easing functions, and explicit prohibitions in the NEVER list. Some directives remain abstract ("signal quality through restraint", "Preserve what matters"), which fits anchor 4 (mostly concrete guidance with minor gaps); not 5 because several planning-stage bullets describe goals rather than give applicable specifics.

4 / 5

Workflow Clarity

The sequence is clear and well-ordered: prepare via /frontend-design and its Context Gathering Protocol, assess intensity sources, plan the refinement strategy, apply per-dimension refinements, then verify quality with explicit questions ("Still functional?", "Still distinctive?", "Better reading?", "Sophistication?"). Matches anchor 4 (clear sequence, most checkpoints present, minor validation gaps); not 5 because there's no feedback loop (verify → revert/adjust) and assessment relies on asking the user rather than explicit checkpoints.

4 / 5

Progressive Disclosure

The body has clean section headers (Assess, Plan, Refine with five sub-dimensions, Verify) with all content one level deep and no buried references; the one external pointer (/frontend-design) is clearly signaled. At ~95 lines it exceeds the under-50-line simple-skill case, and the refinement-dimension detail could arguably live in a reference file, so it fits anchor 4 (good structure, minor organization gaps) rather than 5 (no separate detailed materials to navigate to, and slightly long for a pure overview).

4 / 5

Total

16

/

20

Passed

Description

86%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 strong description: it clearly and explicitly answers both what the skill does and when to use it, with an unusually rich set of natural trigger synonyms. The only weakness is that the capability statement stays at the level of the overall goal rather than naming the concrete refinement dimensions (color, typography, motion) the skill actually works on.

DimensionReasoningScore

Specificity

"Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality" names the domain and one core action (reduce intensity) with a constraint (preserve quality), but doesn't enumerate what the skill concretely adjusts (color, typography, motion, composition). Matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 since no list of several specific actions, and not 2 since it goes beyond merely naming the domain.

3 / 5

Completeness

"Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality" explicitly states what it does, and "Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic" gives an explicit 'when' with concrete trigger phrases. Matches anchor 5 exactly; not 4, because both halves are explicit rather than the 'when' being only adequate.

5 / 5

Trigger Term Quality

"too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic" provides comprehensive natural-language coverage of how users describe this need, including both problem phrases and desired-outcome synonyms. Clearly matches anchor 5 (comprehensive coverage of natural terms including synonyms); file extensions are not applicable to this design domain, and the synonym set is broad enough that anchor 4's 'a few natural terms missing' understates it.

5 / 5

Distinctiveness Conflict Risk

Trigger words like "too bold", "garish", and "overwhelming" are directional and specific to toning down intensity, making conflict with unrelated skills unlikely. Matches anchor 4 (mostly distinct, minor overlap risk with closely related skills such as general design/aesthetic skills that could also claim "calmer, more refined"); not 5 because phrases like "more refined aesthetic" could plausibly activate a general design-styling skill.

4 / 5

Total

17

/

20

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.

Validation — 15 / 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

fengshao1227/ccg-workflow

Path

templates/skills/impeccable/quieter/SKILL.md

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.