CtrlK
BlogDocsLog inGet started
Tessl Logo

square

Graceful, refined aesthetic with delicate typography, minimal palettes, and polished layouts that exude sophistication.

43

Quality

43%

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 ./skills/square/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized, actionable guideline-authoring template with concrete tokens and explicit rules; its only gap is the absence of explicit validation/feedback checkpoints in the authoring workflow. It performs strongly on conciseness, actionability, and structure.

Suggestions

Add an explicit validation checkpoint to the Guideline Authoring Workflow (e.g. 'After step 4, verify every rule anchors to a token, threshold, or example before proceeding') to create a validate-then-proceed loop.

Insert a short 'Definition of done' check tying the QA checklist back to the Quality Gates so reviewers can confirm each rule is testable.

DimensionReasoningScore

Conciseness

The body is lean — compact token tables, lists, and rule bullets with no explanation of concepts Claude already knows and no padding; every line earns its place.

3 / 3

Actionability

It gives concrete, executable guidance: explicit token values (#3B82F6), a typography/spacing scale, required component states, and must/should constraint language — specific and copy-ready for an instruction-only skill.

3 / 3

Workflow Clarity

A numbered 6-step authoring workflow and QA checklist provide a clear sequence, but there are no explicit validation checkpoints or validate-then-proceed feedback loops, matching the 'steps listed but checkpoints implicit' anchor.

2 / 3

Progressive Disclosure

No bundle files exist and the body is under 50 lines, single-purpose, and organized into clearly labeled sections (Mission, Style Foundations, Rules, Workflow, Quality Gates) — meeting the simple-skill allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

0%

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 marketing-style fluff that conveys a vibe rather than a capability: no concrete actions, no natural trigger terms, no usage guidance, and high conflict risk with other design skills. It fails the rubric's anti-fluff and trigger requirements on every dimension.

Suggestions

Rewrite in third person naming concrete actions, e.g. 'Authors Square design-system guidelines: defines tokens, component anatomy, states, and accessibility acceptance criteria.'

Add an explicit trigger clause: 'Use when creating or reviewing Square design-system guidance, component rules, or brand token usage.'

Replace adjective-driven language ('graceful', 'refined', 'exude sophistication') with the concrete deliverables the skill produces.

DimensionReasoningScore

Specificity

The description uses aesthetic adjectives ('delicate typography', 'minimal palettes', 'polished layouts') but names no concrete actions performed, matching the vague/abstract anchor rather than the action-naming anchor at 2.

1 / 3

Completeness

It vaguely conveys a look-and-feel ('what') but provides no 'Use when...' or equivalent trigger for 'when', and the what itself is weak — both halves are missing or very weak.

1 / 3

Trigger Term Quality

Phrases like 'graceful, refined aesthetic' and 'exude sophistication' are buzzword fluff with no natural trigger terms a user would say ('design system', 'brand guidelines', 'UI tokens'); it earns no keyword coverage.

1 / 3

Distinctiveness Conflict Risk

The generic aesthetic language ('refined', 'minimal palettes', 'sophistication') would overlap with many design or brand skills and offers no distinct trigger to disambiguate.

1 / 3

Total

4

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-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.