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.

55

Quality

61%

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

65%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-organized, concise design-direction skill whose thematic sections read clearly, but it has an empty '## Workflow' header and stays descriptive rather than offering spec-level actionable detail. Filling the workflow and adding concrete tokens/specs would lift actionability and workflow clarity.

Suggestions

Remove or populate the empty '## Workflow' section; either delete it or add the actual step sequence a user should follow to apply the design system.

Add concrete, executable specifics — example color tokens (e.g. base #0A0A0F, accent #C026D3), border widths, corner radii, and a sample container markup/CSS snippet — to raise actionability.

Optionally add a brief 'verify the result' checkpoint so the design direction includes a validation loop.

DimensionReasoningScore

Conciseness

The body is sectioned and mostly efficient, assuming Claude's competence about basic design concepts, with only minor adjective-heavy padding ('playful futuristic focal objects', 'fashion-forward'). Not a 5 because a few descriptive clauses could be trimmed without losing clarity.

4 / 5

Actionability

It gives concrete visual direction ('bordered shells, rounded search/input bars, floating cards', 'purple-to-blue accent edge, high-radius corners') but stays descriptive rather than providing spec-like or executable guidance. Not a 4 because there are no concrete tokens, color values, spacing rules, or copy-paste-ready patterns that would make it directly executable.

3 / 5

Workflow Clarity

The '## Workflow' header is present but empty, and there is no sequenced multi-step process or validation checkpoints; structure is thematic rather than procedural. Not a 2 because the thematic sections still give a usable order (target → implementation → patterns → tuning), but the empty Workflow section is a clear gap.

3 / 5

Progressive Disclosure

This is a single-purpose skill under 50 lines with no external references needed and clearly organized sections (Use When, Scope, Visual target, Implementation, Patterns, Tuning knobs, Avoid); per the simple-skill exception this earns a 5. No bundle files exist, so no nested-reference risk.

5 / 5

Total

15

/

20

Passed

Description

58%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 gives a vivid, specific picture of the design direction but omits any explicit 'Use when...' trigger guidance, which caps completeness at 3 and limits trigger-term quality. Adding a concrete trigger clause would substantially improve the score.

Suggestions

Add an explicit 'Use when...' clause stating when to apply this skill (e.g. 'Use when building a dark, container-led technical UI with purple accents').

Include natural trigger synonyms a user might actually say, such as 'purple dark mode', 'futuristic tech dashboard', or 'neon-purple UI theme'.

Tighten the property list into concrete actions/outcomes so the 'what' reads as capabilities rather than only adjectives.

DimensionReasoningScore

Specificity

Names the domain and several concrete visual properties/actions ('dark container-led technical design system', 'fuchsia-purple accents', 'layered rounded shells', 'crisp frame lines', 'playful futuristic focal objects'), with only minor coverage gaps. Not a 5 because the actions are stylistic descriptors rather than a comprehensive set of concrete operations.

4 / 5

Completeness

It clearly states the 'what' (create a particular dark purple technical design system) but provides no explicit 'when'/'Use when' clause; per the rubric, a missing 'Use when' clause caps completeness at 3. Not a 2 because the 'what' is clear and concrete, not vague.

3 / 5

Trigger Term Quality

Relevant niche keywords are present ('fuchsia-purple accents', 'container-led', 'design system') but it lacks common variations, synonyms, or natural phrasing a user would say verbatim when requesting this style. Not a 4 because several natural trigger terms (e.g. 'purple dark mode', 'tech UI theme') are missing.

3 / 5

Distinctiveness Conflict Risk

The highly specific visual niche ('funky purple container tech') makes it clearly distinguishable from generic dark-mode or dashboard skills with only minor overlap risk. Not a 5 because it lacks explicit trigger phrases that fully disambiguate it from adjacent design-direction skills.

4 / 5

Total

14

/

20

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.