charter — Claude Code skill: what it does, how to install
This Claude Code skill writes, revises, or reviews a charter that defines deliverables, boundaries, and success checks. It runs when work needs a written brief before an executor starts.
Apache-2.0 ★ 869 updated 2026-11-16
npx skills add sno-ai/sno-station-skills --skill charter -a claude-codeWhat charter does
The skill creates a Markdown file describing the expected outcome, out-of-scope work, and ways to verify completion. It reads existing project materials and decisions first, then asks only about unresolved choices that could change the result. Each check must make a pass or fail observable.
For review-only requests, it reports concrete mismatches and suggested minimal fixes in a separate file; it leaves the reviewed charter untouched. A scope change updates the related decisions and checks while preserving the rest. By default, an agent cannot release the charter on its own: it stays a draft until the owner approves it. Shell access and file read/write access are required.
What it helps with
- write a brief with clear deliverables and boundaries
- define checks with observable pass-or-fail outcomes
- spot mismatches between a charter and completed work
- revise related decisions and checks after a scope change
Example prompts for the agent
- Write a charter for this request using the existing project notes.
- Review this charter against the related work and put your findings in a separate file.
- Revise the charter for the changed scope while keeping unrelated decisions intact.
How to install charter
1Skills CLI (Vercel)
npx skills add sno-ai/sno-station-skills --skill charter -a claude-code2Manually: put the files in place
~/.claude/skills/charter/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/charter/
1Skills CLI (Vercel)
npx skills add sno-ai/sno-station-skills --skill charter -a codex2Manually: put the files in place
.agents/skills/charter/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sno-ai/sno-station-skills --skill charter -a cursor2Manually: put the files in place
.cursor/skills/charter/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sno-ai/sno-station-skills plugins/sno-station-standalone/skills/charter2Manually: put the files in place
.github/skills/charter/SKILL.md1Skills CLI (Vercel)
npx skills add sno-ai/sno-station-skills --skill charter -a gemini-cli2Platform CLI
gemini skills install https://github.com/sno-ai/sno-station-skills --path plugins/sno-station-standalone/skills/charterManually: put the files in place
.devin/skills/charter/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sno-ai/sno-station-skills --skill charter -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about charter
How do I install charter in Claude Code?
Run npx skills add sno-ai/sno-station-skills --skill charter -a claude-code. The skill file is located at ~/.claude/skills/charter/SKILL.md.
What does charter do?
It creates or revises a document that sets out the expected work, its boundaries, and checks for completion. It can also review a charter without editing the reviewed file.
Who releases a completed charter?
By default, the agent leaves it in draft until the owner approves it. After approval, its status becomes released, and its path goes to the executor or work supervisor.
Source text
SKILL.md · Apache-2.0
---
name: charter
description: "Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter."
requires:
programs: []
harness:
- {slot: 4.shell, need: required}
- {slot: 4.file-read-write, need: required}
---
# charter
A charter is one markdown file that says what to deliver and how everyone will know it was
delivered. A task is named by its charter
filename. `charter` writes it; `deliver` carries a released charter out. Any kind of project
uses it: software, documents, campaigns, research, operations. The owner is whoever owns the
work (often the user); speak to them in the language they use.
Prerequisites: none to use it; its selftest needs bash and python3.
Read `references/template.md` for the file layout and `references/questions.md` before asking
the owner anything.
## Rules that keep a charter useful
- Preserve the owner's words and decisions. Never invent a decision, a fact or a requirement.
A missing choice that would change the outcome is asked once, one question at a time, at the
end of a message; independent work continues while it waits, and silence is not approval.
- Read the existing work first (files, documents, data, earlier decisions). Ask nothing they
already answer.
- Every success check names what will be observed, where, and how, and can be answered pass or
fail by a real run or inspection. The expected result comes from the requirement or from
independent data, never from pasting the program's own output. For a defect, the check
reproduces the defect first.
- Before adding a precondition, check, section or approval step, name the failure it detects
and what would change if it failed. If nothing changes, leave it out. By default no checksums,
sign-off records, warm-up runs, baselines, fixed snapshots or report formats are entry
conditions.
- By default a security check, a full test suite or a full evaluation enters a charter only if
the owner names it. Propose it as a question that says what it would check and what it would
block; do not write it in as a requirement on your own judgment. A project may choose
otherwise.
- Say what happens on failure: which operation is logged with its error, what continues. A
record or report failure never disables the main result; a real failure stays a failure.
- Time is finite. A check that takes long states its expected duration from existing timings;
by default no full suites unless the owner asks.
- State what the executor may not do without the owner: publish, send to other people, spend,
delete, overturn a recorded decision.
## Write
1. Read the request, adjacent notes and the existing work. Cite settled decisions without
copying or locking their source. When the work depends on a third-party product, service or
version, read its current official documentation and record the facts that constrain the
work with the page and version.
2. Draft Owner decisions, Outcome, Scope and non-goals, and Success checks from the template.
Length follows the work: a few lines for a small task, a sliced charter (named slices, each
with its own checks) for a big one. There is one kind of charter, not sizes.
3. Read it as the executor: for each check, could someone tell pass from fail without asking?
Walk one real example through it. Fix the gaps that would make the result fail. Do not run
the future work to plan it.
4. One independent review for the owner's intent and concrete defects (`peer-review` when it
is installed, otherwise a second agent). Fix material findings; no second round unless the
owner asks.
5. Tell the owner what the charter will deliver and any genuine open decision, in plain
words, ending with the one question. After the owner approves, set `status: released` and
hand the path to the executor, or to whoever supervises the work.
By default an agent alone never releases a charter: it records the owner's decisions. When the
owner is away, leave the charter as a `draft` for them to release; a project may choose
otherwise.
## Revise
A scope change updates the affected decisions and checks in the same edit, sets `updated`, and
leaves the rest alone. A replaced charter gets `status: superseded` and a pointer to its
successor. Delivery records `delivered` only through `deliver`; never infer it from the header.
## Review only
Read the charter and the affected work. Report concrete mismatches, their consequences and the
smallest corrections in one local file; do not edit the reviewed charter. Questions go in the
conversation. Applying accepted corrections is Revise.
© sno-ai · Apache-2.0 · sno-ai/sno-station-skills