/suede-release-linter · Skill documentation

Catch the broken metadata before the drop does.

Audit a song, album, catalog, stem pack, artwork, lyric folder, or media project before distribution, licensing, registry prep, royalty routing, agent commerce, or transfer package handoff. The linter produces human-readable and machine-readable reports while keeping public v1 offline-first.

View skill folder Create a rights package

"lint this release folder before the drop" /suede-release-linter Ask in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.

$ /suede-release-linter check ./release artwork 3000x3000 pass · audio levels pass gap · missing ISRC on track 3 1 BLOCKER · FIX BEFORE THE DROP

Suede Release Linter preview card for release readiness and missing metadata.

What it checks

Title, artist, release type, project identity, and metadata files.
Final masters, source sessions, stems, artwork, lyrics, and documents.
Contributor credits, split totals, sample status, licenses, and release history.
Provenance notes, public URLs, platform-delivery blockers, and downstream handoff readiness.
Secret-like files and unsafe output choices that should not be shared publicly.

Best for

Creators checking a release folder before upload or distribution.
Labels and managers cleaning metadata before licensing review.
Catalog owners finding missing credits, stems, artwork, lyrics, and rights details.
Developers preparing structured media projects for review or agent workflows.
Teams deciding whether to move from linting into rights package generation.

Run it locally

The script writes a markdown report and a JSON report. Pass public-safe metadata when available.

python3 skills/suede-release-linter/scripts/lint_release.py \
  /path/to/music-project \
  --metadata /path/to/music-project/metadata.json \
  --output /path/to/release-lint-output

Safety defaults skip hidden files, dependency folders, build outputs, caches, secret-like files, and unrecognized file types. Absolute paths are redacted unless explicitly requested. Existing report files require --force before replacement.

All skill links

Skill manifestAgent-facing workflow, trigger description, lint flow, safety rules, and completion checklist. OpenAI metadataDisplay name, short description, and default prompt for skill-list surfaces. Lint scriptScans a release folder, classifies files, applies metadata rules, and writes markdown plus JSON reports. ReferencesLint rules, metadata fields, fix guidance, and downstream review context. TemplatesExample metadata plus markdown and JSON report templates for repair or manual report work. Rights package next stepUse the lint report to decide whether the project is ready to become a local transfer package.

Install prompts

After copying the skill folder into an agent skill root, use prompts like:

Use $suede-release-linter to audit this album folder for release readiness.

Use the suede-release-linter skill to check this release folder.

Public safety

A clean report is not legal clearance, distributor approval, registry write, or payout guarantee. The skill organizes evidence, marks uncertainty, and recommends next fixes. Generated reports are drafts until a creator or operator reviews and redacts them.