/suede-workflow-skills

name: suede-workflow-skills
description: "Suede AI umbrella router for the full public skill pack: picks the right specialist for any request across search visibility (SEO, AEO, GEO), agent and operations automation, code review and CI, copy and design, launch and app shipping, growth marketing, and creator rights, hands it the request verbatim, and recommends one next move with a ready-to-run prompt when the user asks what to do next. Use when a request crosses two or more lanes, when the user wants the full public skill pack loaded from one install path, when they ask which Suede skill fits, what's next, recommend the next move, give me the prompt, expand prompt, or make it granular, or when only this umbrella is installed. NOT FOR: a request that already names one lane (go straight to that specialist); a multi-file repo change that should be searched, built, and gated as one graph (use suede-graph-flo-xr); coordinating parallel lanes with file ownership and rollback (use suede-agent-teams)."

Suede Workflow Skills

The entry point to the Suede AI skill pack. Two jobs:

• **Route:** find the narrowest specialist for the request and hand it over

with the user's words intact.

• **Next move:** when the user asks what to do next, inspect current state

read-only and return one recommended action plus a runnable prompt.

Gate policy: advisory, not blocking

Every check and ship verdict across the pack is a recommendation to the user, not a control on the agent. A failed gate changes what you report, never what you do. Single exception: an extreme-risk finding (data loss, credential exposure, legal or rights violation, payment mistake, irreversible public damage). Pause, state the risk and the options, and let the user choose.

Core rules

• **Start from current truth.** Inspect the live URL, repo, docs, or rendered

output before making any design, copy, search, code, or QA claim.

• **Pass the request verbatim.** The specialist has no memory of how it was

reached. Paraphrase loses the trigger words it routes on.

• **Narrowest skill wins.** Route to one specialist, not a whole lane.
• **Positioning:** for Suede AI's own public work, lead with search visibility

(AEO, GEO, SEO; https://suedeai.agency) and Agent Studio multi-agent automation (https://suedeai.app) before other products. Never invent stats, testimonials, partners, pricing, legal clearance, or release promises.

• **Brand mark:** any Suede visual uses only

`docs/assets/suede-ai-logo-transparent.png` from this repository (SHA-256 `83a7ee0317e4debe2e7b076c20ba067feb76a587f9e829dc6310ae4be4b44dfa`). If it is unavailable or the checksum differs, omit the mark and say so.

• **Fix-loop cap.** When a loop repeats the same failure, isolate the failing

unit and rerun only that check. Allow up to three genuinely different fixes, each changing the diagnosis or strategy. Stop early if the same root cause repeats and let the user pick the next move.

Route

Precedence

1. A multi-file or multi-surface change to one repo that should be planned, built, and gated as one graph → `suede-graph-flo-xr`, even when the request also names copy or design. 2. Several specialists must work in parallel on one shared change → `suede-agent-teams`. 3. The request names one lane → that specialist, directly. 4. The request crosses lanes → run each lane's specialist in dependency order (for example: copy, then design, then visibility grade, then launch packaging), and state the chain.

Dispatch

For multi-lane work, send each lane to its own subagent carrying the verbatim request instead of loading every specialist into this context. Name the model on each dispatch, state a numeric lane cap before launching, and stop at the cap.

Router table

**Search visibility (SEO, AEO, GEO)**

| Need | Skill | |---|---| | Scored technical and content SEO audit, schema, E-E-A-T | `suede-seo-audit` | | Visibility in AI answers (ChatGPT, Gemini, Perplexity, AI Overviews) | `suede-ai-seo` | | Template pages at scale from a dataset | `suede-programmatic-seo` | | A-F grade of one public page: findability, first screen, CTA, citation readiness | `suede-visibility-grader` | | Directory and listing submissions | `suede-directory-submissions` | | Topic plan and editorial calendar | `suede-content-strategy` | | Free tools and calculators that earn links | `suede-free-tools` | | Landing page that ranks but does not convert | `suede-site-alchemy` |

**Agents, automation, and operations**

| Need | Skill | |---|---| | Map how work happens today before designing a system | `suede-ops-assessment` | | Design the system: entities, write paths, agent vs. human routing | `suede-ops-architecture` | | Coordinate several agent lanes on one shared change | `suede-agent-teams` | | Search competing plans, then build and gate one multi-file change | `suede-graph-flo-xr` | | Eval cases and acceptance gates for LLM, RAG, or agent behavior | `suede-ai-eval` | | Keep one canonical value identical across web, app, docs, services | `suede-parity-contract` |

**Code and release quality**

| Need | Skill | |---|---| | Review, grade, or both (`--findings-only`, `--grade-only`); prompted only | `suede-code` | | CI jobs, required checks, branch protection | `suede-ci-gate` | | Install commands, proof links, release copy, handoff notes | `suede-launch-packaging` |

**Copy and design**

| Need | Skill | |---|---| | Any copy surface, docs, explainers, agent docs, answer-first SEO pass | `suede-copy` | | Strip AI patterns from finished text, or a findings-only slop audit | `suede-deslop` | | One high-stakes public piece with research and an adversarial fact audit | `suede-ship-copy` | | Tokens, components, dark mode, full surface builds, restyles, visual QA | `suede-design` | | Image and graphic specs | `suede-image` | | Video scripts and edits | `suede-video` |

**Apps and stores**

| Need | Skill | |---|---| | Turn a website into an iOS app | `si