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

83%

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

The canonical home for this skill is algo-rhythmic-narrative in 0gsd/XMVP

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 a well-written, concrete, phase-by-phase specification with genuine validation checkpoints, held back by two structural problems: every reference path it cites is broken (the two files it mandates don't exist, and the two files that do exist are never referenced), and it inlines full schema detail that duplicates its own reference file. Tightening the duplicated format examples and adding a failure-handling loop would raise it further.

Suggestions

Fix the broken references: the body mandates references/pipeline-integration.md and references/grid-language.md, but the bundle contains references/frame-schema.md and references/rhythm-engine.md. Either update the citations to the real filenames and describe what each covers, or restructure the reference files to match the names the body promises.

De-duplicate the schemas: move the complete scaffold/frame/manifest JSON structures out of SKILL.md into references/frame-schema.md (which already claims to hold 'The complete JSON schema'), keeping only one compact inline example, and drop the verbose frame format since the anti-patterns already mandate compact format for the default 64x64 grid.

Add an explicit feedback loop after the Quality Checklist, e.g. 'If any check fails, fix the scaffold or scene plans and regenerate the affected frame range before export', so batch generation failures have a defined recovery path.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain knowledge Claude doesn't have, but it could be tightened: both the verbose AND compact frame JSON formats are fully specified inline even though the anti-patterns mandate compact for the default 64x64 grid, a large ASCII pipeline diagram plus metaphorical framing ("Think of them as the musical score to the orchestra's performance") add tokens, and the full scaffold/frame/manifest schemas duplicate material in references/frame-schema.md. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than anchor 4, since the duplication is more than minor.

3 / 5

Actionability

Mostly executable guidance: copy-paste Python for the beat grid ("fps = (bpm / 60.0) * frames_per_beat"), complete JSON output structures, and a concrete generator-script spec (--start-frame, --preview, numpy+stdlib only). It falls short of anchor 5 because "run analyze_audio() and analyze_audio_profile()" gives no import or provenance, and the XMVP handoff's grid_ref extension is hand-waved as something cartoon_producer.py "can be patched to recognize" with no patch detail.

4 / 5

Workflow Clarity

The four phases are clearly sequenced with per-phase inputs/outputs, and a 9-item Quality Checklist ("Compact hex strings are exactly width * height * 6 characters", "Downbeat frames show measurable brightness increase") provides real checkpoints for this batch generation workflow. It misses anchor 5 because there is no error-recovery feedback loop — the checklist says 'verify' but never says what to do when a check fails or how to regenerate affected frames.

4 / 5

Progressive Disclosure

The 'Before Starting' section instructs loading references/pipeline-integration.md and references/grid-language.md ("Do not proceed without reading them"), but neither file exists in the bundle — the actual references are frame-schema.md and rhythm-engine.md, which the body never mentions — so every referenced path is broken and the real reference material is undiscoverable. Combined with complete JSON schemas inlined in the body that frame-schema.md says it contains ('The complete JSON schema for algo-rhythmic-narrative output'), this matches anchor 2 ('content that clearly belongs in separate files is inlined') rather than anchor 3, where references are present and merely under-signaled.

2 / 5

Total

13

/

20

Passed

Description

100%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 model description: third-person voice, concrete and comprehensive action statements, an explicit 'Use whenever…' clause with natural trigger phrases and synonyms, and a highly distinctive niche with essentially no conflict risk. Its only weakness is verbosity — it runs long — but it contains no fluff or over-claims, just dense specification.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "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" — plus convert/bridge/plan action variants, giving comprehensive coverage of the skill's capabilities. It matches the anchor-5 example's breadth (multiple specific concrete actions) and exceeds anchor 4, which allows coverage gaps.

5 / 5

Completeness

Both questions are explicitly answered: what it does ("generates per-frame JSON instruction files… synced to musical beats and sections") and when to use it ("Use whenever the user wants to plan a music video as pixel grids, create a frame-by-frame color map…" followed by concrete trigger phrases). This matches the anchor-5 example exactly; it is not anchor 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and includes synonyms and natural user phrasings: "plan a music video as pixel grids", "convert a storyboard or shooting schedule into cell-painting instructions", plus an explicit quoted trigger list ('beat-synced pixel grids', 'music video frame map', 'cell painting instructions', 'shooting schedule to frames') and tool filenames (frame_canvas.py, cartoon_producer.py). Nothing natural to this niche is obviously missing, so it fits anchor 5 rather than anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is extremely specific — beat-synced pixel-grid instruction files for XMVP's cell-based painting pipeline — with distinct triggers like 'beat-synced pixel grids' and 'cell painting instructions' that no generic skill would claim. Minimal conflict risk, matching anchor 5; it is well above anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

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

.gemini/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.