AudioPod
v1.2.3Use AudioPod AI's API for audio processing tasks including AI music generation (text-to-music, text-to-rap, instrumentals, samples, vocals), stem separation, text-to-speech, noise reduction, speech-to-text transcription, speaker separation, and media extraction. Use when the user needs to generate music/songs/rap from text, split a song into stems/vocals/instruments, generate speech from text, clean up noisy audio, transcribe audio/video, or extract audio from YouTube/URLs. Requires AUDIOPOD_API_KEY env var or pass api_key directly.
⭐ 3· 3.1k·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name and description align with the SKILL.md: audio generation, stems, TTS, transcription, extraction, and wallet management are all documented. However the registry metadata does not declare the single obvious credential (AUDIOPOD_API_KEY) as a required env var or primary credential, which is an inconsistency.
Instruction Scope
SKILL.md stays within the audio-processing domain and documents concrete endpoints, SDK usage, and cURL examples. It does instruct extracting audio from YouTube/URLs and mentions voice cloning and wallet/billing; these are expected for this functionality but raise ethical/billing considerations. The instructions do not ask the agent to read unrelated system files or other environment variables.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but SKILL.md instructs users to run 'pip install audiopod' and 'npm install audiopod'. Installing packages from PyPI/npm is common but carries risk because package provenance/version is not specified here and the skill provides no checksum or pinned version. This is moderate risk and should be validated (official package, expected maintainer, review package contents).
Credentials
The runtime docs explicitly require an AUDIOPOD_API_KEY (and the service uses a wallet/credits), but the registry metadata lists no required env vars and no primary credential. That mismatch is concerning because users may not realize an API key (and therefore potential billing) is required and must be supplied. No other unrelated credentials are requested.
Persistence & Privilege
always:false and no install spec means the skill does not request permanent/force-included presence. The skill also does not modify other skills or system-wide settings in the provided instructions.
What to consider before installing
Before installing or enabling this skill:
- Expect to provide an AUDIOPOD_API_KEY (SKILL.md requires it) and to fund an AudioPod wallet; that implies possible charges — confirm pricing and quota.
- The registry metadata failing to declare the API key is an inconsistency; ask the publisher or registry maintainer to correct metadata (primary credential should be AUDIOPOD_API_KEY).
- The SKILL.md recommends 'pip install audiopod' / 'npm install audiopod' — verify the package on PyPI/npm, confirm the publisher/maintainer, check versions and read the package source before running to avoid supply-chain risk.
- Voice-cloning and extracting audio from third-party content have legal and ethical implications; avoid uploading others' voices or copyrighted material without permission.
- If you want to limit risk, do not store the API key globally in agent environment variables; pass it per-request if possible and monitor wallet usage/keys for unexpected charges.
- If you need higher assurance, request a versioned install spec, package checksums, or an authored source/homepage for the skill so you can audit the client library.Like a lobster shell, security has layers — review code before you run it.
latestvk97fyze9dd3f6z221hb1mr36dn8094je
License
MIT-0
Free to use, modify, and redistribute. No attribution required.