CtrlK
BlogDocsLog inGet started
Tessl Logo

atmosphere-background

Create a dark atmospheric background with drifting vertical light folds, screen-blended glow, and a concentrated luminous corner or lower-edge bloom.

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/atmosphere-background/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 and reasonably lean, with clear visual and tuning guidance, but it suffers from an empty Workflow section, verbatim description repetition, and a lack of executable code or concrete parameter values.

Suggestions

Fill or remove the empty '## Workflow' section — either give a concrete build sequence (e.g., set base → add folds → blend → focal bloom) or delete the heading.

Add an executable snippet or specific numeric ranges (fold count, drift speed/period, blend mode, gradient stops) so the guidance is copy-paste ready rather than purely directional.

Replace the verbatim 'Use When' copy with concise trigger phrasing to remove redundancy with the frontmatter description.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but the 'Use When' section repeats the frontmatter description verbatim and the 'Workflow' heading is left empty. It is not 3 because of this redundancy and the wasted empty section; not 1 because it is otherwise efficient and skimmable.

2 / 3

Actionability

Guidance is conceptually concrete ('multiple tall overlapping bands or folds with slow sine-wave drift', 'screen or additive-style blending', 'vertical gradients that fade at the top and intensify toward the bottom') but provides no executable code, shader snippet, or numeric parameters. For an instruction-only skill this is actionable but incomplete, so it sits at 2 rather than 3.

2 / 3

Workflow Clarity

The '## Workflow' section is empty, leaving no explicit build sequence, though the surrounding sections (Visual target → Implementation guidance → Tuning knobs → Avoid) imply a loose order. It is not 1 because the single task is unambiguous and non-destructive, but the missing workflow content keeps it from 3.

2 / 3

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and is organized into clearly labeled sections (Scope, Visual target, Implementation guidance, Tuning knobs, Avoid). Per the rubric's simple-skill guidance, this well-organized single-file structure merits 3 without external references.

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 concrete and distinctive, clearly conveying the visual effect it produces, but it omits an explicit 'Use when' trigger clause and leans on technical phrasing over natural user keywords.

Suggestions

Append a 'Use when...' clause naming concrete triggers (e.g., 'Use when the design needs a moody atmospheric backdrop or drifting light-curtain background').

Add natural keyword variations users would actually say, such as 'glow effect', 'ambient background', or 'light-curtain backdrop', alongside the technical terms.

DimensionReasoningScore

Specificity

Quotes concrete output elements — 'drifting vertical light folds, screen-blended glow, and a concentrated luminous corner or lower-edge bloom' — naming multiple specific concrete visual actions rather than vague language. It is at 3 (not 2) because the components are explicit and concrete, not merely a domain label.

3 / 3

Completeness

It clearly states what the skill does ('Create a dark atmospheric background...') but lacks any 'Use when...' clause or explicit trigger guidance in the description. Per the rubric, a missing 'Use when...' clause caps completeness at 2; it is not 1 because the 'what' is clearly answered.

2 / 3

Trigger Term Quality

Includes some relevant terms like 'dark atmospheric background' and 'glow', but leans on specialized phrasing ('screen-blended glow', 'lower-edge bloom', 'vertical light folds') rather than the natural variations a user would say ('glow effect', 'ambient backdrop', 'gradient background'). It is not 3 because common user phrasings are missing; not 1 because several usable keywords are present.

2 / 3

Distinctiveness Conflict Risk

The narrow visual niche — 'drifting vertical light folds, screen-blended glow, and a concentrated luminous corner or lower-edge bloom' — is highly specific and unlikely to trigger for unrelated skills. It is not 2 because the description carves a clear, distinct niche rather than a broad overlap.

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.