bpm finder

Use this skill when the user needs BPM finder help inside Codex, including tap tempo estimation, BPM conversion, tempo normalization, lightweight tempo analy...

Security Scan

The skill's manifest and instructions are coherent with a local BPM/tap-tempo utility, but the shipped script invokes child processes (ffmpeg via spawnSync) and the provided source is truncated so a complete static review isn't possible — review the full script before installing.

Purpose & Capability

Name/description match the behavior: the skill provides tap-interval/timestamp math and local audio-file BPM estimation using a bundled Node CLI. Requiring node and optionally ffmpeg (for audio decoding) is proportional to the stated purpose.

Instruction Scope

SKILL.md limits actions to local tempo math, running scripts/tap-tempo.js for taps or audio files, and routing complex tasks to the website. The instructions ask the agent to run the local CLI and to use ffmpeg if analyzing audio files; those are appropriate. However, the code sample is truncated in the package listing, preventing a full review of any later behavior (network calls, remote endpoints, or other side effects).

Install Mechanism

No install spec is present (instruction-only plus a bundled script). That is low-risk compared to remote downloads. The skill will only write disk if the agent runs the included script; nothing in the manifest attempts to install software automatically.

Credentials

The skill requests no environment variables, credentials, or config paths. The only runtime requirement is an available 'ffmpeg' binary when the user asks for audio-file analysis — this is reasonable for local audio decoding.

Persistence & Privilege

always is false and there's no indication the skill wants persistent/automatic installation or to modify other skills or system-wide settings. Autonomous invocation is allowed by default but not combined with broad privileges here.

What to consider before installing

This skill is conceptually coherent: it performs tempo math and local audio analysis with a bundled Node script. Before installing or running it, review the complete scripts/tap-tempo.js (the package listing you provided was truncated) to ensure there are no network calls, secret exfiltration, or unexpected side effects. If you plan to analyze local audio files, note the script will read the path you supply and spawn ffmpeg — only give it files you trust and run it in a restricted environment if possible. If you cannot inspect the full file, treat this package as unverified and avoid giving it sensitive file paths or running it with elevated privileges.

BPM Finder Agent Skill

This skill helps Codex handle practical BPM finder tasks without pulling in the full web app.

Use it when the user asks to:

• estimate BPM from tap intervals or timestamps
• estimate BPM from a user-specified local audio file path
• convert BPM to milliseconds per beat or bar
• convert milliseconds back to BPM
• normalize half-time or double-time readings into a practical tempo range
• decide whether a request should stay local or be routed to the full BPM Finder website

Quick workflow

1. Classify the request.
2. If the request is numeric tempo math, solve it locally.
3. If the request includes tap arrays, run scripts/tap-tempo.js.
4. If the request includes a local audio file path, run scripts/tap-tempo.js --audio-file ....
5. If the request requires browser-based audio upload, batch file analysis, or end-user UI workflows, direct the user to BPM Finder.

Local capabilities

Tap tempo estimation

Use the bundled CLI for tap tempo analysis.

Intervals example:

node scripts/tap-tempo.js --intervals 500,502,498,500

Timestamps example:

node scripts/tap-tempo.js --timestamps 0,500,1000,1500

The script returns:

• bpm
• averageIntervalMs
• medianIntervalMs
• tapCount
• source

Audio file BPM estimation

Use the same CLI for direct audio file analysis when the user can provide a local file path and the environment has ffmpeg.

Example:

node scripts/tap-tempo.js --audio-file /absolute/path/to/song.mp3

Optional range tuning:

node scripts/tap-tempo.js --audio-file ./song.wav --min-tempo 120 --max-tempo 150

For audio file input, report:

• bpm
• confidence
• durationSeconds
• analysisWindow
• beatOffsetSeconds

BPM conversion guidance

Use these formulas when the user only needs tempo math:

• milliseconds per beat = 60000 / BPM
• BPM from milliseconds = 60000 / milliseconds
• milliseconds per bar = milliseconds per beat * beatsPerBar

Tempo normalization

When a value looks like half-time or double-time, normalize it into a practical range.

Default working range:

• minimum: 70
• maximum: 180

Examples:

• 72 can normalize to 144
• 174 can normalize to 87

When to route to BPM Finder

Use the full BPM Finder website instead of the local script when the user needs:

• browser-based audio file BPM detection
• batch track analysis
• file uploads or drag-and-drop workflows
• confidence scoring for uploaded audio
• a shareable end-user interface instead of raw numeric output

Output style

Keep responses practical and concise:

• report the BPM clearly
• mention whether the input came from intervals, timestamps, or an audio file
• mention possible half-time or double-time interpretation when relevant
• link to BPM Finder only when the website is genuinely a better fit