CtrlK
BlogDocsLog inGet started
Tessl Logo

beam-glow-states

Create React loading, processing, selected, current, focus, and pressed states with the border-beam package's animated edge glow. Use when a card, button, input, tab, option, task panel, or agent surface needs a restrained traveling or breathing beam; includes installation, imports, prop selection, state wiring, reduced motion, accessibility, and performance and layout guardrails.

69

Quality

85%

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

78%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.

The body is a dense, highly actionable reference: executable code with concrete prop values, precise behavioral contracts, accessibility semantics, and an explicit verification checklist, with almost no filler. Its weakness is structure at the file level — the complete API reference is inlined in a ~340-line monolith and the single links-only reference file it points to does not exist.

Suggestions

Create the missing REFERENCES.md (or remove the dangling link) so the 'links-only source list' pointer resolves to a real file.

Move the full prop-by-prop API reference table into a separate reference file (e.g., references/api.md), keeping only the most-used props and the effect-selection table in SKILL.md.

Tighten the Verify section and the overlapping-states example to the checks most likely to catch real defects (fade timing, reduced motion, radius detection) to reduce body length toward a lean overview.

DimensionReasoningScore

Conciseness

Nearly every line is package-specific knowledge Claude could not have (presets, prop contracts, wrapper quirks like "sm, md, line, and pulse-inner clip overflow"), with no padding about generic React or CSS. Not 5 because sections like the elaborate state-resolution example and the long Verify checklist could each be trimmed somewhat without losing guidance.

4 / 5

Actionability

Copy-paste-ready install commands, named imports, mounted-wrapper and state-wiring TSX examples with concrete prop values (e.g., strength={0.65}, duration={4.2}), a working useReducedMotion hook, fallback CSS, and a complete prop table. Fully executable guidance covering the common cases; matches the top anchor.

5 / 5

Workflow Clarity

The sequence is clear and well-ordered: install/import → choose effect → wire each state → resolve conflicts → handle reduced motion → verify, with an explicit Verify checklist of test scenarios. Not 5 because it stops at a checklist — there is no fix-and-revalidate feedback loop for failures found during verification; not 3 because checkpoints (e.g., "recheck the official README when the installed version changes", timing thresholds, the Verify list) are explicit.

4 / 5

Progressive Disclosure

Section headers and navigation are good, but the body is a ~340-line monolith with the full prop-by-prop API reference table inlined — the anchor example of content that could live in a separate file. Critically, the only bundle reference, "Keep [REFERENCES.md](REFERENCES.md) as the links-only source list", is dangling: no REFERENCES.md (or references/ directory) exists in the bundle. Not 4 because a broken sole reference plus an inlined API reference leaves the file splitting undone.

3 / 5

Total

16

/

20

Passed

Description

92%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 is comprehensive, specific, and clearly triggered: it names the package, the exact states, and the surfaces that should prompt use, with an explicit 'Use when' clause. Its only weakness is mild verbosity in the trailing scope-enumeration clause and a few missing colloquial synonyms, which keep trigger-term coverage just short of maximal.

DimensionReasoningScore

Specificity

"Create React loading, processing, selected, current, focus, and pressed states with the border-beam package's animated edge glow" names multiple concrete state types, the exact package, and the effect mechanism, and then enumerates the covered scope (installation, imports, prop selection, state wiring, reduced motion, accessibility, guardrails). This matches the comprehensive multi-action anchor; not 4 because no capability area is obviously missing.

5 / 5

Completeness

Both halves are explicit: the "what" (create specific React states with an animated edge glow) and a clear "Use when a card, button, input, tab, option, task panel, or agent surface needs a restrained traveling or breathing beam" trigger clause listing concrete surfaces. Matches the anchor with concrete trigger phrases exactly.

5 / 5

Trigger Term Quality

Strong natural vocabulary: "loading", "processing", "selected", "focus", "pressed", "card", "button", "input", "tab", "task panel", "agent surface", "traveling or breathing beam" — terms a user would naturally say. Not 5 because common synonyms like "glowing/animated border", "shimmer", or "loading animation" are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche: state-indicating animated edge glow via the named `border-beam` package. Triggers (specific state words plus component surfaces) are unlikely to fire for unrelated skills; no overlap concerns.

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

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.