CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-spotify-card

Spotify Now Playing-style card with album art, progress bar, and playback controls, suited to video overlays or personal homepages.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/social-spotify-card/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, highly specific design spec that gives Claude everything needed to render the card in one pass — exact colors, dimensions, typography, input-mapping rules, and accessibility handling — with no filler or background explanations. The only meaningful improvement would be consolidating the repeated color tokens and adding a minimal reference HTML skeleton.

DimensionReasoningScore

Conciseness

The body is dense, spec-only content with no explanations of concepts Claude already knows — every line carries design constraints (hex colors, px values, gradient literals). Minor redundancy keeps it below 5: '#1DB954' is repeated three times, '#121212' appears in two sections, and the gradient example partially duplicates the design-details section.

4 / 5

Actionability

Highly concrete guidance: exact colors ('#1DB954', '#121212', '#b3b3b3'), sizes (22-28px titles, 4px progress bar, 60-200px album art), a literal gradient, font fallback chain, and 'prefers-reduced-motion' handling. It stops short of 5 because there is no complete, copy-paste-ready HTML example — guidance is specific but requires assembly.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (render content as one card) and the single action is unambiguous: two named canvas sizes, explicit input-mapping rules ('若用户输入是文本/标题 → 标题当歌名, 副标当艺人, 时长默认 3:42'), and a single-file HTML constraint. The simple-skill exception applies; no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clearly labeled sections (【意图】【画布】【卡片结构】【字体】【设计细节】) with no nested or buried references. Per the simple-skill exception, well-organized sections alone merit 5.

5 / 5

Total

18

/

20

Passed

Description

66%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 clearly and specifically states what the skill produces, with strong natural trigger terms around Spotify and now-playing cards. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3 and leaves the 'when' only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Spotify, a now-playing widget, music overlays, or wants a music-style card for a homepage or video.'

Include a couple of natural synonyms (music card, song widget, now-playing bar) to broaden trigger coverage.

State the two output sizes (1280×720 overlay / 600×200 widget) in the description to sharpen what the skill delivers.

DimensionReasoningScore

Specificity

The description lists several concrete features — 'album art, progress bar, and playback controls' — with minor coverage gaps, matching the anchor for several specific actions. It falls short of 5 because it does not comprehensively enumerate capabilities, and exceeds 3 because it names more than 1-2 concrete elements.

4 / 5

Completeness

The 'what' is clear (a Spotify Now Playing-style card with specific features), but there is no 'Use when...' clause; 'suited to video overlays or personal homepages' only weakly implies when to use it. Per the judging guideline, a missing explicit trigger clause caps completeness at 3 even though the 'what' is strong.

3 / 5

Trigger Term Quality

'Spotify', 'Now Playing', 'card', 'album art', 'progress bar', 'video overlays' are natural terms a user would say, but common synonyms like 'music widget', 'song card', or 'now-playing bar' are missing. Not 3 (keyword coverage is good, not just 'some relevant'), not 5 (a few natural terms missing).

4 / 5

Distinctiveness Conflict Risk

The Spotify-specific niche ('Spotify Now Playing-style card') is highly distinctive with distinct triggers, but generic terms like 'card', 'overlay', and 'personal homepages' create minor overlap risk with other card/overlay template skills. Mostly distinct — anchor 4 rather than 5.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nexu-io/open-design

Path

skills/social-spotify-card/SKILL.md

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.