Skip to content
Back to skills

Verify Sources

ASecurity

Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.

  • 497 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
ai-agentspythonbash

Works with

  • mcp

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill verify-sources --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify Sources?

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

Security grade badge for Verify Sources
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bitwize-music-studio-verify-sources/badge)](https://www.skillsdirectory.com/skills/bitwize-music-studio-verify-sources)

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: verify-sources
description: Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
argument-hint: <album-name>
model: claude-sonnet-4-5-20250929
allowed-tools:
  - Read
  - Edit
  - Glob
  - Grep
  - Bash
---

## Your Task

**Input**: $ARGUMENTS (album name)

Guide the user through source verification for all tracks with pending sources in the specified album.

---

# Source Verification 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.

---

## Step 1: Find the Album

1. Read `~/.bitwize-music/cache/state.json`
2. Find the album by name (case-insensitive, slug matching)
3. If not found, list available albums and exit

## Step 2: Identify Pending Tracks

From the album's tracks, find all with `sources_verified: "Pending"`.

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
```

## Step 3: Walk Through Each Track

For each pending track:

1. **Read the track file** to find its sources section
2. **Read SOURCES.md** in the album directory for the full citation list
3. **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.
```

4. **Wait for user response**:
   - If "verified" (or equivalent affirmative) → update the track
   - If issues reported → note them, ask user how to proceed

## Step 4: Update Track Files

When user confirms verification for a track:

1. **Edit the track markdown file** — update the `sources_verified` field in frontmatter:
   - Change: `sources_verified: "Pending"` or `sources_verified: "❌ Pending"`
   - To: `sources_verified: "✅ Verified (YYYY-MM-DD)"`
   - Use today's date

2. **Confirm the update**:
```
✅ [track-title] — Sources verified (2025-02-06)
```

3. Move to next pending track

## Step 5: Update Album Status

After all tracks are verified:

1. Check if album status should advance:
   - If album was `Research Complete` → update to `Sources Verified`
   - If album was `In Progress` and all tracks now verified → note it

2. **Rebuild state cache**:
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/tools/state/indexer.py update
```

3. **Summary report**:
```
VERIFICATION COMPLETE
=====================
Album: [title]
Tracks verified: X/Y
Date: YYYY-MM-DD

All sources verified. This album is cleared for generation.
Next step: /bitwize-music:pre-generation-check [album-name]
```

---

## Handling Issues

If the user reports a problem with a source:

1. **Document the issue** in the track file as a comment or note
2. **Do NOT mark as verified** — keep status as Pending
3. **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?"
4. After resolution, re-present for verification

---

## 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

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.