CtrlK
BlogDocsLog inGet started
Tessl Logo

beautiful-shadows

Apply exact Tailwind arbitrary shadow utilities for polished, layered neutral elevation. Use when compact cards, controls, panels, popovers, hero media, feature callouts, or modal-like containers need refined shadows without default Tailwind shadow scales or colored tinting.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, highly actionable reference that gives exact utility classes and clear selection guidance in a well-organized layout. The only weakness is redundant restating of each variant's use case between the per-shadow headers and the Usage Rules section.

Suggestions

Remove the first three 'Usage Rules' bullets that repeat each variant's 'Use for...' line verbatim; keep only the general rules (surface fill, one strength per state) to avoid redundancy.

Consider folding the 'Use When' section's guidance into the per-shadow descriptions, since they overlap, to further tighten the body.

DimensionReasoningScore

Conciseness

The body is lean overall with no padding explaining concepts Claude knows, but the first three "Usage Rules" bullets duplicate the per-shadow "Use for..." lines nearly verbatim (e.g., the Beautiful sm description), which is unnecessary repetition that could be tightened.

2 / 3

Actionability

It provides the exact, copy-paste-ready arbitrary-value Tailwind class strings for each variant plus a concrete applied HTML example, matching the fully-executable top anchor.

3 / 3

Workflow Clarity

This is a simple single-purpose skill where the action is unambiguous (choose sm/md/lg by use case and paste the class), with clear selection guidance and no destructive or batch steps requiring validation checkpoints.

3 / 3

Progressive Disclosure

The skill is self-contained and under the threshold needing external references, with well-organized sections (Use When, Shadow Utilities, Examples, Usage Rules, Avoid) and no nested references, matching the simple-skill allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, well-targeted description that clearly states the capability and gives explicit, natural trigger conditions. It is slightly limited by describing essentially one action rather than enumerating multiple concrete actions.

DimensionReasoningScore

Specificity

It names a concrete action ("Apply exact Tailwind arbitrary shadow utilities for polished, layered neutral elevation") and a precise domain, but it lists a single action rather than the multiple specific actions the top anchor expects, so it sits at level 2 rather than 3.

2 / 3

Completeness

It explicitly answers both what ("Apply exact Tailwind arbitrary shadow utilities...") and when ("Use when compact cards... need refined shadows..."), with third-person voice and no first/second person, satisfying the top anchor.

3 / 3

Trigger Term Quality

The "Use when compact cards, controls, panels, popovers, hero media, feature callouts, or modal-like containers" clause gives broad coverage of natural UI-component terms a user would actually say, matching the top anchor.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and clearly bounded (exact arbitrary-value utilities, neutral, no default Tailwind scales, no colored tinting), making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

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.