MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Next-action selector for the Suede pack: inspects current repo, terminal, plan, or handoff state read-only and returns one recommended next move plus a short, self-contained copy/paste prompt for it.
Install Suede Recommend Next Action
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-recommend-next-action --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-recommend-next-action .claude/skills/suede-recommend-next-action && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "suede-recommend-next-action" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-action into .claude/skills/suede-recommend-next-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-recommend-next-action", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-actionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-recommend-next-action --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/suede-recommend-next-action .agents/skills/suede-recommend-next-action && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "suede-recommend-next-action" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-action into .agents/skills/suede-recommend-next-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-recommend-next-action", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-recommend-next-action --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/suede-recommend-next-action .cursor/skills/suede-recommend-next-action && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "suede-recommend-next-action" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-action into .cursor/skills/suede-recommend-next-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-recommend-next-action", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JasonColapietro/suede-creator-skills.git --path skills/suede-recommend-next-action--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-recommend-next-action --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/suede-recommend-next-action .gemini/skills/suede-recommend-next-action && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "suede-recommend-next-action" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-action into .gemini/skills/suede-recommend-next-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-recommend-next-action", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JasonColapietro/suede-creator-skills suede-recommend-next-actionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/suede-recommend-next-action .github/skills/suede-recommend-next-action && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "suede-recommend-next-action" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-action into .github/skills/suede-recommend-next-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-recommend-next-action", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-recommend-next-action --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/suede-recommend-next-action .opencode/skills/suede-recommend-next-action && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "suede-recommend-next-action" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-recommend-next-action into .opencode/skills/suede-recommend-next-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-recommend-next-action", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
suede-recommend-next-action- GitHub stars
- 127
- Token cost
- ~1.4k tokens
- SKILL.md length
- 698 words
- Files
- 4 (incl. references)
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Next-action selector for the Suede pack: inspects current repo, terminal, plan, or handoff state read-only and returns one recommended next move plus a short, self-contained copy/paste prompt for it.
- Works in 4 steps: Resolve the target and the user's actual… → Check only the evidence needed to… → Generate 2-4 candidate actions… → …
- The user asks whats next
- SKILL.md covers Recommendation Workflow, Routing Rules, Prompt Levels and Output Format, plus 2 more sections
- Calls git, curl and make
What it does
Suede Recommend Next Action is an agent skill from JasonColapietro/suede-creator-skills. Next-action selector for the Suede pack: inspects current repo, terminal, plan, or handoff state read-only and returns one recommended next move plus a short, self-contained copy/paste prompt for it. Use when the user asks 'what's next', 'what should I do next', 'recommend the next move', 'give me the prompt', 'expand prompt', or 'make it granular', especially after a review, audit, plan, or stalled task. NOT FOR: executing the recommended action without the user's separate authorization, or coordinating a…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `references/prompt-levels.md`).
It sits in Agent Workflows. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.
When your agent uses it
- The user asks whats next
- What should I do next
- Recommend the next move
- Give me the prompt
Example prompts
- “s next”
- “what should I do next”
- “recommend the next move”
- “/suede-recommend-next-action”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Resolve the target and the user's actual done outcome from the current
- Check only the evidence needed to distinguish the next move. Prefer, in
- Generate 2-4 candidate actions internally. Exclude work already verified as
- Score each candidate from 0-2 on every criterion below. Recommend the
What it can do on your machine
Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitcurlmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Suede Recommend Next Action loads about 1.4k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 698 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 698 words, ~1,408 tokens.
Download SKILL.mdSave it as
.claude/skills/suede-recommend-next-action/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- suede-recommend-next-action
- description
- Next-action selector for the Suede pack: inspects current repo, terminal, plan, or handoff state read-only and returns one recommended next move plus a short, self-contained copy/paste prompt for it. Use when the user asks 'what's next', 'what should I do next', 'recommend the next move', 'give me the prompt', 'expand prompt', or 'make it granular', especially after a review, audit, plan, or stalled task. NOT FOR: executing the recommended action without the user's separate authorization, or coordinating a multi-lane build across specialists (use suede-agent-teams).
Suede Recommend Next Action
Recommend one action and package it as a short runnable prompt. Inspect current state read-only; do not execute the recommended action unless the user separately authorizes execution. Keep the full operator contract hidden until the user asks to expand it.
Recommendation Workflow
- Resolve the target and the user's actual done outcome from the current request, conversation, handoff, plan, repo, or live surface.
- Check only the evidence needed to distinguish the next move. Prefer, in
order: current terminal/repo/live state, current source documents, current
plans or handoffs, then older memory. Run the reads, don't assume them:
git -C <target-repo> status --short --branchfor dirty files and ahead/behind,git -C <target-repo> log --oneline -5for what actually landed, a direct read of the named plan/STATE/handoff file at its exact path, and, when a live surface is in scope, a fetch of the URL itself (curl -sS -o /dev/null -w '%{http_code}' <url>) instead of trusting the last recorded deploy. Skip any read that cannot change which candidate wins. - Generate 2-4 candidate actions internally. Exclude work already verified as complete, adjacent cleanup, and actions outside the user's authorized scope.
- Score each candidate from 0-2 on every criterion below. Recommend the highest total.
| Criterion | 2 points | 1 point | 0 points |
|---|---|---|---|
| Goal alignment | Directly produces the user's done signal | Required prerequisite | Merely adjacent |
| Unblocking | Unlocks a core path or at least two downstream steps | Unlocks one step | Unlocks nothing known |
| Evidence | Confirmed by current source | Confirmable with one read-only check | Depends on an assumption |
| Urgency | Active failure, deadline, security risk, or release gate | Needed for the active milestone | No current pressure |
| Leverage | Fits one focused session and prevents rework or creates a reusable result | Bounded work with moderate payoff | Unscoped, multi-day, or low-payoff work |
- Break ties by preferring a required prerequisite, then current-evidence verification, then the more reversible action. If the top two remain within one point and target ambiguity would change the answer, run at most three additional read-only checks. If still tied, show both choices and state the single fact that decides between them.
- Turn the recommendation into a 2-4 sentence quick prompt. Keep the scoring
and full operator contract internal unless the user asks to compare choices,
expand prompt, ormake it granular.
Show full SKILL.md (319 more words)Show less
Routing Rules
- If a repo or task already has its own plan, progress doc, issue tracker, or project board, do not create a second one. Treat its recorded next step as one candidate, verify it against current source, and recommend the winner: don't replace the existing tracker.
- If the user needs options explored before a commitment can be made, say so and offer to brainstorm instead of forcing a single recommendation.
- If missing evidence is the real blocker, make the smallest read-only check the recommended action and generate a prompt for that check.
Prompt Levels
The three prompt depths, short copy/paste, full operator prompt, granular steps,
are in references/prompt-levels.md. The default is the short prompt; read this
only when the user asks to expand or make it granular.
Output Format
Recommended action: <one sentence>
Why now: <one evidence-backed sentence>
Quick prompt: <2-4 runnable sentences>
Say "expand prompt" for the full operator version or "make it granular" for exact steps and commands.Show the route, score, evidence list, confidence, or alternatives only when the
user asks for rationale or when the unresolved tie rule requires them. When the
recommendation is an evidence-gathering step, state that in Why now without
loading the expanded prompt.
Boundaries
- Do not mutate files, repos, deployments, accounts, messages, or live systems while recommending.
- Do not load the expanded or granular prompt by default.
- Do not repeat a broad audit when one current execution lane can be selected.
- Do not invent paths, URLs, skill availability, status, metrics, owners, or completion evidence.
- Do not recommend vague actions such as "keep working", "improve the app", or "do more research". Name a command, artifact, decision, edit, or verification result.
- Do not hide a blocker. If authority or a decisive fact is missing, make its resolution the next action.
Routing
- Need multi-lane coordination across specialists -> use
suede-agent-teams. - Need help picking which single skill fits a request -> read this pack's
router (
suede-workflow-skills) or ask directly. - Need idea exploration before selecting a move -> brainstorm directly with the user instead of forcing a single recommendation.
- Need execution -> use the specialist named in the generated prompt.
© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/suede-recommend-next-action of JasonColapietro/suede-creator-skills.
- SKILL.md
- CARD.md
- agents/openai.yaml
- references/prompt-levels.md
Open the folder on GitHubat commit e5f94d7
Compare with similar skills
Suede Recommend Next Action next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Suede Recommend Next Action this skillJasonColapietro/suede-creator-skills | 127 | — | ~1.4k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from JasonColapietro/suede-creator-skills
All 78 skills in this repoSuede Release Linter
JasonColapietro/suede-creator-skills
Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.
Creator Rights Passport
JasonColapietro/suede-creator-skills
Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.
Suede Clip to Guide
JasonColapietro/suede-creator-skills
Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.
Suede MCP Release QA
JasonColapietro/suede-creator-skills
Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.
Android App Factory
JasonColapietro/suede-creator-skills
Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.
Suede Ad Creative
JasonColapietro/suede-creator-skills
Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.
Related
Categories
Questions about Suede Recommend Next Action
What does Suede Recommend Next Action do?
Next-action selector for the Suede pack: inspects current repo, terminal, plan, or handoff state read-only and returns one recommended next move plus a short, self-contained copy/paste prompt for it. Suede Recommend Next Action is an agent skill from JasonColapietro/suede-creator-skills. Next-action selector for the Suede pack: inspects current repo, terminal, plan, or handoff state read-only and returns one recommended next move plus a short, self-contained copy/paste prompt for it.
When should I use Suede Recommend Next Action?
Suede Recommend Next Action fits situations like: the user asks whats next; what should I do next; recommend the next move; give me the prompt.
How do I install Suede Recommend Next Action in Claude Code?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a claude-code`. Or copy the skill folder (skills/suede-recommend-next-action in JasonColapietro/suede-creator-skills) into .claude/skills/suede-recommend-next-action in your project. Claude Code loads it when a task matches its description.
How do I install Suede Recommend Next Action in Codex?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a codex`. Or copy the skill folder (skills/suede-recommend-next-action in JasonColapietro/suede-creator-skills) into .agents/skills/suede-recommend-next-action in your project. Codex loads it when a task matches its description.
Can I use Suede Recommend Next Action in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-recommend-next-action -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-recommend-next-action, .gemini/skills/suede-recommend-next-action, .github/skills/suede-recommend-next-action and .opencode/skills/suede-recommend-next-action in your project.
What does Suede Recommend Next Action need to run?
Going by SKILL.md and its folder, Suede Recommend Next Action needs the command-line tools its instructions call (git, curl and make).
Does Suede Recommend Next Action access the network?
SKILL.md contains no URLs. Its commands use git and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Suede Recommend Next Action safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Suede Recommend Next Action use?
Suede Recommend Next Action is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Suede Recommend Next Action use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 638 tokens, read only when the agent opens those files.
What are the alternatives to Suede Recommend Next Action?
Skills that share tags, products or a category with Suede Recommend Next Action: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Suede Recommend Next Action?
JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.
Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.