suede-workflow-skills

Routes multi-lane requests to specialist Suede skills across copy, design, code review, SEO, and launch workflows.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-workflow-skills-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-workflow-skills
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-workflow-skills
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-workflow-skills-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a request spans several disciplines — copy, design, code review, SEO, launch packaging, creator rights — it is unclear which specialist workflow should handle it, and loading every workflow at once wastes context. This umbrella router inspects the request and dispatches each lane to the right Suede specialist skill, or falls back to condensed built-in workflows when the specialists are not installed. ## Core Features & Use Cases - Specialized Lane Router: Maps requests to copy, design, build/quality, ship, launch, growth/marketing, creator, and consumer-recovery lanes, passing the original user request verbatim to each specialist. - Umbrella-Only Fallback: Ships condensed versions of the Suedify, design, copy/SEO, visibility grading, site alchemy, code review, and agent-team workflows for installs where only this skill is present. - Advisory Quality Gates: Applies copy, design, design-system, visual QA, and agent-team gates as recommendations, with a fix-loop cap that stops repeated failures and hands the decision back to the user. - Use Case: A user asks to polish a landing page, audit its SEO, and review the underlying code in one session; the router dispatches the design lane to the design specialist, the audit to the SEO specialist, and the review to the code specialist, each with the verbatim request. ## Quick Start Ask the agent to handle a request that crosses multiple Suede lanes, such as reviewing a launch page's copy, design, and code together, and it will route each part to the right specialist.

Frequently Asked Questions about suede-workflow-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route a request that spans copy, design, and code review?

Invoke the umbrella workflow and it dispatches each lane to its own specialist subagent, passing your original request verbatim. Each lane runs independently with a named model and a numeric lane cap, so multi-lane work stays coordinated without loading every specialist into one context.

What is the difference between the umbrella skill and individual Suede skills?

Individual skills like suede-copy or suede-seo-audit own the current version of one workflow and should be used directly when a request names a single lane. The umbrella skill selects among them for cross-lane requests and carries condensed fallback workflows for installs where specialists are absent.

Can I use this skill in Codex without installing the full pack?

Yes. The Codex install path supports installing only the umbrella skill from the GitHub repository. In that configuration it falls back to the condensed workflows reference file, which carries frozen versions of the Suedify, design, copy/SEO, visibility, site-alchemy, code-review, and agent-team workflows.

Do the quality gates block my work from shipping?

No. Every gate, grade, and ship verdict is advisory: it changes what is reported, never what the agent does. The single exception is extreme-risk findings such as data loss, credential exposure, or legal violations, where the agent pauses and lets you decide.

When should I not use the umbrella router?

Skip it when a request names one lane that can go straight to its specialist, or when a multi-file repo change should be built and reviewed as one DAG, which routes to suede-graph-flo-xr instead. Using the router for single-lane tasks adds unnecessary dispatch overhead.