菜单
Analyse a music-video project's audio track with python3 + librosa to populate Project.audio_analysis — bpm, downbeats, beats, and onsets in milliseconds — so the timeline can snap cell durations to the beat grid.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
PA dispatch — morning briefing, inbox/task triage, and send-queue dispatch for the personal-assistant surface. Reads `ikenga.db` via `host.dbQuery` (SELECT-only); triggers approved sends via `host.dbExec`. DISPATCH-ONLY: task and email CRUD belongs to the tasks and mail pkgs, not here. TRIGGER when the user asks for a morning briefing, inbox/task triage, or wants to dispatch queued sends. Runs as a Chi conversation in the dock. DO NOT TRIGGER for task or email CRUD (create/edit/delete). Route those to the tasks pkg or the mail pkg.
Turn a script (Fountain or plain text) into a populated com.ikenga.studio storyboard in one pass — segment it into shots (cells), tag the source script with each shot's id so the board and the script stay linked, and extract the recurring characters, locations, and props as reusable, seed-lockable anchors. Populates the board only; it generates nothing and spends nothing — the shots and anchor stubs are proposals for a human to review and approve before any fal render.
Read and search emails from local Thunderbird mail storage, and save reply drafts to the IMAP server. Use when agents need to access email data for financial workflows (payment receipts, billing notifications), editorial workflows (newsletter curation), or research workflows (industry intel), or to place a drafted reply into the user's Drafts folder for review. Triggers on email search, payment receipts, subscription notifications, newsletter extraction, or "save this as a draft / draft a reply in Thunderbird".
Finance dispatch — reconciliation sweep with match/pair/dispute decisions, A/R aging chase, and project setup for the finance domain. Reads `ikenga.db` via `host.dbQuery` (SELECT-only); approved decisions dispatch through the host write path. DISPATCH-ONLY: transaction CRUD and payment release belong to the finance app pkg (`com.ikenga.finance`), not here. TRIGGER when the user asks to reconcile transactions, review unmatched ledger rows, chase overdue invoices, or configure the finance skill for this project. DO NOT TRIGGER for transaction CRUD (create/edit/delete), payment release (approve-gate + host own it), or bank pull (external cron). DO NOT run KPI math — cash/burn/runway stays client-side in the pane (R-03 query-collapse). DO NOT send AR follow-ups directly — transport belongs to skill-outbound (R22).
Research dispatch — source-sweep with stale-refresh and dossier-commission proposals, and report-draft surface for the research domain. Reads `ikenga.db` via `host.dbQuery` (SELECT-only, `research_notes` + `research_sources`); approved proposals dispatch through the host write path. DISPATCH-ONLY: research CRUD belongs to the research app pkg (`com.ikenga.research`), not here. TRIGGER when the user asks for a research sweep, source freshness check, dossier commission proposals, or to draft a new research report or persona in chat. DO NOT TRIGGER for research CRUD (create/edit/delete/reassign from skill). Route those to the research app pkg. DO NOT run KPI math — that stays client-side in the pane (R-03). DO NOT run web-scraping or real-time source fetching — source re-scraping is dispatched through the host after operator approval.
Strategy dispatch — OKR review with countersign proposals, at-risk flagging, and objective-draft surface for the strategy domain. Reads `ikenga.db` via `host.dbQuery` (SELECT-only); approved review actions dispatch through the host write path. DISPATCH-ONLY: strategy CRUD belongs to the strategy app pkg (`com.ikenga.strategy`), not here. TRIGGER when the user asks for a strategy review, OKR sweep, cycle summary, at-risk objective flags, or to draft a new objective in chat. DO NOT TRIGGER for strategy CRUD (create/edit/delete/reassign from skill). Route those to the strategy app pkg. DO NOT run KPI math — that stays client-side in the pane (R-03). DO NOT query cross-domain tables directly — KR progress proxies from finance/sales stay client-side.
| name | studio-beat-detect |
| description | Analyse a music-video project's audio track with python3 + librosa to populate Project.audio_analysis — bpm, downbeats, beats, and onsets in milliseconds — so the timeline can snap cell durations to the beat grid. |
Populates Project.audio_analysis for the music-video archetype. The other six archetypes don't need it.
Shells python3 to run the bundled beat_detect.py over the project's audio track and writes:
{
"bpm": 128.0,
"downbeats": [0, 1875, 3750, ...], // bar starts, ms
"beats": [0, 468, 937, ...], // every beat, ms
"onsets": [12, 470, 940, ...], // transient onsets, ms
"source": { "uri": "audio/track.wav" },
"analysed_at": "2026-05-22T12:00:00Z"
}
This matches AudioAnalysisSchema exactly. The composition timeline snaps cell durations to bar/beat boundaries when this block is present (P2 consumes it; P1 just populates it).
librosa.beat.beat_track for bpm + beats, librosa.onset.onset_detect for onsets. Downbeats are derived by grouping beats into bars (4/4 assumed; configurable via --meter). Pip-installable on Python 3.11+.beat_detect.py only uses madmom if --detector madmom is passed and the import succeeds.python3 skills/studio-beat-detect/beat_detect.py --audio <track> --out audio_analysis.json
# or generate a 120-bpm test tone to smoke the script:
python3 skills/studio-beat-detect/beat_detect.py --self-test
If librosa is not importable, the script exits non-zero with a clear message; studio-doctor flags this case ahead of time as a warn-not-fail optional dependency.