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.
Mainline deploy steward. An agent skill from SethGammon/Citadel.
Install Deploy Steward
$ npx skills add SethGammon/Citadel --skill deploy-steward -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SethGammon/Citadel deploy-steward --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/SethGammon/Citadel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deploy-steward .claude/skills/deploy-steward && 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 "deploy-steward" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/deploy-steward into .claude/skills/deploy-steward/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-steward", 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/SethGammon/Citadel/tree/main/skills/deploy-stewardType 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 SethGammon/Citadel --skill deploy-steward -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SethGammon/Citadel deploy-steward --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deploy-steward .agents/skills/deploy-steward && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploy-steward" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/deploy-steward into .agents/skills/deploy-steward/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-steward", 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 SethGammon/Citadel --skill deploy-steward -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SethGammon/Citadel deploy-steward --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deploy-steward .cursor/skills/deploy-steward && 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 "deploy-steward" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/deploy-steward into .cursor/skills/deploy-steward/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-steward", 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/SethGammon/Citadel.git --path skills/deploy-steward--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 SethGammon/Citadel --skill deploy-steward -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SethGammon/Citadel deploy-steward --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deploy-steward .gemini/skills/deploy-steward && 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 "deploy-steward" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/deploy-steward into .gemini/skills/deploy-steward/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-steward", 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 SethGammon/Citadel deploy-stewardInstalls 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 SethGammon/Citadel --skill deploy-steward -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deploy-steward .github/skills/deploy-steward && 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 "deploy-steward" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/deploy-steward into .github/skills/deploy-steward/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-steward", 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 SethGammon/Citadel --skill deploy-steward -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SethGammon/Citadel deploy-steward --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deploy-steward .opencode/skills/deploy-steward && 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 "deploy-steward" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/deploy-steward into .opencode/skills/deploy-steward/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-steward", 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
deploy-steward- GitHub stars
- 922
- Token cost
- ~1.7k tokens
- SKILL.md length
- 737 words
- Files
- 1
- Skills in repo
- 48
- Repo updated
- First seen
- Licence
- MIT
At a glance
Mainline deploy steward. An agent skill from SethGammon/Citadel.
- Works in 4 steps: Build the Queue → Acquire the Steward Lease → Process One Mainline Candidate at a Time → …
- Agent Workflows work in your project
- SKILL.md covers When to Use, Required Inputs, Invocation Forms and Protocol, plus 5 more sections
- Calls node and gh; reaches github.com
What it does
Deploy Steward is an agent skill from SethGammon/Citadel. Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: The operating layer for Claude Code + OpenAI Codex: persistent project memory, intent routing, safety hooks, cost telemetry, and parallel agent fleets. The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/deploy-steward”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e41ff1d. 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:
nodegh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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
Deploy Steward loads about 1.7k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 737 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 SethGammon/Citadel at commit e41ff1d, republished under its MIT licence (© SethGammon). 737 words, ~1,673 tokens.
Download SKILL.mdSave it as
.claude/skills/deploy-steward/SKILL.md (or your agent's skills folder).- name
- deploy-steward
- description
- Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
- license
- MIT
- user-invocable
- true
- auto-trigger
- false
- trigger_keywords
- deploy steward, deploy queue, merge steward, mainline steward, land prs, land PRs, deploy prs, deploy PRs, merge queue, release train
- effort
- high
- last-updated
- 2026-06-20
/deploy-steward - Mainline Deploy Steward
You are the deploy steward. You serialize mainline landing for parallel agent work. Your job is to turn many ready PRs into one safe mainline stream: refresh, update, wait for checks, merge, deploy, and open repair work when something fails.
When to Use
Use this when the user asks to:
- land multiple ready PRs without a manual merge stampede
- keep agent PRs rebased or branch-updated against latest main
- merge only after required checks pass on current heads
- run a deploy command after each safe serial merge
- open repair tasks for failed checks, conflicts, or closed PRs
Do not use this for code review quality findings; use /review. Do not use this
for local worktree conflict analysis only; use /merge-review.
Required Inputs
The steward can start from either source:
.planning/pr-readiness/*.mdreports generated bynode scripts/pr-ready.js- explicit GitHub PR URLs passed with
--enqueue-pr
If .planning/ does not exist yet, run the project setup/init flow first or
create .planning/pr-readiness/ before scanning. Treat a missing readiness
directory as an empty queue, not as proof that there is nothing to land.
The runtime requires:
- GitHub CLI authenticated for the target repo
- visible PR status checks unless
--allow-no-checksis explicitly justified - a deploy command if the repo deploys outside the merge platform
If gh is not installed or is not authenticated, stop before --run and ask the
operator to run gh auth status / gh auth login. Do not substitute raw tokens
or ad hoc curl commands inside the steward.
Invocation Forms
node scripts/deploy-steward.js --scan
node scripts/deploy-steward.js --scan --run
node scripts/deploy-steward.js --run --deploy-command "npm run deploy"
node scripts/deploy-steward.js --enqueue-pr https://github.com/OWNER/REPO/pull/123 --run
node scripts/deploy-steward.js --run --merge-mode merge-queueUse --dry-run before first live use on a repo:
node scripts/deploy-steward.js --scan --run --dry-runProtocol
Phase 1 - Build the Queue
Run:
node scripts/deploy-steward.js --scanThis reads .planning/pr-readiness, writes .planning/deploy-steward/queue.jsonl,
and records each candidate as ready, blocked, or already terminal.
For ad hoc PRs:
node scripts/deploy-steward.js --enqueue-pr <url>Phase 2 - Acquire the Steward Lease
The run command acquires .planning/deploy-steward/lease.lock and mirrors the
lease to .planning/deploy-steward/lease.json. If another steward has an active
lease, stop instead of racing main.
Use --force-lease only after confirming the old holder is dead.
Phase 3 - Process One Mainline Candidate at a Time
Run:
node scripts/deploy-steward.js --runFor each processable queue item, the steward:
- Refreshes live PR state with
gh pr view. - Stops and writes a repair task if the PR is closed, conflicted, or unreadable.
- Updates the branch against its base when GitHub reports it is behind.
- Waits when checks are pending.
- Opens a repair task when checks fail.
- Merges with
gh pr merge --<method> --match-head-commit <sha>when checks pass. - Runs the optional deploy command after a successful serial merge.
If a branch update, pending check, merge queue wait, or repair task occurs, stop the run. Rerun after the external state advances.
Show full SKILL.md (301 more words)Show less
Phase 4 - Deploy
For serial landing, pass the project deploy command:
node scripts/deploy-steward.js --run --deploy-command "npm run deploy"If the repo uses GitHub merge queue, prefer:
node scripts/deploy-steward.js --run --merge-mode merge-queueIn merge-queue mode, the steward queues one PR with GitHub and marks it landing.
Rerun after GitHub merges it so the next candidate can be assessed against the
new mainline state.
State Files
.planning/deploy-steward/queue.jsonl- durable landing queue.planning/deploy-steward/lease.json- active steward lease mirror.planning/deploy-steward/runs/latest.md- latest steward report.planning/intake/*deploy-steward*.md- generated repair tasks
Safety Rules
- Never let multiple steward runs merge into the same target at once.
- Never merge without a current PR refresh.
- Never merge a PR with failing or pending checks.
- Never merge a conflicted PR; create repair work instead.
- Never force-push a contributor branch from the steward.
- Use
--allow-no-checksonly when the repo truly has no CI. - Use
--require-fresh-readinesswhen local readiness reports must remain the source of truth; otherwise live GitHub checks are authoritative after branch refreshes.
Fringe Cases
- No
.planning/directory: stop setup and initialize Citadel state before writing queue or repair files. - No readiness reports: report an empty queue; accept explicit
--enqueue-prURLs if the operator wants to seed the queue manually. ghunavailable or unauthenticated: do not run; surface the authentication problem and keep the queue unchanged.- PR already merged: mark the queue item
landedand continue to the next candidate. - PR closed without merge: create a repair intake task and stop.
- Branch is behind base: update the PR branch, mark it waiting for checks, and stop until CI reruns.
- Checks fail: create a repair intake task and stop.
- Checks pending: keep the item queued and stop until the external state advances.
- Merge conflict or dirty merge state: create repair work; never merge or force-push from the steward.
Quality Gates
node scripts/test-deploy-steward.jsnode scripts/skill-lint.js deploy-stewardnode scripts/test-routing-sync.jsnode scripts/test-all.js
Exit Protocol
Return the steward report and a handoff:
---HANDOFF---
- Queue: <N> candidates in .planning/deploy-steward/queue.jsonl
- Last action: merged | updated-branch | waiting-for-checks | repair-needed | idle
- Report: .planning/deploy-steward/runs/latest.md
- Repair task: <path or none>
---© SethGammon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/deploy-steward of SethGammon/Citadel.
Open the folder on GitHubat commit e41ff1d
Compare with similar skills
Deploy Steward 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 |
|---|---|---|---|---|---|---|
| Deploy Steward this skillSethGammon/Citadel | 922 | — | ~1.7k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | 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
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.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
More from SethGammon/Citadel
All 48 skills in this repoCreate Skill
SethGammon/Citadel
Creates new skills from the user's repeating patterns. An agent skill from SethGammon/Citadel.
Houseclean
SethGammon/Citadel
Cross-drive storage audit and cleanup. An agent skill from SethGammon/Citadel.
Loop
SethGammon/Citadel
Bounded foreground repetition for the current session. An agent skill from SethGammon/Citadel.
Triage
SethGammon/Citadel
GitHub issue and PR investigator. An agent skill from SethGammon/Citadel.
Watch
SethGammon/Citadel
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills.
Archon
SethGammon/Citadel
Autonomous multi-session campaign agent. An agent skill from SethGammon/Citadel.
Related
Categories
Questions about Deploy Steward
What does Deploy Steward do?
Mainline deploy steward. An agent skill from SethGammon/Citadel. Deploy Steward is an agent skill from SethGammon/Citadel. Mainline deploy steward.
When should I use Deploy Steward?
Deploy Steward fits situations like: agent Workflows work in your project.
How do I install Deploy Steward in Claude Code?
Run `npx skills add SethGammon/Citadel --skill deploy-steward -a claude-code`. Or copy the skill folder (skills/deploy-steward in SethGammon/Citadel) into .claude/skills/deploy-steward in your project. Claude Code loads it when a task matches its description.
How do I install Deploy Steward in Codex?
Run `npx skills add SethGammon/Citadel --skill deploy-steward -a codex`. Or copy the skill folder (skills/deploy-steward in SethGammon/Citadel) into .agents/skills/deploy-steward in your project. Codex loads it when a task matches its description.
Can I use Deploy Steward 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 SethGammon/Citadel --skill deploy-steward -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-steward, .gemini/skills/deploy-steward, .github/skills/deploy-steward and .opencode/skills/deploy-steward in your project.
What does Deploy Steward need to run?
Going by SKILL.md and its folder, Deploy Steward needs the command-line tools its instructions call (node and gh).
Does Deploy Steward access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Deploy Steward 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 Deploy Steward use?
Deploy Steward is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deploy Steward use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deploy Steward?
Skills that share tags, products or a category with Deploy Steward: 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, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deploy Steward?
SethGammon (a GitHub user) maintains it in SethGammon/Citadel, which has 922 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 1, 2026.
Source: SethGammon/Citadel on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.