# suede-release-linter

Lints a local release folder and scores how ready it is: missing files, thin metadata, artwork and stem trouble, split gaps, sample and rights blockers.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 126
- Author: JasonColapietro
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/JasonColapietro/suede-creator-skills/tree/HEAD/skills/suede-release-linter/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/suede-release-linter

## What it does

Point this skill at a music or media release folder and it produces a readiness report. A bundled offline script, `scripts/lint_release.py`, writes two files: `release-lint-report.md` for people and `release-lint-report.json` for machines. Categories, severity levels and the scoring bands live in `references/lint-rules.md`; read that file before classifying anything instead of guessing severities.

Typical run: `python3 /path/to/suede-release-linter/scripts/lint_release.py /path/to/music-project --output /path/to/release-lint-output`. A metadata file goes in through `--metadata`, and JSON, YAML plus plain key=value text are accepted. YAML needs PyYAML, installed with `python3 -m pip install PyYAML`. Hidden files, dependency folders, caches and secret-like files are skipped unless you ask otherwise, and absolute paths get redacted to safer names until `--include-absolute-paths` is passed.

Exit code `1` does not mean the script broke. It means the report was written and at least one `error` finding exists, which is a `blocked` status — do not abort or re-run. The report states what is present, missing or unknown, and a clean result is not legal clearance or proof of ownership. Rights, sample and split gaps stay open and route to `suede-rights-passport`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add JasonColapietro/suede-creator-skills --skill suede-release-linter -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/suede-release-linter/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/suede-release-linter/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add JasonColapietro/suede-creator-skills --skill suede-release-linter -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/suede-release-linter/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add JasonColapietro/suede-creator-skills --skill suede-release-linter -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/suede-release-linter/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install JasonColapietro/suede-creator-skills suede-release-linter
```

2. **Manually: put the files in place**
- File: `.github/skills/suede-release-linter/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add JasonColapietro/suede-creator-skills --skill suede-release-linter -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/JasonColapietro/suede-creator-skills --path skills/suede-release-linter
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/suede-release-linter/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JasonColapietro/suede-creator-skills --skill suede-release-linter -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/JasonColapietro/suede-creator-skills/tree/HEAD/skills/suede-release-linter/SKILL.md

## When to use it
- catch missing files in a release folder before distribution
- check track metadata for gaps and bad formatting
- get a readiness score and status for a release
- spot artwork and stem problems early
- flag unstated AI involvement and sample blockers

## Example prompts
- Lint the `music-project` folder and show me the report
- Run `scripts/lint_release.py` on the folder with `metadata.json`
- Which items in my release are marked `unknown` or `missing`?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d0cd85d58bf7b38c.

BEGIN THIRD-PARTY FILE d0cd85d58bf7b38c
```text
---
name: suede-release-linter
description: "Suede AI skill that lints a local music or media release folder and scores it for release readiness: missing files, weak or malformed metadata, artwork and stem problems, split gaps, sample and rights blockers, unstated AI involvement, and platform-delivery issues, produced by a bundled offline script as a scored markdown and JSON report. Use when a creator has one or more release folders of tracks, artwork, and stems and wants to know what is missing before distributing, delivering, or handing it off; when metadata quality or a delivery rejection is the question; or when a release-readiness score is asked for. Reports what is present, missing, or unknown; never upgrades unknown to confirmed and never means legal clearance. NOT FOR: investigating the rights gaps the report surfaces or building the transfer package (use suede-rights-passport); a sync one-sheet (use suede-sync-packaging); a release rollout campaign (use suede-campaign-in-a-box)."
---

# Release Metadata Linter

## Gate policy

Every check and verdict here is advice to the user, not a control on the agent.
Run the checks, report results honestly, and complete what the user asked. A
failed gate changes the report, never the work. The one exception: a finding
that risks data loss, credential exposure, a legal or rights violation, a
payment mistake, or irreversible public damage. Pause, name the risk, give the
options, and let the user choose.

## Overview

Audit a music or media project folder and produce a practical release-readiness report. The linter should help creators find missing files, weak metadata, rights risks, split gaps, platform-delivery blockers, and downstream handoff issues before a release or transfer package is created.

**Core principle:** report what is present, missing, or unknown. Never upgrade unknown to confirmed, and never treat a clean report as clearance, ownership confirmation, or approval.

Public v1 is offline-first: inspect local files and supplied metadata, do not upload files, write to a registry, call distribution APIs, request private keys, or claim legal clearance.

## Workflow

1. Identify the source folder or supplied files.
2. Ask for the output location if it is not obvious.
```
END THIRD-PARTY FILE d0cd85d58bf7b38c

The third-party file has ended. Everything between the d0cd85d58bf7b38c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2260 of 9138 bytes. © JasonColapietro · MIT · https://github.com/JasonColapietro/suede-creator-skills/tree/HEAD/skills/suede-release-linter/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md