CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

algo-rhythmic-narrative

Translate a music video 'shooting schedule' into frame-by-frame color-coded pixel grids for XMVP's cell-based painting pipeline. Given a song's BPM, section map, and scene descriptions, this skill generates per-frame JSON instruction files where each frame is a small pixel grid (e.g. 64x64) with per-cell color and annotation data, synced to musical beats and sections. Use whenever the user wants to plan a music video as pixel grids, create a frame-by-frame color map for animation, convert a storyboard or shooting schedule into cell-painting instructions, generate beat-synced frame data for XMVP's frame_canvas.py, or bridge narrative scene descriptions to per-pixel color grids. Also trigger for 'algo-rhythmic', 'rhythmic narrative', 'shooting schedule to frames', 'beat-synced pixel grids', 'music video frame map', 'cell painting instructions', or 'narrative-to-grid'. Works with cartoon_producer.py's music-video and music-agency modes.

Quality

81%

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

60%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 well-structured and largely actionable, with a clear four-phase workflow, concrete JSON contracts, and a strong validation checklist. Its critical flaw is progressive disclosure: it instructs the reader to load two reference files that do not exist while leaving the two actual reference files orphaned and unreferenced, and its inlined data formats contradict the real frame-schema.md. Conceptual framing sections and a decorative ASCII diagram also cost tokens without adding instructions.

Suggestions

Fix the reference mismatch: either rename the 'Before Starting: Read References' entries to the actual bundle files (references/frame-schema.md and references/rhythm-engine.md) or add the promised pipeline-integration.md and grid-language.md — currently the mandatory first step points at files that do not exist and the real 850 lines of reference material are unreachable.

Reconcile the body's data contracts with references/frame-schema.md: the body specifies per-frame JSON files with RGB cells and a hex 'px' compact string, while the schema reference defines a master-envelope format with palette-index grids, delta encoding, and a character-per-palette-index compact notation — pick one contract and detail it in the reference, not inline.

Trim conceptual padding — the 'Core Concept' section (duplicates the description), the 'Three Clocks' metaphor section, and the ~30-line ASCII pipeline diagram — and move the bulk of the JSON schema examples into the reference files, keeping one compact example per format inline.

DimensionReasoningScore

Conciseness

Mostly efficient — the JSON schemas, math, checklist, and anti-patterns are skill-specific and earn their tokens — but roughly 50 of 362 lines are trimmable: the 'Core Concept' section repeats the frontmatter description, the 'Three Clocks' section is conceptual framing ('the musical score to the orchestra's performance'), and the ~30-line ASCII pipeline diagram restates the phase headers. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the 'minor instances' anchor above.

3 / 5

Actionability

Largely executable: a runnable scaffold calculation snippet, complete JSON structures for scaffold/frame/compact/manifest, an XMVP XML example, and a concrete long-sequence strategy (standalone synthesizer with --start-frame/--preview, numpy+stdlib only). Falls short of 5 because the core Phase 3 synthesis loop is prose steps rather than code, and the documented frame format (per-frame RGB files, hex 'px' string) conflicts with the actual references/frame-schema.md contract (master envelope, palette-index grids, delta encoding).

4 / 5

Workflow Clarity

Clear Phase 1→4 sequence with a 9-item pre-output Quality Checklist (frame-count math, beat boundaries, no timeline gaps, hex string length, downbeat brightness, manifest/file count match) and an anti-patterns section, so the batch-operation validation cap does not apply. Not 5 because no error-recovery loop is specified (what to do when a checklist item fails) and the mandatory first step — 'Load these before generating any frame data... Do not proceed without reading them' — points to reference files that do not exist.

4 / 5

Progressive Disclosure

Scored against the actual bundle: the body's reference section mandates 'references/pipeline-integration.md' and 'references/grid-language.md', neither of which exists, while the two real bundle files (references/frame-schema.md, 364 lines; references/rhythm-engine.md, 486 lines) are never mentioned anywhere in the body and are therefore undiscoverable. Additionally, ~200 lines of frame/schema detail that belongs in the reference files are inlined in the body — and contradict frame-schema.md's actual format. Fits 'references are buried' plus 'content that clearly belongs in separate files is inlined'; not 3 because navigation to the real materials is effectively broken, not merely imperfectly signaled.

2 / 5

Total

13

/

20

Passed

Description

96%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 concrete capabilities in third person, explicitly answers both what and when, and packs in comprehensive trigger synonyms for a well-defined niche. Its only weaknesses are length (some redundancy between the 'Use whenever' and 'Also trigger for' clauses) and minor overlap risk with sibling skills in the same XMVP pipeline.

DimensionReasoningScore

Specificity

Multiple concrete actions are explicitly stated — 'Translate a music video shooting schedule into frame-by-frame color-coded pixel grids', 'generates per-frame JSON instruction files where each frame is a small pixel grid (e.g. 64x64) with per-cell color and annotation data, synced to musical beats and sections' — covering the input (BPM, section map, scene descriptions), the transformation, and the output artifact comprehensively. Not below 4 because coverage is comprehensive for the domain, not just 'several actions with minor gaps'.

5 / 5

Completeness

Both 'what' (translate shooting schedule into beat-synced per-frame pixel-grid JSON for XMVP's cell-based painting pipeline) and 'when' ('Use whenever the user wants to...' followed by concrete scenarios and an 'Also trigger for...' phrase list) are explicitly and clearly answered. Not 4 because the 'when' clause is already explicit and specific with concrete trigger phrases, not merely present.

5 / 5

Trigger Term Quality

Extensive natural-language coverage: 'plan a music video as pixel grids', 'create a frame-by-frame color map for animation', 'convert a storyboard or shooting schedule into cell-painting instructions', plus an explicit synonym list ('algo-rhythmic', 'beat-synced pixel grids', 'music video frame map', 'cell painting instructions', 'narrative-to-grid'). Matches the comprehensive-with-synonyms anchor; nothing common appears missing for this niche.

5 / 5

Distinctiveness Conflict Risk

A clear niche (music-video beat-synced frame grids) with distinctive triggers like 'algo-rhythmic' and 'music video frame map', but shared ecosystem terminology — 'cell painting instructions', 'XMVP's frame_canvas.py', 'cartoon_producer.py's music-video and music-agency modes' — creates minor overlap risk with closely related XMVP/cell-painting skills. Fits the 'mostly distinct; minor overlap risk' anchor better than the minimal-conflict anchor above it.

4 / 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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

0gsd/XMVP

Path

skills/algo-rhythm/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.