CtrlK
BlogDocsLog inGet started
Tessl Logo

funky-purple-container-tech

Create a dark container-led technical design system with fuchsia-purple accents, layered rounded shells, crisp frame lines, and playful futuristic focal objects.

56

Quality

62%

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/funky-purple-container-tech/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 well-organized as an aesthetic direction but has two weaknesses: an empty Workflow section and repeated design directives across sections, plus a lack of concrete values that would make the guidance directly executable.

Suggestions

Fill in or remove the empty "## Workflow" section so the intended process (or its single-step nature) is explicit.

Consolidate the recurring container/shell/purple-focal guidance to remove duplication across Scope, Visual target, Implementation guidance, and Recommended patterns.

Add a few concrete specifics (e.g. representative hex values for the purple/fuchsia family, border widths, or corner-radius ranges) to lift actionability toward copy-paste ready.

DimensionReasoningScore

Conciseness

The bullet-style directives are mostly efficient and avoid explaining concepts Claude knows, but the same ideas (rounded shells, purple focal objects, frame lines) recur across Scope, Visual target, Implementation guidance, and Recommended patterns, adding redundancy that could be tightened.

2 / 3

Actionability

Gives concrete compositional direction (e.g. "centered max-width master container with visible outer boundaries, border rails, and corner markers") but stops short of copy-paste-ready specifics like color values, radii, or spacing, leaving it directional rather than fully executable.

2 / 3

Workflow Clarity

Sections imply a sequence but the "## Workflow" header is empty and there is no explicit step order or checkpoints; the missing workflow content is a real gap.

2 / 3

Progressive Disclosure

A single under-50-line SKILL.md with no external references and clear, well-organized sections meets the simple-skill anchor for progressive disclosure.

3 / 3

Total

9

/

12

Passed

Description

67%

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 and distinctive about the visual direction, but it omits any explicit "Use when..." trigger guidance, so it answers what but not when.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating a dark, technical-but-funky UI with purple/fuchsia accents and container-led layouts."

Include common natural trigger terms users would say, such as "dark mode design", "purple theme", or "futuristic UI".

DimensionReasoningScore

Specificity

Lists multiple concrete visual actions/elements — "fuchsia-purple accents, layered rounded shells, crisp frame lines, and playful futuristic focal objects" — matching the multi-action anchor.

3 / 3

Completeness

Clearly states what the skill does, but provides no "when to use it" trigger clause; per the rubric a missing Use-when clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant descriptive keywords ("dark container-led technical design system", "fuchsia-purple") but lacks common trigger variations and explicit "Use when" phrasing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The aesthetic niche (funky purple container tech) is specific and distinctive, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation16 / 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.