verify-sources

Name: verify-sources
Availability: InStock
Author: bitwize-music-studio

Audit album tracks and update sources_verified status with verification timestamps.

408|97|Updated Jan 14, 2026

Search Tags:#verify #human-in-the-loop #sources #music-production #audit-trail #tracks

Ready to run

npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill verify-sources

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-sources
Source: https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/verify-sources
Command: npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill verify-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the human-source verification gate, auditing album tracks, timestamping verifications, and updating track files to ensure generation only proceeds after sources are verified.

Core Features & Use Cases

Human-in-the-loop verification gate: prevents generation until all sources are verified.
Track and album state updates: updates frontmatter and maintains an auditable history.
Use Case: When an album has pending sources, run this skill to verify each track's citations and record verification timestamps.

Quick Start

Use the verify-sources skill with an album name to begin the per-track source verification workflow.

Frequently Asked Questions about verify-sources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify sources for album tracks before generation?▼

To verify sources for album tracks, you run a per-track verification workflow that audits citations and updates the sources_verified status. This process reads local state and parses track frontmatter to ensure generation only proceeds after verification.

What is a human-in-the-loop verification gate for music production?▼

A human-in-the-loop verification gate for music production requires manual confirmation of track sources before automated generation proceeds. It ensures every track's sources are audited and timestamped in an audit trail.

How do I maintain an auditable history of track sources verified?▼

You maintain an auditable history by running a verification workflow that parses track frontmatter and writes updated verification timestamps directly into the track metadata files.

Can I use this workflow to audit albums with pending sources only?▼

Yes, the source verification workflow specifically applies to albums with pending sources. It guides a per-track verification process to audit citations and update the sources_verified status before generation.

Does the verification process update track frontmatter automatically?▼

Yes, the verification process updates track frontmatter automatically. It reads local state, parses the track metadata, and writes updated verification timestamps to maintain an auditable history.