CtrlK
BlogDocsLog inGet started
Tessl Logo

mono

Monospace-driven, matrix-inspired design with high-contrast elements, compact density, and a hacker-chic aesthetic.

36

Quality

32%

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

Quality

Content

57%

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-organized, reasonably lean design-system authoring playbook with concrete tokens, rules, and a sequenced workflow. Its main gaps are an irrelevant Brand line, the absence of a worked output example, and missing intermediate validation checkpoints in the workflow.

Suggestions

Remove or repurpose the "Brand" marketing line, which adds noise unrelated to authoring design-system guidelines.

Add one short worked example showing a generated guideline section (anatomy, states, tokens) so the output structure is concrete and imitable.

Insert an explicit validation checkpoint inside the authoring workflow (e.g., verify rules against Quality Gates before drafting component guidance) to add a feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean bullets and directives without explaining concepts Claude already knows, but the "Brand" line ("Join the private club where people are building, monetizing, and marketing products with AI.") is off-topic marketing fluff that does not earn its place.

2 / 3

Actionability

Guidance is concrete for an instruction-only skill (named tokens, required states, do/don't rules, a 6-step workflow), but it lacks any worked example of actual generated output, keeping it short of fully copy-paste-ready.

2 / 3

Workflow Clarity

The Guideline Authoring Workflow is a clear 6-step sequence ending in a QA checklist, but it has no intermediate validation checkpoints or error-recovery feedback loops between steps.

2 / 3

Progressive Disclosure

It is a single self-contained file organized into clear, well-labeled sections with no nested references and no content bulky enough to warrant splitting out, which satisfies progressive-disclosure goals for a skill of this size.

3 / 3

Total

9

/

12

Passed

Description

7%

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 a buzzword-heavy aesthetic portrait that fails to convey what the skill does or when to use it, performing poorly on action specificity and trigger/completeness criteria. It is only saved from the lowest possible outcome by a moderately distinctive visual niche.

Suggestions

Rewrite the description in third person around the skill's actual action, e.g. "Authors implementation-ready design-system guidelines for a monospace, matrix-inspired aesthetic.

Add an explicit trigger clause: "Use when creating or applying a matrix/hacker-chic design system, monospace-heavy UIs, or high-contrast compact layouts."

Replace decorative terms like "hacker-chic aesthetic" with concrete capability and keyword language users would naturally say.

DimensionReasoningScore

Specificity

The description lists only aesthetic adjectives ("Monospace-driven, matrix-inspired", "hacker-chic aesthetic") and names no concrete actions or capabilities, matching the vague/abstract anchor rather than the level-2 example that names a domain and some actions.

1 / 3

Completeness

It does not state what the skill does (it describes a look, not a capability) and entirely omits any "Use when…" trigger, so both the 'what' and 'when' are missing or very weak.

1 / 3

Trigger Term Quality

Terms like "monospace" and "matrix" are decorative style descriptors rather than natural task triggers a user would say to invoke this skill, and "hacker-chic aesthetic" is buzzword fluff the guidelines penalize.

1 / 3

Distinctiveness Conflict Risk

The matrix/monospace/hacker aesthetic carves a recognizable niche unlikely to fire for unrelated skills, but it lacks explicit triggers and could still overlap with other design-system skills, matching the level-2 anchor.

2 / 3

Total

5

/

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.