Claude Code, Codex, and any skills-CLI agent

Install Suede once. Stop rebuilding the agent brief.

Two commands, and your agent has the folder that runs Suede Labs. A hardcoded secret caps a staged diff at F, with the file and the line. The same folder argued $448.31 back from a real Amazon account. Suede Graph Flo XR writes competing plans for a repo change, refutes the survivors, and builds one.

Which install is yours Same skill contracts on every runner; only Claude Code runs the bundled workflow
Install paths Claude Code installs the plugin in two lines. Codex installs the Codex-native plugin. Cursor, Copilot, and Windsurf install through the skills CLI. A git clone runs install.sh. All four install the portable skill contracts. The full and workflow Claude Code plugins, plus install.sh, also register the six profiles required by Suede Graph Flo XR's bundled workflow. MCP is an optional layer on top. Your agent pick one row Claude Code /plugin install suede-skills@suede Codex codex plugin add suede-skills@suede-codex Cursor / Copilot / Windsurf npx skills add ... Anything else git clone && install.sh 76 skills, loaded on demand MCP (optional) 9 tools · 7 resources 5 prompts · stdio

Claude Code: two lines

Add the marketplace, install the pack. suede-skills brings the whole folder. 30 seconds, start to finish.

/plugin marketplace add JasonColapietro/suede-creator-skills
/plugin install suede-skills@suede

Take a slice instead. Three focused subsets install the same way: /plugin install suede-marketing@suede (43 skills: paid acquisition, outbound, pricing, offers, lifecycle, Instagram growth, the six-role content newsroom, AI search optimization, attribution, and analytics), /plugin install suede-agent-workflows@suede (orchestration and evals), or /plugin install suede-code@suede (review and the A-F ship grade). A subset is fewer descriptions in context, nothing else. An installed skill costs its name and description, and the body loads only when a request matches.

Prefer a clone? install.sh copies every skill into ~/.claude/skills/ and never touches skills that are not part of the pack:

git clone https://github.com/JasonColapietro/suede-creator-skills.git && bash suede-creator-skills/install.sh

Cursor, Copilot, Windsurf, and the rest take one line. The open skills CLI installs the whole pack into every agent it supports, Claude Code and Codex included:

Every route installs the portable skill contracts. One thing does not travel. The executable Suede Thought Graph workflow, capped at 55, 110 or 200 calls and read-only against production, needs Claude Code on macOS plus its six suede-graph-flo-xr-* agent profiles. The full plugin, the suede-agent-workflows subset, and install.sh register them; Codex and skills-CLI installs follow the contract by hand.

npx skills add JasonColapietro/suede-creator-skills

For a project-level copy of a single skill in Claude Code: cp -R suede-creator-skills/skills/<name> .claude/skills/. A single-folder copy of Suede Graph Flo XR installs its orchestration contract only. To run its bundled workflow, also copy skills/suede-graph-flo-xr/agents/suede-graph-flo-xr-*.md into ~/.claude/agents/ and restart Claude Code.

Codex: two lines and a restart

The Codex-native plugin installs every skill contract and registers three read-only MCP discovery profiles. They answer questions about the pack and write nothing. Add the repo marketplace, install the pack, restart Codex.

codex plugin marketplace add JasonColapietro/suede-creator-skills --ref main
codex plugin add suede-skills@suede-codex

Want only selected skills? Codex can also install any public skill folder from GitHub. Direct skill installs land in ~/.codex/skills (or $CODEX_HOME/skills).

The umbrella: start here

One skill that picks the rest. Every description carries a NOT FOR line naming the sibling that should win instead, so your agent loads one skill and not five.

python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
  --repo JasonColapietro/suede-creator-skills \
  --path skills/suede-workflow-skills
Direct workflow skills

Install one skill and trigger it by name. suede-code grades a staged diff A-F across 7 lanes, and the weakest lane caps the grade. Pass extra skills/<name> paths to take several at once:

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-agent-teams \
  skills/suede-ai-eval \
  skills/suede-recommend-next-action \
  skills/suede-deslop \
  skills/suede-ci-gate \
  skills/suede-seo-audit \
  skills/suede-visibility-grader \
  skills/android-app-factory
Creator toolkit

For music, media, and artist-campaign work: campaigns, sync packaging, release linting, rights evidence. They organize evidence; they do not clear rights.

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-audit
Read every skill in the folder See which plan survives the DAG Find what locks a diff at F Check how a page earns an A

Hermes Agent: one tap, then take what you need

This repo is a Hermes skills tap: a GitHub repo laid out as skills/<name>/SKILL.md, which is what it already was. Subscribe to browse and search the pack inside Hermes, or install a single skill without subscribing at all.

hermes skills tap add JasonColapietro/suede-creator-skills
hermes skills install JasonColapietro/suede-creator-skills/skills/suede-seo-audit

Hermes downloads the whole skill folder, not just the contract: references/, agents/, and evals/ come with it. Every install runs through Hermes' own security scan first, and the skill lands in ~/.hermes/skills/ as a /skill-name command. The repo ships a skills.sh.json grouping sidecar, so the hub files each skill under its lane — Code review & CI, Search & AI visibility, Money & funnel — instead of guessing from tags.

What does not travel: the three MCP discovery profiles and the executable Suede Thought Graph workflow, which are Claude Code and Codex surfaces. The orchestration contracts install and read normally.

The Suede Skills MCP: zero dependencies

A dependency-free stdio MCP server ships in the repo at mcp/. Open it and read it before you point an agent at it, then run the one line below.

node mcp/suede-skills-mcp.mjs --profile all

Profiles: all, the bundle areas workflow, marketing, creator, consumer, or any one specialty — ship, craft, found, demand, revenue, position. It implements initialize, tools/list, tools/call, resources/list, resources/read, prompts/list, and prompts/get: 9 tools, 7 resources, 5 prompts. No dependencies, no network calls, no install step beyond running the file.

The MCP surface One process, area and specialty profiles, zero dependencies
The Suede Skills MCP surface An agent speaks JSON-RPC over stdio to the server, which selects an area or specialty profile and exposes 9 tools, 7 resources, and 5 prompts. Your agent JSON-RPC stdio suede-skills-mcp.mjs --profile all workflow marketing creator consumer 9 tools list / search / get / install_options / grades / qa 7 resources catalog, plugins, audit and grade scaffolds 5 prompts discovery and audit entry points

The 9 tools

list_suede_specialtiesLists the six specialties, their sub-lanes, and skill counts. Call it first to pick a specialty, then filter with it.
list_suede_skillsLists Suede skills, optionally narrowed to one bundle area or one specialty.
search_suede_skillsRanks the pack against a task description and returns the best-matching skills instead of the whole pack.
get_suede_skillReturns one skill description and when to use it, or the full SKILL.md with includeBody.
suede_install_optionsReturns public skill, MCP, local plugin, and skill-copy install options.
suede_copy_seo_auditBuilds an SEO/AEO/AI EO copy audit scaffold with metadata, schema, CTA, proof, and verification checks.
suede_visibility_gradeBuilds an A-F visibility and CTA grading scaffold: findability, first-screen clarity, proof, AI readability, design signal, grade caps, ship readiness.
suede_code_gradeBuilds an A-F code grading scaffold: correctness, security, data/state, UX and release behavior, tests, deploy readiness, required upgrades.
suede_qa_checklistBuilds a multi-lane QA checklist for MCP, skills, docs, local plugin notes, and public site work.

What changes the first time your agent runs it

Skill discoveryYour agent ranks the pack against your task and gets the matches back, instead of picking the skill it happens to remember.
Install optionsThe marketplace line, the MCP route, and the copy path come back as structured guidance, instead of a command your agent invented.
Grading scaffoldsVisibility and code checks route through A-F graders across 7 lanes, where the weakest lane caps the grade, instead of vibes.
QA loopsOne call returns a multi-lane checklist for skills, MCP, docs, and site changes, instead of whatever you remembered to check.

The pack costs you descriptions

Every installed skill costs its name and description. One body loads when a request matches. Every description carries a NOT FOR line naming the sibling that should win instead.

Aug 2026 71 skills installed. Your agent reads almost none of them. Progressive disclosure, 55/110/200-call Suede Thought Graph shipping (winner-only, read-only, never deploys), and this MCP layer Aug 2026 Why breadth is free now, and what that changes Every SKILL.md stays on disk; only the descriptions sit in context, and one body loads at a time Aug 2026 NOT FOR: the two words that make a big skill pack work How the router picks one skill instead of five Archive All essays The full writing archive

Read PROMO.md before you install anything

PROMO.md explains the whole workflow to people who did not build it. It names the mechanisms and their numbers: an A-F code grade across 7 lanes, and a 50-point score gate on deslop.

This page is the GitHub Pages surface generated from the public repo, not a separate marketing site. The install commands, docs, sitemap, and skill pages live beside the source.

The skills and MCP inspect local files and pages and return structured context. They do not upload music, clear rights, write to a registry, distribute releases, approve payouts, or publish unsupported statements on their own.

Proof is part of the release.

First install takes two commands. After the marketplace is added, install is one. Every skill is plain Markdown.

$ /plugin marketplace add JasonColapietro/suede-creator-skills → /plugin install suede-skills@suede Open one before you trust it