Suede Creator Skills is an open-source, MIT-licensed 21-skill workflow pack for Codex, Claude Code, and other agent-assisted product and creator workflows. It is broadly reusable tooling, not a closed Suede product funnel. Install it when an agent needs portable context, linked guidance, reference-site restyling, sharper copy, SEO/AEO/AI EO, GitHub Pages polish, visibility grades, A-F code review, coordinated agent teams, AI evals, iOS/product checks, launch evidence, and creator music/IP utilities without rebuilding the prompt stack.
The pack gives an agent a reusable product workflow: page structure, copy
standards, reference-site analysis, visual QA, review gates, install paths,
MCP scaffolds, a claim-safety boundary, and feedback loops that follow the
work. It keeps context linked and inspectable instead of stuffing every
preference into one giant prompt. In this pack, SEO includes AEO and AI EO:
search snippets, answer engines, AI summaries, schema, sourceable claims, and
citation-ready proof. When the agent does something that works, tell it what to
keep. When it misses, tell it exactly what to change. You can also say
Cue Suede mid-workflow or at the end to bring up choices: change something,
preserve what worked so the agent can mimic it later, or keep as-is by saying
nothing.
The components are reusable outside the Suede brand:
- Evolving context: the skill links to preferences and project guidance instead of trapping the agent in one bloated memory page.
- Suedify: give it a reference URL and a target URL, then push the target toward that aesthetic with your own assets, copy, SEO/AEO/GEO/AI EO, and QA.
- iOS/product packaging: turn a site or product into iOS-ready copy, App Store metadata, screenshot direction, native-contract checks, and release QA.
- Communicating agent teams: scout, build, review, verifier, and release lanes share evidence so subagents do not disappear into disconnected silos.
- Visibility scoring: grade findability, CTA pull, proof, AI readability, schema depth, Google and Gemini result-surface readiness, and brand clarity.
- Code and project grading: run A-F review across correctness, security, data, UX, deploy readiness, public-claim truth, missing gates, and next fixes.
- Music/IP suite: package campaigns, metadata, sync prep, rights packages, release lints, provenance, credits, split notes, and review reports.
- MCP: use structured skill discovery, install options, SEO/AEO/GEO/AI EO audit scaffolds, QA checklists, and MCP validation only when structure helps.
- Johnny Suede shortcuts: invoke Write, Design/Create, or Code to load the whole workflow; a supplied company brief overrides the default Suede voice.
Public GitHub users can bring their own company, repo, page, campaign, release, or product. Use the umbrella modes with a company brief, voice, audience, proof, allowed claims, forbidden claims, CTA, assets, and reference URLs; the workflow keeps the quality gates while using the user's brand voice and domain language.
Suedify is the marketable site workflow: give the agent a reference URL and a target URL, then have it study layout, hierarchy, spacing, type, color, motion, proof structure, and content rhythm before pushing the target toward the reference with brand-safe design, matched screenshots, token distillation, copy, SEO, and QA.
Even the GitHub Pages site is part of the pitch. It is not a README that got published by accident. The public site ships a polished landing page, docs guide, copy bank, skill catalog, MCP page, sitemap, schema, Open Graph assets, mobile-tested pages, and visible Jason Colapietro attribution from the same repo as the skills.
johnny-suede-write is the one-name writing mode: public copy, company voice,
product and mobile conversion copy, SEO/AEO/AI EO discoverability, CTAs,
launch copy, social/email variants, and anti-generic line editing with
Directness, Rhythm, Trust, Specificity, Authenticity, Density, and
Search/AI readability scoring. johnny-suede-design is the one-name design
mode: Suedify, mobile and product surfaces, product screenshots, UI polish,
design-system QA, responsive checks, visual QA, visibility grading,
implementation handoff, company voice, and the full writing mode included.
Suede Visibility Grader turns a public page into an A-F visibility and CTA brief. It checks whether a site can be found, understood, trusted, cited by AI systems, acted on, and promoted with rendered design evidence. Suede Code Grader gives code an A-F ship-risk grade with the reason why across correctness, security, state, UX, tests, deploy readiness, and public-claim truth. Suede Code Review keeps the deeper findings and fix brief workflow. Suede Agent Teams adds grouping loops for major work: scout, constraints mapping, safe parallel build, shared context, adversarial review, consensus review, design visibility review, A-F code grading, WIP protection, quality/eval gates, release lock, recovery replay, and evidence handoff without lanes stepping on the same files or acting like siloed subagents. Suede AI Eval turns AI-powered surfaces into measurable AI-SPECs, failure-mode rubrics, eval cases, acceptance gates, and coverage audits.
The artist lane turns a song, catalog moment, show, or drop into campaign material: era systems, song worlds, hook maps, release stunts, fan rituals, visualizer directions, merch objects, setlist theater, catalog resurrections, identity guides, collab angles, campaign-in-a-box plans, and sync-style review packages. Sync packaging stops at clean review prep: no placement promises, clearance claims, outreach claims, or Suede promo funnel.
Creator utility skills for release metadata, provenance, rights packages, and royalty notes include evidence tables and severity models for projects that need them, but they are support tools, not the headline.
The public site sells the workflow directly: install the umbrella skill, browse the 21 skill folders, use MCP only when structured discovery or QA helps, and keep legal, payout, registry, and distribution claims outside the public tools.
Suede is one downstream review workflow for creator ownership infrastructure, programmable IP, registry-backed media, royalty routing, licensing readiness, and agent commerce. The pack is useful without Suede: it inspects current files, pages, repos, and local folders, but it does not upload files, write to a registry, call private services, request secrets, or claim legal clearance.
- GitHub Pages site - public documentation generated from this GitHub repository, not a separate marketing site; the page itself is proof of the design/copy/SEO bar.
- GitHub repository
- Public explainer pack - long-form public guide for founders, builders, agencies, creators, AI power users, Suedify, MCP, skills, social posts, emails, SEO/AEO/AI EO metadata, FAQ, and claim boundaries.
- Suede Creator Skills copy bank - public copy for GitHub descriptions, docs pages, CTAs, SEO/AEO/AI EO snippets, FAQs, social posts, and safety language.
- Copy bank page - live copy bank for sharing, explaining, and documentation work.
- Public installs and MCP page - GitHub skill install commands plus the Suede Skills MCP server for skill discovery, SEO/AEO/AI EO copy audits, install guidance, and QA checklists.
- Skill docs catalog - public catalog with primary skill pages, install links, manifests, scripts, folders, and resource maps.
- Suede Agent Teams docs - controlled max-agent loops for scout, safe parallel build, adversarial review, visibility grading, code grading, release lock, recovery, and evidence handoff.
- Suede AI Eval docs - public eval workflow for AI-SPECs, failure-mode rubrics, prompt and retrieval test cases, acceptance gates, and coverage audits.
- Creator rights package docs - full documentation for transfer package generation, provenance, credits, splits, licenses, intake JSON, templates, safety defaults, and install prompts.
- Release linter docs - full documentation for music release linting, metadata checks, missing-file detection, rights blockers, report outputs, templates, and downstream next steps.
Install the umbrella workflow first and call it for Suedify, design, copy, SEO/AEO/AI EO, visibility grading, code grading, agent teams, AI evals, launch packaging, or creator utility work:
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/suede-workflow-skillsExample prompts:
Use $suedify. Study https://apple.com and push https://example.com toward that design language with brand-safe design, copy, SEO/AEO/AI EO, and QA.
Use $suede-workflow-skills to rewrite this page, audit SEO/AEO/AI EO, check design quality, and run final QA.
Use $johnny-suede-write for my company with our brand voice.
Company: Acme Robotics.
Audience: operations leaders at mid-market manufacturers.
Voice: precise, practical, slightly bold, never hype.
Proof: customer quotes, uptime reports, factory screenshots, install docs.
Forbidden claims: no guaranteed savings, no unverified rankings, no fake logos.
Primary CTA: book a plant-floor workflow review.
Use $johnny-suede-design for my company. Redesign this landing page with our
voice, proof, CTA, assets, and reference URLs while keeping the full design,
copy, SEO/AEO/AI EO, visual QA, and ship-gate workflow.
Utility scripts are available when the project needs local creator reports:
git clone https://github.com/jasoncolapietro/suede-creator-skills.git
cd suede-creator-skills
python3 skills/suede-release-linter/scripts/lint_release.py \
/path/to/music-project \
--output /path/to/release-lint-output
python3 skills/suede-rights-passport/scripts/create_transfer_package.py \
/path/to/creator-project \
--output /path/to/transfer-package \
--metadata /path/to/creator-project/metadata.json \
--project-title "Project Title" \
--artist "Artist Name"Both scripts skip hidden files, secret-like files, dependency folders, build outputs, and unrecognized file types by default.
Use PROMO.md when explaining the full workflow publicly. It
includes founder, designer, developer, agency, creator, and AI power-user
positioning plus reusable copy for Suedify, Suede Workflow Skills, the optional
MCP, install listings, social posts, DMs, email, SEO/AEO/AI EO metadata, FAQ
answers, objection handling, and safe claim boundaries.
The public-explainer rule: explain the outcome first. The pack gives agents a repeatable
workflow for Suedify, design, copywriting, SEO/AEO/AI EO, visibility and CTA
grading, code review with A-F Suede grades, QA, agent-team coordination, AI
evals, launch packaging, creator campaign tools, and optional MCP-assisted
discovery. Keep local install details such as @personal inside technical
setup sections.
Founder context for public explanations: the workflow was built from live pressure, not theory, turning repeated agent failures into reusable rules. The core conviction is that public work is not done until it is findable across Google, Gemini, and AI result surfaces, readable to AI systems, backed by proof, and clear enough for a real visitor to act.
Safety-oriented CLI flags:
--include-hidden: include hidden files and folders, while still skipping secret-like files.--include-other: include unrecognized file types in inventories.--include-absolute-paths: write absolute local paths into reports for private operator workflows. Reports use share-safer paths by default.--force: replace existing generated report/package files.
Suede skills can be installed from this public GitHub repo as plain Codex skills. Use the Suede Skills MCP when structured discovery, install guidance, SEO/AEO/AI EO copy audit scaffolds, or QA checklists would help the agent.
Public Codex skill installs:
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/suede-workflow-skillsInstall individual workflow and operations skills when you want direct triggers:
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/johnny-suede-design \
skills/johnny-suede-write \
skills/suede-code \
skills/suede-code-review \
skills/suede-code-grader \
skills/suede-copy \
skills/suede-design \
skills/suede-agent-teams \
skills/suede-ai-eval \
skills/suede-ship-gate \
skills/suede-seo-audit \
skills/suede-visibility-grader \
skills/suede-site-alchemy \
skills/suede-launch-packaging \
skills/suede-mcp-qaInstall creator skills:
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/suede-campaign-in-a-box \
skills/suede-sync-packaging \
skills/suede-release-linter \
skills/suede-rights-passport \
skills/suede-rights-auditRestart Codex after installing new skills.
Local personal marketplace plugin installs:
codex plugin add suede-workflow-skills@personal
codex plugin add suede-creator-skills@personalThese commands are for a local Codex personal marketplace where the Suede plugin sources are registered. They are not the public install route.
Optional MCP server names:
suede_workflow_mcpsuede_creator_mcp
The public repo also includes the dependency-free stdio MCP server:
node mcp/suede-skills-mcp.mjs --profile allMCP tools:
list_suede_skillsget_suede_skillsuede_install_optionssuede_copy_seo_auditsuede_visibility_gradesuede_code_gradesuede_qa_checklist
Folder: skills/suede-workflow-skills
Install the public umbrella workflow when you want one skill to load the Suede design, anti-slop copy, SEO/AEO/AI EO, site polish, visibility and CTA grading, code review with A-F Suede grades, visual QA, launch, install support, MCP QA, public explanation, agent-commerce, Suedify, progressive feedback, two-level final explanations, Cue Suede choices, max-agent grouping loops, artist campaign, and creator utility workflow. The repository now ships 21 public skill folders.
python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
--repo JasonColapietro/suede-creator-skills \
--path skills/suede-workflow-skillsIndividual workflow and operations skills (15):
skills/johnny-suede-designskills/johnny-suede-writeskills/suede-agent-teamsskills/suede-codeskills/suede-code-graderskills/suede-code-reviewskills/suede-copyskills/suede-designskills/suede-ai-evalskills/suede-ship-gateskills/suede-seo-auditskills/suede-visibility-graderskills/suede-site-alchemyskills/suede-launch-packagingskills/suede-mcp-qa
Creator skills (5):
skills/suede-campaign-in-a-boxskills/suede-sync-packagingskills/suede-release-linterskills/suede-rights-passportskills/suede-rights-audit
Folder: skills/suede-rights-passport
Turn a messy creator folder into a local rights and provenance transfer package. The skill inventories media, documents, lyrics, artwork, stems, credits, splits, licenses, provenance notes, missing rights information, and optimization blockers. Suede can be one downstream review workflow, but the package is broadly useful for creators, labels, managers, collaborators, registries, marketplaces, advisors, and agent-readable media workflows.
Outputs include:
RIGHTS_PASSPORT.mdsuede-intake.jsonprovenance.mdcredits-and-splits.mdlicense-notes.mdoptimization-brief.mdmissing-info-report.md
Run it locally:
python3 skills/suede-rights-passport/scripts/create_transfer_package.py \
/path/to/creator-project \
--output /path/to/transfer-package \
--project-title "Project Title" \
--artist "Artist Name" \
--copy-assetsThe script refuses to write the package into or under the source folder and
requires --force before replacing existing generated package files.
To prefill the package with known rights facts, pass --metadata with a
public-safe JSON, YAML, or key=value text metadata file. Do not point metadata
at real .env, credential, wallet, or deployment config files. Metadata can
provide project title, artist, owner claim, ownership status, contributor
confirmations, splits status, sample status, clearance notes, wallet/payment
destination, release history, public URLs, and provenance notes. Unknown or
unconfirmed facts remain flagged in the generated reports.
Folder: skills/suede-release-linter
Audit a song, album, catalog, stem pack, or media project before release, licensing, registry preparation, agent commerce, or downstream review. The linter checks for missing title, artist, metadata, final masters, artwork, lyrics, stems, contributors, split totals, sample status, release history, provenance notes, and readiness blockers.
Outputs include:
release-lint-report.mdrelease-lint-report.json
Run it locally:
python3 skills/suede-release-linter/scripts/lint_release.py \
/path/to/music-project \
--output /path/to/release-lint-outputWith metadata:
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-outputCodex skills live in $CODEX_HOME/skills, falling back to ~/.codex/skills
when CODEX_HOME is not set.
git clone https://github.com/jasoncolapietro/suede-creator-skills.git
cd suede-creator-skills
mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
cp -R skills/suede-rights-passport "${CODEX_HOME:-$HOME/.codex}/skills/"
cp -R skills/suede-release-linter "${CODEX_HOME:-$HOME/.codex}/skills/"Example Codex prompts:
Use $suede-release-linter to audit this album folder for release readiness.
Use $suede-rights-passport to organize this creator project into a rights and provenance package.
Quick install (all 21 skills):
git clone https://github.com/JasonColapietro/suede-creator-skills.git && bash suede-creator-skills/install.shClaude Code skills use SKILL.md files in .claude/skills/ directories. For a
project-level install:
git clone https://github.com/jasoncolapietro/suede-creator-skills.git /tmp/suede-creator-skills
cd /path/to/your-project
mkdir -p .claude/skills
cp -R /tmp/suede-creator-skills/skills/suede-rights-passport .claude/skills/
cp -R /tmp/suede-creator-skills/skills/suede-release-linter .claude/skills/For a user-level install:
mkdir -p ~/.claude/skills
cp -R skills/suede-rights-passport ~/.claude/skills/
cp -R skills/suede-release-linter ~/.claude/skills/Example Claude Code prompts:
Use the suede-release-linter skill to check this release folder.
Use the suede-rights-passport skill to organize this catalog into a local rights package.
Claude.ai and organization-managed Claude Skills may use upload or admin-managed skill flows instead of direct filesystem copy. Review the skill contents before enabling code execution.
creator folder
-> release metadata lint
-> missing info and rights fixes
-> rights and provenance transfer package
-> optional release, licensing, registry, collaborator, marketplace, or review workflow
Use the linter first when you want a fast audit. Use the rights package builder when you are ready to create a durable transfer package with hashes, provenance, credits, splits, license notes, and unresolved questions.
Use these links to inspect the open-source repo, install paths, docs pages, and skill resources.
- GitHub repository: https://github.com/JasonColapietro/suede-creator-skills
- GitHub Pages site: https://jasoncolapietro.github.io/suede-creator-skills/
- Skill docs catalog: https://jasoncolapietro.github.io/suede-creator-skills/skills/ - public index for every Suede Creator Skill and its install/resource links.
- Public explainer source: PROMO.md - full public explanation kit for Suede skills, MCP, Suedify, SEO/AEO/AI EO audits, QA, social posts, emails, FAQ, and claim boundaries.
- Copy bank page: https://jasoncolapietro.github.io/suede-creator-skills/copy.html - live GitHub, docs, CTA, SEO/AEO/AI EO, FAQ, social, and safety copy for Suede Creator Skills.
- Copy bank source: COPY.md - reusable public copy for repo metadata, skill pages, install surfaces, launch posts, and claim boundaries.
- Public installs and MCP page: https://jasoncolapietro.github.io/suede-creator-skills/plugins.html - GitHub skill install commands and Suede Skills MCP docs for skill discovery, SEO/AEO/AI EO copy audits, install guidance, and QA checklists.
- MCP source: mcp/ - dependency-free stdio MCP server, catalog, and MCP README.
- Creator rights package docs: https://jasoncolapietro.github.io/suede-creator-skills/skills/suede-rights-passport.html - transfer package docs for creator rights, provenance, splits, license notes, intake JSON, and optimization briefs.
- Release linter docs: https://jasoncolapietro.github.io/suede-creator-skills/skills/suede-release-linter.html - release-readiness docs for metadata, artwork, masters, lyrics, stems, credits, samples, reports, and downstream blockers.
- Rights Passport skill: skills/suede-rights-passport/SKILL.md
- Rights Passport script: skills/suede-rights-passport/scripts/create_transfer_package.py
- Rights Passport OpenAI metadata: skills/suede-rights-passport/agents/openai.yaml
- Rights Passport references: skills/suede-rights-passport/references/
- Rights Passport templates: skills/suede-rights-passport/assets/
- Release Linter skill: skills/suede-release-linter/SKILL.md
- Release Linter script: skills/suede-release-linter/scripts/lint_release.py
- Release Linter OpenAI metadata: skills/suede-release-linter/agents/openai.yaml
- Release Linter references: skills/suede-release-linter/references/
- Release Linter templates: skills/suede-release-linter/assets/
- Page source: docs/index.html
- Skill docs source: docs/skills/
Platform references:
- OpenAI Skills examples: https://github.com/openai/skills
- Claude Code skills documentation: https://docs.claude.com/en/docs/claude-code/skills
- Claude Skills help center: https://support.claude.com/en/articles/12512180-using-skills-in-claude
Jason Colapietro is the founder and CEO of Suede Labs AI, a published author, and a Forbes contributor. He builds programmable IP and creator ownership infrastructure for AI-native media.
"The gap in the creator economy isn't talent. It's the gap between the moment you make something and the moment you own it in a form that can be licensed, monetized, and defended."
"Rights metadata is the dark matter of the creative economy. It governs everything. Almost nobody can see it."
"Every piece of music that enters the world has a signal chain. The IP chain is just the part most musicians never mapped until now."
"Build what doesn't exist yet. Register that you built it. That sequence is the whole game."
- The Signal Chain: Illustrated electric-guitar tone history, memoir, method, and workbook editions. From pickup to speaker, from gear to IP. (guitar.solutions)
- The Guitar Without a Number: Memoir-driven guitar instruction for the self-taught player. Theory, tone, artist songbooks, and a music IP rights chapter. (Amazon author store)
- Suede Labs: The Human Authenticity Layer: How ownership, origin, and AI redraw the creative map. (Kindle)
- Proof as Infrastructure: Designing durable systems without trust assumptions. (Kindle)
- Stake Your Claim: Hard truths on turning the AI era into a real asset. (Kindle)
Follow: X / @johnnysuede · suedeai.ai · suedeai.ai/founder
A clean lint report or completed transfer package is not a legal opinion, distributor approval, registry write, rights clearance, payment guarantee, or platform approval. These skills prepare materials so creators, reviewers, and advisors can inspect the work with better structure.
Generated reports and transfer packages are private drafts by default. They can contain creator names, wallet/payment notes, file names, hashes, rights claims, contributor details, restrictions, and provenance notes. Review and redact them before publishing, committing, or sending outside the intended workflow.
The scripts are dependency-light Python and run with the standard library. Optional enhancements use installed packages when available, such as Pillow for artwork dimension checks or PyYAML for YAML metadata parsing.
YAML metadata support requires PyYAML:
python3 -m pip install PyYAMLReleased under the MIT License.
Contributions are welcome for docs fixes, install-path corrections, lint rules, template improvements, and public-safe workflow improvements. Do not submit private catalogs, unreleased media, credentials, seed phrases, private Suede API details, payment secrets, or third-party copyrighted files.


