Agent skill

Autopilot

Intake-to-delivery pipeline. An agent skill from SethGammon/Citadel.

MITAuto-check passedTesting & QA

Install Autopilot

skills CLI

$ npx skills add SethGammon/Citadel --skill autopilot -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install SethGammon/Citadel autopilot --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/autopilot .claude/skills/autopilot && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "autopilot" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/autopilot into .claude/skills/autopilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autopilot", 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

$skill-installer install https://github.com/SethGammon/Citadel/tree/main/skills/autopilot

Type 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.

skills CLI

$ npx skills add SethGammon/Citadel --skill autopilot -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install SethGammon/Citadel autopilot --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/autopilot .agents/skills/autopilot && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "autopilot" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/autopilot into .agents/skills/autopilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autopilot", 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.

skills CLI

$ npx skills add SethGammon/Citadel --skill autopilot -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install SethGammon/Citadel autopilot --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/autopilot .cursor/skills/autopilot && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "autopilot" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/autopilot into .cursor/skills/autopilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autopilot", 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

$ gemini skills install https://github.com/SethGammon/Citadel.git --path skills/autopilot

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add SethGammon/Citadel --skill autopilot -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install SethGammon/Citadel autopilot --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/autopilot .gemini/skills/autopilot && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "autopilot" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/autopilot into .gemini/skills/autopilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autopilot", 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.

GitHub CLI

$ gh skill install SethGammon/Citadel autopilot

Installs 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).

skills CLI

$ npx skills add SethGammon/Citadel --skill autopilot -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/autopilot .github/skills/autopilot && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "autopilot" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/autopilot into .github/skills/autopilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autopilot", 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.

skills CLI

$ npx skills add SethGammon/Citadel --skill autopilot -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install SethGammon/Citadel autopilot --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SethGammon/Citadel.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/autopilot .opencode/skills/autopilot && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "autopilot" agent skill from https://github.com/SethGammon/Citadel/tree/main/skills/autopilot into .opencode/skills/autopilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "autopilot", 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: autopilot
GitHub stars: 922
Token cost: ~1.3k tokens
SKILL.md length: 550 words
Files: 3
Skills in repo: 48
Repo updated: Oct 1, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Intake-to-delivery pipeline. An agent skill from SethGammon/Citadel.

Works in 5 steps: DELIVERY PREFLIGHT → SCAN → BRIEF (for pending items) → …
Testing & QA work in your project
SKILL.md covers Orientation, Protocol, Intake Item Format and Fringe Cases, plus 3 more sections
Calls node; reaches github.com

What it does

Autopilot is an agent skill from SethGammon/Citadel. Intake-to-delivery pipeline. Processes pending items from .planning/intake/: briefs new ideas, executes approved work through research → plan → build → verify. Drop a file in .planning/intake/ and invoke this skill.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `__benchmarks__/briefed-item-build.md` and `__benchmarks__/empty-intake.md`).

It sits in Testing & QA. 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

Testing & QA work in your project

Example prompts

“/autopilot”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

DELIVERY PREFLIGHT
SCAN
BRIEF (for pending items)
BUILD (for briefed/approved items)
REPORT

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:
- node
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

Autopilot loads about 1.3k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 550 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~56
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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). 550 words, ~1,257 tokens.

Download SKILL.mdSave it as .claude/skills/autopilot/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: autopilot
description: Intake-to-delivery pipeline. Processes pending items from .planning/intake/: briefs new ideas, executes approved work through research → plan → build → verify. Drop a file in .planning/intake/ and invoke this skill.
license: MIT
user-invocable: true
auto-trigger: false
trigger_keywords: intake, process pending, pipeline
last-updated: 2026-03-20

/autopilot — Intake Pipeline

Orientation

Use Autopilot when:

There are pending items in .planning/intake/
You want to process intake items without manual orchestration
The work is scoped and well-defined (Small or Medium complexity)

Do NOT use Autopilot for:

Large, multi-session campaigns (use Archon)
Parallel execution (use Fleet)
Exploratory or open-ended work (use Marshal)

Protocol

Step 0: DELIVERY PREFLIGHT

When the user names a specific intake file or asks for "intake to PR", prefer the deterministic delivery preflight before freeform build work:

bash

node scripts/deliver.js --intake .planning/intake/{item}.md

If no specific intake file is named, use:

node scripts/deliver.js --next

This selects the highest-priority pending item in .planning/intake/ and keeps the golden path deterministic.

This creates an active campaign with claimed scope, acceptance criteria, map context, and exit evidence rows, then marks the intake item in-progress. Continue from the created campaign with /do continue.

After build and verification, package the delivery before marking the campaign complete:

bash

node scripts/package-delivery.js {campaign-slug}

If a PR exists, record the PR as the review target:

bash

node scripts/package-delivery.js {campaign-slug} --pr https://github.com/{owner}/{repo}/pull/{number}

Step 1: SCAN

Read all files in .planning/intake/ and identify:

status: pending → needs briefing
status: briefed → ready to build
status: approved → ready to build
status: in-progress → check if stuck

Step 2: BRIEF (for pending items)

For each pending item:

Read the intake file
Read related files mentioned in the description
Research the scope: what files exist, what patterns are established
Write the brief:
- Scope: Small / Medium / Large
- Approach: How to implement (2-3 sentences)
- Files: Which files to create or modify
- Quality gates: What must be true when done
- Risks: What could go wrong
Update the item's status to briefed

Step 3: BUILD (for briefed/approved items)

For each briefed item (smallest first):

Read the brief
Execute the approach:
- Create or modify the listed files
- Follow the project's conventions (CLAUDE.md)
- Run typecheck after each change
Verify:
- All quality gates pass
- Typecheck clean
- Tests pass (if applicable)
Update status to completed

Step 4: REPORT

Output a summary of what was processed:

Autopilot processed {N} items:
  ✓ {item-1}: briefed → built → verified
  ✓ {item-2}: briefed
  ✗ {item-3}: blocked — {reason}

Intake Item Format

markdown

---
title: "Feature Name"
status: pending | briefed | approved | in-progress | completed
priority: normal | high
target: src/path/to/affected/area/
---

Description of what needs to be done...

Show full SKILL.md (225 more words)Show less

Fringe Cases

.planning/intake/ is empty or does not exist: Output "Nothing to process — .planning/intake/ is empty. Drop a file there or run /do setup to initialize." Do not error.
Intake item has no clear action: If the description is too vague to execute, ask the user one clarifying question or skip the item with a note: "Skipped — direction unclear. Update the intake file and re-run."
Item status is unrecognized: Treat unknown statuses as pending and proceed through the brief → build flow.
Typecheck fails during build: Record the failure in the item's status, move on to the next item, and report the blocker in the exit summary.
.planning/ does not exist: Output a setup hint and exit cleanly. Autopilot requires .planning/intake/ to operate — if the directory is absent, treat as empty intake and suggest running /do setup.

Contextual Gates

Disclosure: "Processing intake queue: N items pending. Will dispatch skills per item." Reversibility: amber — processes intake items by dispatching other skills that may modify files; undo depends on dispatched skills Trust gates:

Any: review intake and briefing.
Familiar (5+ sessions): autopilot runs autonomously on queued items; novices should review intake before running.

Quality Gates

Never build without reading CLAUDE.md first
Run typecheck after every file change
Mark items as completed only when verification passes
If an item is blocked, record the reason and move on

Exit Protocol

---HANDOFF---
- Processed {N} intake items
- Built: {list of completed items}
- Blocked: {list with reasons}
- Remaining: {count of items still pending}
---

Files

SKILL.md and 2 other files in skills/autopilot of SethGammon/Citadel.

SKILL.md
__benchmarks__/briefed-item-build.md
__benchmarks__/empty-intake.md

Open the folder on GitHubat commit e41ff1d

Compare with similar skills

Autopilot 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.

Autopilot compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Autopilot this skillSethGammon/Citadel	922	—	~1.3k	Automated safety check: Pass	MIT	7 days ago
OpenHarness End-to-End EvalsHKUDS/OpenHarness	16k	1 repos	~2.1k	Automated safety check: Notes	MIT	4 mo ago
Clawteam DevHKUDS/ClawTeam	5.5k	1 repos	~1.1k	Automated safety check: Pass	MIT	5 mo ago
Acceptance Evidence for Deliverieslobehub/lobehub	83k	—	~9.7k	Automated safety check: Pass	Apache-2.0	today
Qwen Code E2E TestingQwenLM/qwen-code	28k	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
Skill Testdatabricks-solutions/ai-dev-kit	1.9k	—	~1.9k	Automated safety check: Pass	Custom licence	1 mo ago

Similar skills

OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
16k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check: notes
Clawteam Dev
HKUDS/ClawTeam
A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…
5.5k GitHub starsUsed in 1 repo~1.1k tokens
Testing & QAAuto-check passed
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
83k GitHub stars~9.7k tokensUpdated today
Testing & QAAuto-check passed
Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
28k GitHub stars~2.1k tokensUpdated today
Testing & QAAuto-check passed
Skill Test
databricks-solutions/ai-dev-kit
Testing framework for evaluating Databricks skills. An agent skill from databricks-solutions/ai-dev-kit.
1.9k GitHub stars~1.9k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Adding LLM MCP Tools
TriliumNext/Trilium
A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…
38k GitHub stars~2.5k tokensUpdated today
Testing & QAAuto-check passed

Questions about Autopilot

What does Autopilot do?

Intake-to-delivery pipeline. An agent skill from SethGammon/Citadel. Autopilot is an agent skill from SethGammon/Citadel. Intake-to-delivery pipeline.

When should I use Autopilot?

Autopilot fits situations like: testing & QA work in your project.

How do I install Autopilot in Claude Code?

Run `npx skills add SethGammon/Citadel --skill autopilot -a claude-code`. Or copy the skill folder (skills/autopilot in SethGammon/Citadel) into .claude/skills/autopilot in your project. Claude Code loads it when a task matches its description.

How do I install Autopilot in Codex?

Run `npx skills add SethGammon/Citadel --skill autopilot -a codex`. Or copy the skill folder (skills/autopilot in SethGammon/Citadel) into .agents/skills/autopilot in your project. Codex loads it when a task matches its description.

Can I use Autopilot 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 autopilot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/autopilot, .gemini/skills/autopilot, .github/skills/autopilot and .opencode/skills/autopilot in your project.

What does Autopilot need to run?

Going by SKILL.md and its folder, Autopilot needs the command-line tools its instructions call (node).

Does Autopilot 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 Autopilot 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 Autopilot use?

Autopilot 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 Autopilot use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Autopilot?

Skills that share tags, products or a category with Autopilot: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Clawteam Dev (HKUDS/ClawTeam, 5.5k stars), Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars) and Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Autopilot?

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.

Install Autopilot

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/autopilot — Intake Pipeline

Orientation

Protocol

Step 0: DELIVERY PREFLIGHT

Step 1: SCAN

Step 2: BRIEF (for pending items)

Step 3: BUILD (for briefed/approved items)

Step 4: REPORT

Intake Item Format

Fringe Cases

Contextual Gates

Quality Gates

Exit Protocol

Files

Compare with similar skills

Similar skills

More from SethGammon/Citadel

Related

Questions about Autopilot