CtrlK
BlogDocsLog inGet started
Tessl Logo

cosmic

Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.

49

Quality

53%

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/cosmic/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, mostly lean instruction-only skill with concrete tokens, enumerated states, and a clear sequenced workflow. It misses top marks on conciseness, actionability, and workflow clarity due to minor redundancy, the absence of a worked example, and lack of interleaved validation checkpoints.

Suggestions

Remove redundancy: drop or trim the "Brand" section (it restates the frontmatter description) and merge "Expected Behavior" into "Rules" where they overlap.

Add one concrete worked example of a finished component guideline (e.g. a short Button rule block showing anatomy, states, tokens, and a QA checklist line) to make the output structure copy-paste ready.

Add an interleaved validation checkpoint in the workflow (e.g. after step 3, verify states/tokens against Quality Gates before proceeding) to create an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean with short bullets and no padding about concepts Claude already knows, but the "Brand" section restates the frontmatter description and "Expected Behavior" overlaps the "Rules" sections, so it could be tightened further.

2 / 3

Actionability

It provides concrete, actionable specifics (exact color/spacing/typography tokens, enumerated required states, a 6-step workflow, required output structure), but lacks a concrete worked example of a finished guideline, stopping short of fully copy-paste-ready guidance.

2 / 3

Workflow Clarity

The 6-step authoring workflow is clearly sequenced and includes a QA checklist plus Quality Gates as validation, but checkpoints are mostly end-of-process rather than interleaved and there is no validate→fix→retry feedback loop, so it falls short of the top anchor.

2 / 3

Progressive Disclosure

It is a single cohesive file organized into clearly labeled sections (Mission, Style Foundations, Rules, Workflow, Output Structure, Quality Gates) with no need for external references; per the simple-skills note, well-organized sections suffice for a top score when no bundle files are required.

3 / 3

Total

9

/

12

Passed

Description

50%

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 conveys a clear, specific aesthetic niche but is style-descriptive rather than action-oriented and omits any explicit "Use when..." trigger guidance. All dimensions land at the mid-anchor as a result.

Suggestions

Lead with a concrete verb stating what the skill does, e.g. "Applies a futuristic sci-fi aesthetic..." or "Generates design-system guidelines for a futuristic sci-fi aesthetic...".

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when the user asks for a sci-fi, futuristic, neon, or dark-theme UI aesthetic."

Include common term variations users might say (e.g. "cyberpunk," "space-themed," "dark mode UI") to broaden trigger coverage and reduce overlap with sibling aesthetic skills.

DimensionReasoningScore

Specificity

It names the domain with concrete attributes ("dark themes, vibrant neon accents, and immersive spatial elements") but describes a style rather than listing concrete actions the skill performs, so it lands above the vague anchor yet below the multi-action anchor.

2 / 3

Completeness

It conveys the aesthetic domain (the "what," only implied) but provides no "Use when..." or equivalent trigger guidance for when to use it; per the rubric guidelines a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It contains natural terms a user might say ("sci-fi," "futuristic," "neon," "dark themes"), but it lacks an explicit "Use when..." clause and misses common variations, capping coverage short of the top anchor.

2 / 3

Distinctiveness Conflict Risk

The "futuristic sci-fi" niche is fairly distinct, but without explicit trigger phrasing it could overlap with other design-system or aesthetic skills, so it does not fully reach the distinct-trigger bar.

2 / 3

Total

8

/

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.