CtrlK
BlogDocsLog inGet started
Tessl Logo

design

Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity — grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill, dispatches the designer specialist, and reviews for taste + accessibility. Standalone — ends with a handoff gate into the chain. Trigger with /hyperflow:design, "design the UI", "make a design system", "design this screen", "give this a visual identity", "redesign this".

74

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-sequenced, highly actionable workflow with concrete dispatch commands, validation checkpoints, and clear one-level-deep references. It is slightly held back by redundant restatements of the iron rules across the Overview, Doctrine, and Prerequisites sections.

Suggestions

Collapse the 'Overview' section — it restates the opening paragraph; keep one concise framing at the top instead of two.

Trim 'Doctrine' and 'Prerequisites' to avoid repeating the design-system-first and researched-prior-art rules already stated under 'Iron Rules'.

Consider folding the 'Per-Step Agent Map' and 'Flow' into a single sequenced view to eliminate parallel duplication of the step breakdown.

DimensionReasoningScore

Conciseness

Mostly lean and efficient, but the 'Overview' section near-duplicates prose from the opening, and the 'Doctrine'/'Prerequisites' sections restate design-system-first and researched rules already covered in 'Iron Rules' — minor redundancy that could be trimmed.

4 / 5

Actionability

Provides fully executable guidance: concrete dispatch commands, exact file paths, specific Skill invocation syntax ('skill: plan', 'args: "session=one spec=..."'), and ready-to-render gate blocks.

5 / 5

Workflow Clarity

Six steps are clearly sequenced via the Per-Step Agent Map and Flow, each with named workers and a reviewer checkpoint, an explicit handoff gate, and a conflict rule ('On a11y conflict, the floor wins') for error recovery.

5 / 5

Progressive Disclosure

Well-structured overview pointing one level deep to clearly signaled external files (design-system.md, DOCTRINE.md, artefact-format.md, failure-recovery.md, task-triage.md); no bundle files present, but content is appropriately split and navigable with minor organization overlap between Flow and Agent Map.

4 / 5

Total

18

/

20

Passed

Description

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

The description is specific, complete, and trigger-rich, explicitly covering both what the skill does and when to use it with natural user phrases. It is concise without padding and clearly distinct from neighboring skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Establishes/extends the design system, invokes the matching local taste skill, dispatches the designer specialist, and reviews for taste + accessibility' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (establish/extend system, invoke taste skill, dispatch designer, review) and when ('Use when the user wants the visual/experiential design...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say are comprehensively listed: 'design the UI', 'make a design system', 'design this screen', 'give this a visual identity', 'redesign this', plus the /hyperflow:design invocation.

5 / 5

Distinctiveness Conflict Risk

Clear niche of systematic, anti-slop product design with distinctive triggers and a /hyperflow:design prefix; minimal conflict risk with adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 12 suspicious

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/tons-of-skills-marketplace
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.