suede-release-linter

Lints music release folders and scores metadata, artwork, splits, and rights readiness.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-release-linter-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-release-linter
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-release-linter
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-release-linter-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, Pillow, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Creators preparing a music or media release often discover missing files, weak metadata, unconfirmed splits, or rights blockers only after a distributor or platform rejects the delivery. This Skill audits a local release folder offline and produces a scored readiness report before anything is shipped. ## Core Features & Use Cases - Automated folder linting: A bundled Python script inventories audio, video, artwork, lyrics, stems, and documents, then emits findings with error, warning, and info severities. - Scored reports: Generates release-lint-report.md and release-lint-report.json with a 0-100 score and a status band (blocked, needs-work, usable-with-cleanup, strong). - Metadata and rights checks: Validates title, artist, contributors, split totals, ownership confirmation, and sample clearance status against documented lint rules. - Use Case: A musician points the skill at an album folder before distribution and learns that publishing splits total 95 instead of 100, artwork is below 1400px, and sample clearance is unconfirmed, with concrete fixes for each. ## Quick Start Ask the agent to lint your release folder with suede-release-linter, for example: run the release linter on my album folder and give me the readiness score and top fixes.

Frequently Asked Questions about suede-release-linter

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

FAQPage Schema
How do I check if my music release folder is ready for distribution?

Run the bundled lint_release.py script against your release folder with python3, passing the source path and an output directory. It writes release-lint-report.md and release-lint-report.json containing a score, status band, and severity-classified findings with fixes.

What metadata format does a music release linter accept?

The linter accepts JSON, YAML or YML when PyYAML is installed, and public-safe key=value text files. It auto-discovers files like metadata.json or release.yaml in the source folder, or you can pass one explicitly with the --metadata flag.

Why does the release linter exit with code 1?

Exit code 1 means the report was written successfully but at least one error-severity finding exists, producing a blocked status. It is not a script failure, so you should read the generated report rather than re-running the script.

Does the release linter upload my files or confirm legal clearance?

No. The linter runs fully offline, never uploads files, calls distribution APIs, or writes to any registry. A clean report only means fewer preparation blockers; it is never a legal opinion, ownership confirmation, or distributor approval.

What split and rights problems block a music release?

Missing contributors, master or publishing splits that do not total 100, unconfirmed ownership, and unknown sample or cover clearance status are all error-severity findings. These block royalty routing and licensing until the creator supplies confirmations.