- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill charter -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill charter -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill charter -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sno-ai/sno-station-skills --skill charter -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/sno-ai/sno-station-skills/tree/HEAD/plugins/sno-station-standalone/skills/charterFrom the publisher
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.
peer-review when it
is installed, otherwise a second agent). Fix material findings; no second round unless the
owner asks.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.
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.
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.
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 w
---name: charterdescription: Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of…---# plugins/sno-station-standalone/skills/charter/SKILL.mdOverview
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.
FAQ
Download plugins/sno-station-standalone/skills/charter/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/sno-ai/sno-station-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.