check-take
Skill668 starsChanged 10 months agoCC0-1.0View on GitHub
Checks a track's Suno takes against the track file by asking Suno's listening agent - which lyric lines are not sung or are changed, tempo, voice, excluded instruments, mix problems. Free and advisory; it never picks a take. Use after generating, or when the user asks "did it sing everything", "check the takes" or "is the tempo right".
In this repository61 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- aboutSkill
- album-art-directorSkill
- album-conceptualizerSkill
- album-dashboardSkill
- album-ideasSkill
- clipboardSkill
- cloud-uploaderSkill
- configureSkill
- document-hunterSkill
- edit-takeSkill
- explicit-checkerSkill
- extend-takeSkill
- generateSkill
- genre-creatorSkill
- health-checkSkill
- helpSkill
- import-artSkill
- import-audioSkill
- import-trackSkill
- listenSkill
- lyric-refinerSkill
- lyric-reviewerSkill
- lyric-writerSkill
- mastering-engineerSkill
- mix-engineerSkill
- new-albumSkill
- next-stepSkill
- plagiarism-checkerSkill
- pre-generation-checkSkill
- promo-directorSkill
- promo-reviewerSkill
- promote-ideaSkill
- promo-writerSkill
- pronunciation-specialistSkill
- release-directorSkill
- release-kitSkill
- renameSkill
- researchers-biographicalSkill
- researchers-financialSkill
- researchers-govSkill
- researchers-historicalSkill
- researchers-journalismSkill
- researcherSkill
- researchers-legalSkill
- researchers-primary-sourceSkill
- researchers-securitySkill
- researchers-techSkill
- researchers-verifierSkill
- resumeSkill
- session-startSkill
- setupSkill
- sheet-music-publisherSkill
- sound-effectsSkill
- suno-engineerSkill
- suno-voiceSkill
- testSkill
- tutorialSkill
- validate-albumSkill
- verify-sourcesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Check a track's takes against its track file and report what differs.
- Very specific: line 38
When /bitwize-music:generate handed off to you and enabled is false, stop without a word: the user turned the automatic check off …
- Very specific: line 42
Look for audio-listen and audio-listen-wait on a connected MCP server and load their definitions.
- Distinctive: line 48
Never have more than five questions unanswered.
- Distinctive: line 77
No recommendation, no "take 2 is better", no ordering by quality.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Your Task
Input: $ARGUMENTS
Check a track's takes against its track file and report what differs. Suno's listening agent does the listening; you ask, collect and report.
You never choose a take and never rank takes. The report says what was heard; the user listens and decides.
Check Take Skill
Asking Suno's agent about a song is free: nothing is made, changed or charged. The limits are five unanswered questions at a time and 200 questions a day.
The agent is good, not infallible. Treat every flag as "listen here", never as proof. Background, and why Suno's lyric alignment is not used for this: ${CLAUDE_PLUGIN_ROOT}/reference/suno/mcp-api-mapping.md § Take Check.
Step 1: Plan
Expected format: <album-name> <track> [take N | all]
Call get_take_check_plan(album_slug, track_slug).
found: false→ report the error and stop.takesis empty → "No Suno takes to check for [track] yet — generate it first. (Takes logged as older share links cannot be checked.)" Stop.- Which takes:
take N→ that one;all→ every entry intakes; neither →default_takes. - When
/bitwize-music:generatehanded off to you andenabledis false, stop without a word: the user turned the automatic check off (generation.take_check: false). A direct request always runs.
Step 2: Find the Tools
Look for audio-listen and audio-listen-wait on a connected MCP server and load their definitions. Not there → say the take check needs Suno's MCP server, give the setup command from the reference doc, and stop. There is no fallback.
Step 3: Ask
For each take, for each entry in questions, in order: audio-listen(id: <clip_id>, question: <the question, word for word>). Keep the id each call returns, with its take and question number.
- Never have more than five questions unanswered. Two takes with one or two questions each fit in one round; beyond that, work in rounds of five.
429 concurrency_limit_exceeded→ read some answers first, then carry on.429 quota_exceeded→ the day's 200 questions are used; say so and stop.
Then read each answer with audio-listen-wait(id). It returns after about 50 seconds whether or not the answer is ready: call it again while status is processing. On error, note the reason and use an empty string as that answer.
Step 4: Evaluate
Once per take: evaluate_take_check(album_slug, track_slug, clip_id, answers) — that take's answers word for word, one per question, in question order. Pass duration_s when you know the take's length.
Step 5: Report
TAKE CHECK — [NN] [Title]
Take 1 (row 3) — 2 things to check
⚠ Lyrics line 2 sung with different words: "Paper boats are lined up on the sill"
heard: 'all lined up' instead of 'are lined up'
⚠ Tempo 112 BPM measured, 96 asked
✓ Vocal female lead — soft, breathy
Take 2 (row 4) — nothing flagged
✓ Lyrics all 24 lines sung as written
✓ Tempo 95 BPM (asked 96)
These are the agent's observations — listen at the flagged spots before deciding.warnchecks first, thenok.infochecks (the key, an unread answer) go last, and only when they add something.- A few lines per take. Quote each check's
detail; do not turn it into a verdict of your own. - No recommendation, no "take 2 is better", no ordering by quality.
After the Report
- The user rejects a take over a flagged problem → the Regeneration Workflow in CLAUDE.md: a lyric or pronunciation problem goes to
/bitwize-music:lyric-writerand/bitwize-music:pronunciation-specialist, a style problem to/bitwize-music:suno-engineer. - A flag looks wrong to the user → the agent can mishear, and its answers vary a little from run to run. Offer to ask again:
/bitwize-music:check-take <album> <track> take N. - Nothing is written to the track file. The Generation Log stays the user's record.
Error Handling
Suno's server is not connected:
The take check asks Suno's listening agent, so it needs Suno's MCP server:
claude mcp add --transport http suno https://api.suno.com/mcp
then run /mcp and sign in.An answer has no readable result (the report's unread check): say which lines were not checked and offer to ask again.
Remember
- Advisory only. Report what was heard; never pick, rank or reject a take.
- Word for word. Questions go to Suno exactly as the plan gives them; answers go to
evaluate_take_checkexactly as Suno gave them. - Five questions at a time, 200 a day — and it is free.
- A flag is a place to listen, not a verdict: the agent can be wrong.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

