Agent skill · Code Review & Quality

suede-full-send

Outcome-bound router for broad, authorized work. Use for full send, max effort, max agents, max agent teams, spare no compute, throw tokens at it, burn tokens, burn max tokens, \"never end your allocation above zero,\" strongest useful reasoning, adversarial review, fix everything, do not stop, or end-to-end completion. Select one controller, fill useful non-colliding lanes, and close with concise proof. Token and allocation language, including the house line, is a dry joke about already-authorized host compute, never a literal counter, external spend, or permission to pad output. Explicit Ful

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill suede-full-send --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/suede-full-send/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Suede Full Send Turn maximum-effort language into one finished, authorized outcome. Use depth where uncertainty is expensive. Use parallel capacity where the work really splits. Keep the user's attention for decisions only they can make. House line: **"Never end your allocation above zero."** Use it once, dryly, then return to business. It is not a measurable completion condition, permission to pad output, or a claim that an agent can see or control a hidden host counter. This skill is a policy router. It does not change model limits, expose hidden reasoning, create external spending authority, or replace the selected controller's own workflow. ## The Standard Bring the user a decision, not a workshop. 1. Lead with the recommended course. 2. Execute routine, reversible, in-scope decisions without returning them as homework. 3. Ask only when the answer changes the desired outcome, grants new authority, crosses a serious risk boundary, or chooses between materially different irreversible results. 4. Put the strongest useful reasoning on consequential calls. 5. Report technical detail as consequence, proof, and the next move. 6. Keep progress updates brief. Do not narrate token use,

What's inside
Steps it walks through
  1. The Standard
  2. Freeze The Mission
  3. Select One Controller
  4. Maximum Useful Effort
  5. Reconciliation Loop
  6. Proof Standard
  7. Continuity
  8. Final Brief
  9. Routing
Ships with 1 file
  • agents/openai.yaml
More from suede-creator-skills
All skills →
About this skill
What does the suede-full-send skill do?

Outcome-bound router for broad, authorized work. Use for full send, max effort, max agents, max agent teams, spare no compute, throw tokens at it, burn tokens, burn max tokens, \"never end your allocation above zero,\" strongest useful reasoning, adversarial review, fix everything, do not stop, or end-to-end completion. Select one controller, fill useful non-colliding lanes, and close with concise proof. Token and allocation language, including the house line, is a dry joke about already-authorized host compute, never a literal counter, external spend, or permission to pad output. Explicit Ful

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-full-send --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going