Deterministic BeatLab pipeline utilities (validate, render grid, export MIDI/WAV). Use for running scripts instead of reasoning about validation/rendering.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add majiayu000/claude-skill-registry --skill beatlab-pipeline --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Beatlab Pipeline?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-beatlab-pipeline-claude-skill-registry)More formats (shields.io, HTML) on the badges page.
---
name: beatlab-pipeline
description: Deterministic BeatLab pipeline utilities (validate, render grid, export MIDI/WAV). Use for running scripts instead of reasoning about validation/rendering.
user-invocable: false
allowed-tools: Read, Write, Bash(uv:*), Bash(mkdir:*), Bash(which:*), Bash(ffmpeg:*)
---
# BeatLab Pipeline
Prefer running these scripts (do NOT read them into context):
## Validate (and normalize) a beat JSON
uv run python .claude/skills/beatlab-pipeline/scripts/validate.py <beat.json> --inplace
## Render 16-step ASCII grid
uv run python .claude/skills/beatlab-pipeline/scripts/render_grid.py <beat.json>
## Export MIDI
uv run python .claude/skills/beatlab-pipeline/scripts/export_midi.py <beat.json> <out.mid>
## Render WAV
uv run python .claude/skills/beatlab-pipeline/scripts/render_wav.py <beat.json> <out.wav>
## Optional MP3 (if ffmpeg exists)
ffmpeg -y -i <out.wav> <out.mp3>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
