CtrlK
BlogDocsLog inGet started
Tessl Logo

taste

Creative-direction layer for music videos and short-form edits in the angelcore / cloud-trance / hyperpop family — a named-genre aesthetic vocabulary, mood + color + light system, beat-synced editing grammar, and a pipeline chaining ECC's video skills from b-roll generation to distribution. Use when a video must feel intentional rather than merely functional — music videos, fancams, moodboard-driven reels, or giving AI-generated b-roll a coherent visual direction.

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

75%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 highly actionable body: concrete palettes, beat math, executable FFmpeg/Remotion code, verbatim generation prompts, and a sequenced pipeline with per-step skill loading. The weaknesses are redundancy — the Key Principles section restates the Core Thesis and earlier rules — and the absence of explicit validation checkpoints in the pipeline.

Suggestions

Merge the 'Key Principles' section into 'Core Thesis' (or cut it): at least five of its seven items restate thesis points or rules already stated verbatim elsewhere in the file, costing ~10 lines of pure repetition.

Add an explicit validation checkpoint to the pipeline (e.g., step 7 POLISH: verify every hard cut lands on the beat grid via the beat math before export, and re-check one-accent-per-shot), turning the implicit 'throw away 80%' curation into a verify-fix-retry loop.

Tighten the top-level pointers to the bundle: reference the taxonomy as a labeled link ('See [genre-taxonomy.md](references/genre-taxonomy.md) for the full catalog') and trim the inlined families table to just the pick-a-primary-plus-accent decision rule.

DimensionReasoningScore

Conciseness

The prose assumes Claude's competence — no explaining what FFmpeg, Remotion, or BPM math is — but the 'Key Principles' section (7 items) largely restates the Core Thesis and rules already given ('Decide the genre before the first generation' vs. thesis 1; 'One accent color per shot' vs. the palette rule; 'Every hard cut lands on a beat' vs. thesis 3), and the genre-families table duplicates material in references/genre-taxonomy.md. That is more than the 'minor instances that could be trimmed' of the anchor above.

3 / 5

Actionability

Fully copy-paste ready throughout: exact hex palette values, computed BPM→frame constants (138 BPM at 24/30/60 fps), executable FFmpeg recipes, a complete Remotion TSX skeleton with a working beat() helper, verbatim fal.ai prompt presets, and a section-by-section shot plan — covering the common cases end to end.

5 / 5

Workflow Clarity

The 0–8 pipeline is a clearly numbered sequence with a table mapping each step to the skill to load, and curation checkpoints exist ('Generate 6–10 per preset, keep 2–3', 'throw away 80%'). It falls short of the top anchor because there is no explicit validation/feedback loop — e.g., verifying cuts land on the beat grid or the grade matches the palette before export — only the implicit rejection step.

4 / 5

Progressive Disclosure

The one bundle file (references/genre-taxonomy.md) exists, is exactly one level deep (it points back to SKILL.md rather than nesting further), and is signaled twice in the body ('The full list lives in references/genre-taxonomy.md'). It misses the top anchor because the reference is cited as a bare backtick path rather than a well-labeled pointer, and the inlined genre-families table partially duplicates the referenced taxonomy.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description: it states a distinct niche in third person, names concrete capability systems, and pairs them with an explicit 'Use when' clause full of natural trigger phrases including genre synonyms. The only soft spot is that capabilities are framed as nouns rather than action verbs, leaving specificity slightly short of the top anchor.

DimensionReasoningScore

Specificity

The description enumerates several concrete capabilities — 'named-genre aesthetic vocabulary, mood + color + light system, beat-synced editing grammar, and a pipeline chaining ECC's video skills from b-roll generation to distribution' — but presents them as capability nouns rather than the crisp, comprehensive verb-actions of the top anchor ('giving AI-generated b-roll a coherent visual direction' is the only clearly verbal form).

4 / 5

Completeness

Both halves are explicit: the 'what' is the creative-direction layer with its four named systems, and the 'when' is a dedicated 'Use when a video must feel intentional rather than merely functional — music videos, fancams, moodboard-driven reels…' clause with concrete trigger phrases, matching the anchor-5 exemplar structure.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered with synonyms: 'music videos', 'short-form edits', 'fancams', 'moodboard-driven reels', 'b-roll', 'coherent visual direction', plus the genre names 'angelcore / cloud-trance / hyperpop' a user would literally say. It sits clearly at the top anchor, not the 'a few natural terms missing' level below.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche — the taste/direction layer explicitly positioned above the mechanical skills it chains ('a pipeline chaining ECC's video skills') — with genre- and format-specific triggers (angelcore, cloud-trance, fancam, moodboard) that no neighboring skill would claim, keeping conflict risk minimal.

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.