Venice Audio Music
nexu-io/open-design
Music generation queueing, retrieval, and completion endpoints via Venice.ai.
Analyse a local audio file into a versioned music map (<stemmap.json, schema music-map/1): tempo from the downbeat grid, 1-based bars, key, band levels, classed sections, drop candidates, optional…
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard music-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/music-production/.pi/skills/music-analysis .claude/skills/music-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "music-analysis" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysis into .claude/skills/music-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "music-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard music-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/music-production/.pi/skills/music-analysis .agents/skills/music-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "music-analysis" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysis into .agents/skills/music-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "music-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard music-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/music-production/.pi/skills/music-analysis .cursor/skills/music-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "music-analysis" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysis into .cursor/skills/music-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "music-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BlackBeltTechnology/pi-agent-dashboard.git --path packages/music-production/.pi/skills/music-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard music-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/music-production/.pi/skills/music-analysis .gemini/skills/music-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "music-analysis" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysis into .gemini/skills/music-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "music-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard music-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/music-production/.pi/skills/music-analysis .github/skills/music-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "music-analysis" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysis into .github/skills/music-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "music-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard music-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/music-production/.pi/skills/music-analysis .opencode/skills/music-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "music-analysis" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/music-production/.pi/skills/music-analysis into .opencode/skills/music-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "music-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
music-analysisAnalyse a local audio file into a versioned music map (<stemmap.json, schema music-map/1): tempo from the downbeat grid, 1-based bars, key, band levels, classed sections, drop candidates, optional…
Music Analysis is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Analyse a local audio file into a versioned music map (<stemmap.json, schema music-map/1): tempo from the downbeat grid, 1-based bars, key, band levels, classed sections, drop candidates, optional stems and style tags. Use on "analyse this track", "what BPM / where is the drop", "map the song for editing", or before cutting music or syncing video to it.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/analyze_mir.py` and `scripts/analyze_music.py`).
The repository describes itself as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote… The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 7a2d171. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uvffmpegpythonjqFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Music Analysis loads about 1.4k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 573 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 573 words, ~1,373 tokens.
.claude/skills/music-analysis/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Turns a local audio file into <stem>_map.json + <stem>_analysis.png. The map
is the input of music-edit-to-length and beat-sync-video.
The scripts never install anything. Resolve the package root first:
PKG=<this skill dir>/../../.. (it holds lib/ and the requirements files).
# quick tier (librosa) — enough for everything except beat_this / stems / tags
uv venv -p python3.14 .venv-music
uv pip install --python .venv-music -r "$PKG/requirements-core.txt"
# deep tier — optional, multi-GB (torch, TensorFlow). Keep it in its OWN venv.
uv venv -p python3.14 .venv-mir
uv pip install --python .venv-mir -r "$PKG/requirements-mir.txt"Verified platform: Python 3.14 on macOS arm64; every requirement is pinned exactly. A missing module makes a script exit 2 with one line naming the requirements file.
Analyse only a local file the user supplies. Never download or extract audio from a streaming service, and never suggest a tool that does. Acceptable sources:
From a video recording, extract the audio and check its level:
ffmpeg -i recording.mkv -vn -ac 2 -ar 44100 -c:a pcm_s16le track_rec.wav
ffmpeg -i track_rec.wav -af volumedetect -f null - 2>&1 | grep -E "max_volume|mean_volume"Quiet recordings: when max_volume is below −12 dBFS, gain the source up so it
peaks at about −2 dBFS before analysis (e.g. a −21.9 dB peak → -af volume=19.9dB),
and note the applied gain next to the file (README row or filename) so the mix stage
knows the source was lifted.
.venv-music/bin/python "$PKG/.pi/skills/music-analysis/scripts/analyze_music.py" track.wav [--out-dir music/].venv-mir/bin/python "$PKG/.pi/skills/music-analysis/scripts/analyze_mir.py" track.wav [--map music/track_map.json] [--no-tags] [--no-stems]Enriches the same map: the beat_this downbeat grid replaces cut_grid
(source: "beat_this") and every bar-indexed field is re-derived against it; essentia
tempo + 3-profile key vote; tags {genre, instrument, mood}; demucs htdemucs_6s
stems under stems/ with energy_share and per-bar RMS, which sharpen section classes
and drop confidence. With stems, drops[] is recomputed on the new grid (drum
re-entry added to the confidence), so drop times move to beat_this downbeats.
Model licences. The tag classifiers (Discogs-EffNet, MTG) are CC BY-NC-SA 4.0 —
non-commercial. They are fetched on first use from a fixed URL table, sha256-verified
(200 MB cap per file) into ${XDG_CACHE_HOME:-~/.cache}/pi-music-production/models/,
and never redistributed. For a commercial deliverable, use the quick tier plus
stems without tags: analyze_mir.py --no-tags.
Third-party weight caches (fetched by those libraries, not hash-pinned by this skill):
demucs and beat_this download their checkpoints into the torch hub cache,
${TORCH_HOME:-~/.cache/torch}/hub/checkpoints/ (beat_this-final0.ckpt, htdemucs).
Delete any of these caches to reclaim space; they refill on the next deep run.
music-map/1 (source time)| Field | Meaning |
|---|---|
schema | "music-map/1"; consumers reject another major version |
source | analysed audio, relative to the map file |
duration, sr | seconds, sample rate |
tempo {bpm, stable_span{start_bar,end_bar}, methods{}} | bpm = 60·meter·(k−1)/(t_k−t_1) over the stable span (longest run of downbeat intervals within ±5 % of their median); per-method estimates only under methods |
cut_grid {source, meter, downbeats[]} | the single authoritative grid; bar n starts at downbeats[n-1] |
beats[], key {label, strength}, band_level_db_rel {sub,bass,low_mid,high_mid,air} | |
sections[] {start,end,start_bar,end_bar,rms_db,bass_db,class} | end_bar is exclusive; class ∈ intro groove breakdown build drop outro (advisory) |
drops[] {time, bar, confidence} | candidates sorted by confidence; a start whose 30–150 Hz gain is not sustained over the next 2 bars scores < 0.5 |
stems {dir, energy_share{}, bar_rms_db{}} | deep tier only; dir relative to the map |
All times are seconds, 3 decimals. Paths are relative, so a project folder can move.
tempo.bpm, not a method's median inter-beat value (frame-quantized, can be
off by 2+ BPM).<stem>_analysis.png: section spans, classes, downbeat lines and drop
candidates should match what you hear.jq '.tempo, .cut_grid.meter, .drops[:3]' <stem>_map.json.© BlackBeltTechnology, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in packages/music-production/.pi/skills/music-analysis of BlackBeltTechnology/pi-agent-dashboard.
Open the folder on GitHubat commit 7a2d171
Music Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Music Analysis this skillBlackBeltTechnology/pi-agent-dashboard | 315 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Venice Audio Musicnexu-io/open-design | 100k | — | ~297 | Automated safety check: Pass | Apache-2.0 | |
| HyperFrames Audioheygen-com/hyperframes | 60k | 1 repos | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Music to Videoheygen-com/hyperframes | 60k | 3 repos | ~4.7k | Automated safety check: Notes | Apache-2.0 | |
| MiniMax Music Generationbytedance/deer-flow | 84k | — | ~717 | Automated safety check: Pass | MIT | |
| AI Music Albumnexu-io/open-design | 100k | — | ~328 | Automated safety check: Pass | Apache-2.0 |
nexu-io/open-design
Music generation queueing, retrieval, and completion endpoints via Venice.ai.
heygen-com/hyperframes
Mixes audio already placed in a HyperFrames composition: fades, gain, ducking under a voiceover, effect chains, automation and shared submix buses.
heygen-com/hyperframes
Turns a music track into a beat-synced HyperFrames video such as a lyric video, slideshow or kinetic promo, with any supplied images or clips cut onto the beat grid.
bytedance/deer-flow
Generates songs, jingles or instrumental tracks as MP3 files from a style prompt and optional lyrics through the MiniMax music API.
nexu-io/open-design
Full-lifecycle AI music album production — concept, lyric drafting, track sequencing, and export.
sickn33/agentic-awesome-skills
Install and use the official AI Music Generator package, pinned by digest, for paid hosted work on the Beatra service.
BlackBeltTechnology/pi-agent-dashboard
Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.
BlackBeltTechnology/pi-agent-dashboard
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and…
BlackBeltTechnology/pi-agent-dashboard
Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.
BlackBeltTechnology/pi-agent-dashboard
Disciplined implementation in pi-agent-dashboard: the rebuild matrix (extension→reload, server→restart, client→build+restart, openspec-apply→full rebuild) plus the project's code discipline rules.
BlackBeltTechnology/pi-agent-dashboard
Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.
BlackBeltTechnology/pi-agent-dashboard
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered…
Analyse a local audio file into a versioned music map (<stemmap.json, schema music-map/1): tempo from the downbeat grid, 1-based bars, key, band levels, classed sections, drop candidates, optional…. Music Analysis is an agent skill from BlackBeltTechnology/pi-agent-dashboard.json, schema music-map/1): tempo from the downbeat grid, 1-based bars, key, band levels, classed sections, drop candidates, optional stems and style tags.
Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a claude-code`. Or copy the skill folder (packages/music-production/.pi/skills/music-analysis in BlackBeltTechnology/pi-agent-dashboard) into .claude/skills/music-analysis in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a codex`. Or copy the skill folder (packages/music-production/.pi/skills/music-analysis in BlackBeltTechnology/pi-agent-dashboard) into .agents/skills/music-analysis in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill music-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/music-analysis, .gemini/skills/music-analysis, .github/skills/music-analysis and .opencode/skills/music-analysis in your project.
Going by SKILL.md and its folder, Music Analysis needs Python for the scripts in its folder and the command-line tools its instructions call (uv, ffmpeg, python and jq). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Music Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Music Analysis: Venice Audio Music (nexu-io/open-design, 100k stars), HyperFrames Audio (heygen-com/hyperframes, 60k stars), Music to Video (heygen-com/hyperframes, 60k stars) and MiniMax Music Generation (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BlackBeltTechnology (a GitHub organization) maintains it in BlackBeltTechnology/pi-agent-dashboard, which has 315 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 10, 2026.
Source: BlackBeltTechnology/pi-agent-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.