Beat

v2.0.0

Track, analyze, and manage music and audio files from the command line. Use when organizing playlists, converting formats, or analyzing metadata.

0· 174·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bytesagain3/beat.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Beat" (bytesagain3/beat) from ClawHub.
Skill page: https://clawhub.ai/bytesagain3/beat
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install beat

ClawHub CLI

Package manager switcher

npx clawhub@latest install beat
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (music/audio CLI) match the code and instructions. The provided script implements commands for run/check/convert/analyze/export/etc., all of which reasonably belong to a local music/metadata management tool.
Instruction Scope
SKILL.md instructs only local CLI usage. The shipped script logs every command and input to ~/ .local/share/beat/*.log and history.log — this is consistent with the stated automatic history feature but means any text you pass (including secrets) will be recorded locally.
Install Mechanism
Instruction-only skill with a single shell script file; no install spec, no downloaded code or external package installs. Low installation risk.
Credentials
No environment variables, credentials, or config paths are requested. The script only uses the user's HOME to create ~/.local/share/beat, which is proportional to its function.
Persistence & Privilege
The skill is not forced-always and does not request elevated privileges, but it does create and persist logs and export files under ~/.local/share/beat. This is expected for a tracker but worth noting if you need to limit on-disk traces.
Assessment
This skill appears to do what it says: an offline CLI for tracking and exporting music/audio-related entries. It stores logs and exports under ~/.local/share/beat — any text you enter (including potentially sensitive notes) will be recorded there. There are no network calls or credential requests in the code, so it will not exfiltrate data by itself. If you plan to input sensitive strings, either avoid doing so or periodically inspect/delete the logs. If you want extra assurance, review the script locally before enabling or run it in a sandboxed account.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bpaggdtsa5rctkbmp9h6bw9835x0z
174downloads
0stars
1versions
Updated 1mo ago
v2.0.0
MIT-0

Beat

Your personal Beat assistant. Track, analyze, and manage all your music & audio needs from the command line.

Why Beat?

  • Works entirely offline — your data never leaves your machine
  • Simple command-line interface, no GUI needed
  • Export to JSON, CSV, or plain text anytime
  • Automatic history and activity logging

Getting Started

# See what you can do
beat help

# Check current status
beat status

# View your statistics
beat stats

Commands

CommandWhat it does
beat runRun
beat checkCheck
beat convertConvert
beat analyzeAnalyze
beat generateGenerate
beat previewPreview
beat batchBatch
beat compareCompare
beat exportExport
beat configConfig
beat statusStatus
beat reportReport
beat statsSummary statistics
beat export<fmt> Export (json
beat search<term> Search entries
beat recentRecent activity
beat statusHealth check
beat helpShow this help
beat versionShow version
beat $name:$c entries
beat Total:$total entries
beat Datasize: $(du -sh "$DATA_DIR" 2>/dev/null
beat Version:v2.0.0
beat Datadir: $DATA_DIR
beat Entries:$(cat "$DATA_DIR"/*.log 2>/dev/null
beat Disk:$(du -sh "$DATA_DIR" 2>/dev/null
beat Last:$(tail -1 "$DATA_DIR/history.log" 2>/dev/null
beat Status:OK
beat [Beat]run: $input
beat Saved.Total run entries: $total
beat [Beat]check: $input
beat Saved.Total check entries: $total
beat [Beat]convert: $input
beat Saved.Total convert entries: $total
beat [Beat]analyze: $input
beat Saved.Total analyze entries: $total
beat [Beat]generate: $input
beat Saved.Total generate entries: $total
beat [Beat]preview: $input
beat Saved.Total preview entries: $total
beat [Beat]batch: $input
beat Saved.Total batch entries: $total
beat [Beat]compare: $input
beat Saved.Total compare entries: $total
beat [Beat]export: $input
beat Saved.Total export entries: $total
beat [Beat]config: $input
beat Saved.Total config entries: $total
beat [Beat]status: $input
beat Saved.Total status entries: $total
beat [Beat]report: $input
beat Saved.Total report entries: $total

Data Storage

All data is stored locally at ~/.local/share/beat/. Each action is logged with timestamps. Use export to back up your data anytime.

Feedback

Found a bug or have a suggestion? Let us know: https://bytesagain.com/feedback/


Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...