Skip to content
Back to skills

Music

ASecurity

Shared ChatCut background-music generation skill. Use when the user wants newly generated music, background music, an intro theme, a music bed, or BGM for a ChatCut video through `submit_music`.

  • 279 stars
  • 0 votes
  • 0 copies
  • 24 views
  • Added September 8, 2026
toolsgo

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add infometa/workbuddyskills --skill music --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Music?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Music
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/infometa-music/badge)](https://www.skillsdirectory.com/skills/infometa-music)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: music
description: |
  Shared ChatCut background-music generation skill. Use when the user wants newly generated music, background music, an intro theme, a music bed, or BGM for a ChatCut video through `submit_music`.
user-invocable: true
---

# Music

Use `submit_music` to create a new background music audio asset from a text prompt. In the native SDK this may appear as `submit_music`; in the WorkBuddy connector it appears as `submit_music`.

The tool submits a generation job and returns `jobId`. The generated audio asset is available after `track_progress` reports completion.

## Capability Boundary

Mureka is a music generation model. It creates a new original music asset; it does not edit, clean up, remix, separate, or adjust existing audio.

Mureka also cannot guarantee exact beat, drop, or timestamp alignment. Generate the music asset first, then use timeline tools for placement, trimming, looping, fades, and ducking. If the user requires precise beat-level sync, explain that this must be handled as a timeline/audio edit rather than guaranteed by the generation model.

## Workflow

1. Write a concise prompt describing style, energy, instrumentation, mood, tempo, and edit role.
2. Provide a short descriptive `name` when useful.
3. Call `submit_music`.
4. Use `track_progress` if the next edit needs the completed asset.
5. Place, trim, loop, or duck the audio with timeline tools after the asset exists.

## Prompt Shape

Good prompts combine:

- genre or instrumentation: "minimal electronic", "warm acoustic guitar", "cinematic piano"
- energy: "upbeat", "calm", "tense", "confident"
- role: "under a product walkthrough", "intro sting", "background bed under speech"
- constraints: "not distracting", "no vocals", "short loop feel" when needed

## Rules

- Do not cover speech with loud music; lower volume or duck under narration.
- Do not use generated music as a substitute for user-provided copyrighted tracks.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…