verify-sources
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseYour Task
你的任务
Input: $ARGUMENTS (album name)
Guide the user through source verification for all tracks with pending sources in the specified album.
输入:$ARGUMENTS(专辑名称)
引导用户完成指定专辑中所有待审核来源的音轨的来源验证流程。
Source Verification Skill
来源验证Skill
You facilitate the human source verification gate — the critical checkpoint between research and generation. No track should be generated on Suno until a human has verified that all sources are real, accessible, and accurately represented.
你负责执行人工来源验证关卡——这是调研与生成之间的关键检查点。在人工确认所有来源真实、可访问且表述准确之前,不得在Suno上生成任何音轨。
Step 1: Find the Album
步骤1:查找专辑
- Call — fuzzy match by name, slug, or partial
find_album(name) - If not found, MCP returns available albums
- 调用——按名称、slug或部分内容进行模糊匹配
find_album(name) - 若未找到,MCP将返回可用专辑列表
Step 2: Identify Pending Tracks
步骤2:识别待审核音轨
- Call — returns all pending tracks grouped by album
get_pending_verifications() - Filter to the target album
If no pending tracks:
All tracks in [album] have been verified. No action needed.If pending tracks exist, list them:
SOURCE VERIFICATION: [Album Title]
===================================
Tracks needing verification:
1. [track-slug] — [track-title]
2. [track-slug] — [track-title]
...
Total: X tracks pending verification- 调用——返回按专辑分组的所有待审核音轨
get_pending_verifications() - 筛选出目标专辑的待审核音轨
若无待审核音轨:
All tracks in [album] have been verified. No action needed.若存在待审核音轨,列出它们:
SOURCE VERIFICATION: [Album Title]
===================================
Tracks needing verification:
1. [track-slug] — [track-title]
2. [track-slug] — [track-title]
...
Total: X tracks pending verificationStep 3: Walk Through Each Track
步骤3:逐个处理音轨
For each pending track:
- Call — extracts markdown links from the track file
extract_links(album_slug, track_slug) - Call — get the full citation list
extract_links(album_slug, "SOURCES.md") - Read RESEARCH.md (if it exists) for evidence chains, confidence levels, and claim-to-source mappings — this gives the human verifier context for what each source is supposed to support, not just the URL
- Present sources to the user:
TRACK: [track-title]
--------------------
Sources referenced in this track:
1. [Source Name](URL) — [brief description of what it supports]
2. [Source Name](URL) — [brief description]
...
Please verify:
- Each URL is accessible and contains the claimed information
- No sources are fabricated or hallucinated
- Claims in lyrics are supported by cited sources
Type "verified" to confirm, or describe any issues.- Wait for user response:
- If "verified" (or equivalent affirmative) → update the track
- If issues reported → note them, ask user how to proceed
对于每个待审核音轨:
- 调用——从音轨文件中提取Markdown链接
extract_links(album_slug, track_slug) - 调用——获取完整引用列表
extract_links(album_slug, "SOURCES.md") - 阅读RESEARCH.md(若存在)以查看证据链、置信度以及主张与来源的对应关系——这能为人工审核者提供上下文,让他们了解每个来源应支持的内容,而非仅提供URL
- 向用户展示来源:
TRACK: [track-title]
--------------------
Sources referenced in this track:
1. [Source Name](URL) — [brief description of what it supports]
2. [Source Name](URL) — [brief description]
...
Please verify:
- Each URL is accessible and contains the claimed information
- No sources are fabricated or hallucinated
- Claims in lyrics are supported by cited sources
Type "verified" to confirm, or describe any issues.- 等待用户响应:
- 若回复“verified”(或其他等价确认语)→ 更新该音轨
- 若报告问题→记录问题,询问用户处理方式
Step 4: Update Track Files
步骤4:更新音轨文件
When user confirms verification for a track:
-
Call— updates the field and auto-rebuilds state cache
update_track_field(album_slug, track_slug, "sources-verified", "✅ Verified (YYYY-MM-DD)")- Use today's date
-
Confirm the update:
✅ [track-title] — Sources verified (2025-02-06)- Move to next pending track
当用户确认某音轨的验证结果后:
-
调用——更新字段并自动重建状态缓存
update_track_field(album_slug, track_slug, "sources-verified", "✅ Verified (YYYY-MM-DD)")- 使用当前日期
-
确认更新:
✅ [track-title] — Sources verified (2025-02-06)- 处理下一个待审核音轨
Step 5: Update Album Status
步骤5:更新专辑状态
After all tracks are verified:
-
Check if album status should advance:
- If album was → update to
Research CompleteSources Verified - If album was and all tracks now verified → note it
In Progress
- If album was
-
Rebuild state cache: Callto ensure MCP server has fresh data
rebuild_state() -
Summary report:
VERIFICATION COMPLETE
=====================
Album: [title]
Tracks verified: X/Y
Date: YYYY-MM-DD
All sources verified. This album is cleared for lyric writing.
Next step: /bitwize-music:lyric-writer [track] (write lyrics from verified sources)所有音轨审核完成后:
-
检查是否需要更新专辑状态:
- 若专辑当前状态为→更新为
Research CompleteSources Verified - 若专辑当前状态为且所有音轨已审核→记录该状态
In Progress
- 若专辑当前状态为
-
重建状态缓存:调用以确保MCP服务器拥有最新数据
rebuild_state() -
生成总结报告:
VERIFICATION COMPLETE
=====================
Album: [title]
Tracks verified: X/Y
Date: YYYY-MM-DD
All sources verified. This album is cleared for lyric writing.
Next step: /bitwize-music:lyric-writer [track] (write lyrics from verified sources)Handling Issues
问题处理
If the user reports a problem with a source:
- Document the issue in the track file as a comment or note
- Do NOT mark as verified — keep status as Pending
- Suggest resolution:
- Source URL broken → "Can you find an updated URL?"
- Source doesn't support claim → "Should we revise the lyric, or find a supporting source?"
- Source is fabricated → "I'll remove this source. Do we need to revise the track?"
- After resolution, re-present for verification
若用户报告某来源存在问题:
- 记录问题:在音轨文件中以注释或备注形式记录问题
- 请勿标记为已验证——保持状态为待审核
- 建议解决方案:
- 来源URL失效→“能否找到更新后的URL?”
- 来源不支持相关主张→“我们是否需要修改歌词,或寻找支持该主张的来源?”
- 来源为伪造→“我将移除该来源。是否需要修改此音轨?”
- 问题解决后,重新向用户展示该音轨以进行验证
Remember
注意事项
- Never auto-verify — this skill exists specifically for human review
- Present sources clearly — the user needs to actually check each URL
- Date-stamp everything — verification dates matter for audit trail
- One track at a time — don't rush through, each track matters
- Update state cache — after changes, run indexer update so MCP server has fresh data
- 绝不自动验证——本Skill专为人工审核而设计
- 清晰展示来源——用户需要实际检查每个URL
- 所有操作均需添加时间戳——验证日期对于审计追踪至关重要
- 逐个处理音轨——不要急于完成,每个音轨都很重要
- 更新状态缓存——修改后运行索引器更新,确保MCP服务器拥有最新数据