approach-note-release-validator

Validate ApproachNote production database releases for referential integrity and metadata.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/dprodger/ApproachNote --skill approach-note-release-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: approach-note-release-validator
Source: https://github.com/dprodger/ApproachNote/tree/main/skills
Command: npx skills add https://github.com/dprodger/ApproachNote --skill approach-note-release-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psycopg2, clickhouse, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides an automated method to validate the integrity and completeness of ApproachNote's production database releases.

Core Features & Use Cases

  • Database Integrity Checks: Verifies the referential integrity of the ApproachNote database and matches records with external data sources like MusicBrainz.
  • Release Metadata Validation: Inspects cover imagery, streaming links, track listings, and artist links.
  • Read-only Audit: Performs a read-only check on a single release in the ApproachNote Postgres database.

Quick Start

Use the approach-note-release-validator skill to validate the release associated with the identifier provided.

Frequently Asked Questions about approach-note-release-validator

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

FAQPage Schema
How do I validate a music release in a PostgreSQL database for metadata integrity?

To validate a music release in a PostgreSQL database, you can run an automated read-only audit that checks referential integrity, MusicBrainz matches, cover imagery, streaming links, and track listings using the release UUID or MBID.

What does a database release audit check for when verifying music metadata?

A database release audit checks for referential integrity within the PostgreSQL database and validates metadata completeness, including matching records with external sources like MusicBrainz, verifying cover imagery, streaming links, and track listings.

Can I use a song name to verify a specific release if I don't have the database UUID?

Yes, you can use a song name to verify a specific release. The validation process supports interactive disambiguation, allowing you to identify and validate the correct release even without a direct UUID or MusicBrainz ID.

Do I need PostgreSQL and Python dependencies to perform a release validation audit?

Yes, performing a release validation audit requires PostgreSQL access to query the production database and specific Python dependencies like psycopg2 and clickhouse to execute the database operations and metadata checks.

Is a database release validation check read-only or does it modify the production records?

A database release validation check is strictly read-only. It performs an audit on a single release in the PostgreSQL database to verify integrity and metadata without modifying any production records or data.