Skills de Audio

Generate, inpaint, and outpaint music with ACE Step on RunComfy via the `runcomfy` CLI. ACE Step is StepFun-AI's open-weights music foundation model — tag-driven composition (genre, mood, instruments), multilingual lyrics with section markers, 5 s to 4 min stereo output, $0.0002–0.0003 per second (≈ 27× cheaper than ElevenLabs Music). Four endpoints: ACE Step text-to-audio (the default), ACE Step 1.5 text-to-audio (50+ language lyrics, refined structured-lyric handling), ACE Step...

Generate, inpaint, and outpaint music with ACE Step on RunComfy via the `runcomfy` CLI. ACE Step is StepFun-AI's open-weights music foundation model — tag-driven composition (genre, mood, instruments), multilingual lyrics with section markers, 5 s to 4 min stereo output, $0.0002–0.0003 per second (≈ 27× cheaper than ElevenLabs Music). Four endpoints: ACE Step text-to-audio (the default), ACE Step 1.5 text-to-audio (50+ language lyrics, refined structured-lyric handling), ACE Step...

Generate, inpaint, and outpaint music with ACE Step on RunComfy via the `runcomfy` CLI. ACE Step is StepFun-AI's open-weights music foundation model — tag-driven composition (genre, mood, instruments), multilingual lyrics with section markers, 5 s to 4 min stereo output, $0.0002–0.0003 per second (≈ 27× cheaper than ElevenLabs Music). Four endpoints: ACE Step text-to-audio (the default), ACE Step 1.5 text-to-audio (50+ language lyrics, refined structured-lyric handling), ACE Step...

Generate AI music on RunComfy via the `runcomfy` CLI — a smart router across the music-model catalog. Routes to ElevenLabs AI Music Generation (premium 44.1 kHz stereo vocal tracks, 5 s–5 min, $0.0083/s) and ACE Step / ACE Step 1.5 (StepFun-AI open-weights, tag-driven composition, multilingual lyrics, $0.0002–0.0003/s, ~27× cheaper), plus ACE Step audio-inpaint (regenerate a time range inside an existing track) and ACE Step audio-outpaint (extend a track before or after). Picks the right...

Generate AI music on RunComfy via the `runcomfy` CLI — a smart router across the music-model catalog. Routes to ElevenLabs AI Music Generation (premium 44.1 kHz stereo vocal tracks, 5 s–5 min, $0.0083/s) and ACE Step / ACE Step 1.5 (StepFun-AI open-weights, tag-driven composition, multilingual lyrics, $0.0002–0.0003/s, ~27× cheaper), plus ACE Step audio-inpaint (regenerate a time range inside an existing track) and ACE Step audio-outpaint (extend a track before or after). Picks the right...

Generate AI music on RunComfy via the `runcomfy` CLI — a smart router across the music-model catalog. Routes to ElevenLabs AI Music Generation (premium 44.1 kHz stereo vocal tracks, 5 s–5 min, $0.0083/s) and ACE Step / ACE Step 1.5 (StepFun-AI open-weights, tag-driven composition, multilingual lyrics, $0.0002–0.0003/s, ~27× cheaper), plus ACE Step audio-inpaint (regenerate a time range inside an existing track) and ACE Step audio-outpaint (extend a track before or after). Picks the right...

We need to translate the given text from English to Spanish, preserving the name "elevenlabs-music-generation" but it's not in the text. The instruction says: "Do not include the name unless it appears in the source text." The name does not appear in the provided text, so we don't include it. Also preserve product names, protocol names, URLs, numbers, technical terms. So "ElevenLabs Music", "RunComfy", "runcomfy CLI", "44.1 kHz", "stereo audio", "Intro / Verse / Chorus / Bridge", etc. should remain as is or translated? The instruction says "preserve product names" so keep "ElevenLabs Music", "RunComfy", "runcomfy CLI". Numbers: "5 seconds to 5 minutes" - translate the words but keep numbers. "44.1 kHz" keep. "stereo audio" - stereo is same, audio is same. "section-level control" - translate. "multilingual vocals" - translate. "com

We need to translate the given text from English to Spanish, preserving the name "elevenlabs-music-generation" but it's not in the text. The text describes a skill. We must translate only the text inside <text>. No extra labels. Keep product names, protocol names, URLs, numbers, technical terms. "ElevenLabs Music" is a product name, keep as is. "RunComfy" and "runcomfy CLI" - keep as is. "44.1 kHz" - keep numbers and unit. "5 seconds to 5 minutes" - translate numbers? Numbers are universal, but "seconds" and "minutes" should be translated. "Intro / Verse / Chorus / Bridge" - these are musical terms, keep as is or translate? Typically in Spanish music, "Intro", "Verso", "Coro", "Puente" are used. But the instruction says preserve technical terms. I think it's safe to translate them as they are common. However, to be safe, I'll keep the English terms as they are

We need to translate the given text from English to Spanish, preserving the name "elevenlabs-music-generation" but it's not in the text. The instruction says: "Do not include the name unless it appears in the source text." The name is not in the source text, so we don't include it. Also preserve product names, protocol names, URLs, numbers, technical terms. So "ElevenLabs Music", "RunComfy", "runcomfy CLI", "44.1 kHz", "stereo", "Intro / Verse / Chorus / Bridge", etc. should remain as is or translated? "ElevenLabs Music" is a product name, keep as is. "RunComfy" keep. "runcomfy CLI" keep. "44.1 kHz" keep. "stereo" keep. "Intro / Verse / Chorus / Bridge" keep as is (they are musical terms, often kept in English). "multilingual vocals" - "voces multilingües". "commercial-friendly output

Preprocesamiento de activos para composiciones HyperFrames — TTS multiproveedor (HeyGen / ElevenLabs / Kokoro local), BGM multiproveedor (Google Lyria / MusicGen local), transcripción Whisper, eliminación de fondo y creación de subtítulos. Úselo para npx hyperframes tts, bgm, transcribe, remove-background, selección de voz/proveedor, indicación de estado de ánimo musical, subtítulos / letras / karaoke / estilo por palabra.

飞书妙记：搜索妙记列表、查看妙记基础信息、下载妙记音视频文件、上传音视频生成妙记、更新妙记标题、替换说话人。当需要获取、操作或者生成妙记时使用。也支持将本地音视频文件转成纪要和逐字稿（优先使用本 skill，不要用 ffmpeg/whisper 本地转写）。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要

We need to translate the given text from English to Spanish, preserving the name "lipsync" and other technical terms like "RunComfy", "runcomfy CLI", "ByteDance OmniHuman", "Sync Labs sync v2 / Pro", "Kling lipsync", "Creatify lipsync". Also preserve URLs, numbers, etc. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "lipsync" appears in the source text as "Lip-sync" at the beginning, so we should translate that as "Sincronización de labios" or similar? But careful: the instruction says "Preserve product names, protocol names, URLs, numbers, and technical terms." "lipsync" is a technical term? It's a skill name. The instruction says "Name to preserve: lipsync". So we should preserve the word "lipsync" as is when it appears. In the source, it's "Lip-sync" (capitalized,

We need to translate the given text from English to Spanish. The text is a description of an agent skill for music-to-video. We must preserve the name "music-to-video" but it's not in the text, so we don't include it. We translate only the text inside <text>. No extra commentary, no labels. The text is: "Use when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting. The music drives everything: one analyzer reads it once, the orchestrator lays out the frames and fills a per-frame plan, and one sub-agent builds each frame. Typography and templates are the floor — a complete video needs zero assets — but any images or videos the user supplies are cut into the frames on the same beat grid (beat-cut /..." We need to translate accurately, preserving technical terms like "HyperFrames", "beat-synced", "analyzer", "orchestrator", "sub-agent",