sno-station-skills
sno-ai · sno-ai/sno-station-skills
A collection of skills for Claude Code to enable cross-agent reviews, shared memory, and automatic handoffs.
Sno Station Skills: 31 tested skills that turn Claude Code and Codex into one working team. Cross-vendor peer review, automatic handoff when an agent hits its quota, a one-page morning brief, work orders with proof, and a nightly loop that learns from your own sessions. Open source, installed with one sno setup.
Preview
What you can do with it
- Request a peer review of your code from a different LLM vendor automatically
- Continue a task seamlessly when one agent hits its rate limit using shared memory
- Generate a morning brief of what your agents 'learned' or improved overnight
Safety check
Usable, but read the notes first.
- ●Installer downloads a remote script and pipes it to the shell.
README.md
Automated scan of the repo files. Always review code you run.
From the README
Sno Station Skills — The working habits of a real team, installed into your AI agents.
Install
All skills with Sno Station
Copy this prompt into your agent's chat:
Install sno.ai from GitHub.
This installs Sno Station and sets up all 37 skills, plus the programs they call, for the supported agents it finds on your machine.
Or paste this command into your terminal:
sh -c 'sno_installer_body=$(curl -fsSL https://sno.ai/install) && printf "%s\n" "$sno_installer_body" | sh'
Already have Sno Station? Run sno setup to install the skills into your agents.
Run it again if you add another agent later.
Install one skill
Use the copy button on either prompt below, then paste it into your agent's chat. Your agent finds and installs the skill; you do not need to download or copy files yourself.
peer-review checks code, plans and documents with a reviewer from another model vendor.
It needs Sno Station programs and a logged-in reviewer. The prompt checks those dependencies first.
Install only the peer-review skill from https://github.com/sno-ai/sno-station-skills
for this project, including its scripts and references.
Check its dependencies and tell me what is missing before installing anything else.
less-is-more helps your agent write less code and remove unnecessary complexity.
It can run without Sno Station.
Install only the less-is-more skill from https://github.com/sno-ai/sno-station-skills
for this project, including its scripts and references.
Supported agents for Sno Station: Claude Code, Codex, OpenClaw and Hermes Agent. Each skill declares what it needs from the agent. Setup uses that declaration to install it fully, install it in a reduced form, or skip it when the agent cannot run it.
Updates come by themselves: sno updates itself when it finds a newer release. The full
command list is in Sno Station's command reference.
Install as a plugin
Claude Code:
claude plugin marketplace add sno-ai/sno-station-skills
claude plugin install sno-station@sno-ai
Codex:
codex plugin marketplace add sno-ai/sno-station-skills
codex plugin add sno-station@sno-ai
sno-station holds all 37 skills; most of them call Sno Station programs, so install Sno Station too.
For only the 7 skills that run without Sno Station, install sno-station-standalone@sno-ai instead.
Install · What changes for you · Why these skills · The pain, and what fixes it · Stories from our own machine · The skills · Built to be trusted · For skill authors · License
What changes for you
You keep working exactly as before, in whichever agent you like. Then:
- You finish a change and want it checked. Say "peer-review this". A reviewer from the other vendor reads it cold, reports what would break in real use, and the author fixes the root cause, round after round, until the review comes back clean.
- You start a long run before bed. Say "arm rotate-agent". If the working agent's quota drops to the threshold overnight, it hands the task to a fresh agent from the other vendor, with the brief verified before a single file is touched.
- You come back. Say "away brief". One page, at most 60 lines: what got done, what is stuck and why, what waits for your answer, and what it cost in quota.
- You have a job for someone else. Say "write a charter". You get one file that says what
to deliver, what is out of bounds, what you already decided, and how each success check will
be proven. Any agent can then
deliverit, and every check is proven by a recorded real run. - Every night, the team looks back. The nightly loop reads the day's Claude Code and Codex
sessions, finds the mistakes that repeat, and proposes lessons and skill changes. In the
morning you accept the ones you like with
sno rem-reflect accept <id>. Nothing changes without that accept.
Why these skills
One AI agent is a brilliant new hire with no colleagues. It reviews its own work, so it misses what it cannot see. It stops dead when its quota runs out, at 3 a.m., halfway through your build. It says "done" when the tests are green and nothing actually happened. It builds three layers of machinery you never asked for. And tomorrow it makes the same mistake it made today, because nobody told it otherwise.
Sno Station Skills fixes the team, not the model. These are the skills Sno Station installs into the agents you already run. They give Claude Code and Codex the habits every good engineering team has: a second pair of eyes from a different vendor, a clean handover when someone has to leave, a lead who hands out work with a written definition of done, a one-page brief when you come back, and a retrospective every night that turns this week's mistakes into next week's rules.
Dual Brain: different roles, one team. One agent carries out your task. The other reviews the result against your requirements. Claude Code and Codex can take either role. When both CLIs are installed, the review runs in the other vendor's CLI, in a fresh session with none of the author's conversation. The agents exchange findings and corrections. Add more roles, and you have an Agent Squad.
Work that finishes while you sleep. Arm it before bed, and when the working agent's subscription runs low it writes a handover brief while it still can, wakes an agent from the other vendor, and hands the task over with the exact commit to continue from. Your build does not care which vendor finished it.
"Done" means proven. Every task can carry a written list of success checks, each one answered pass or fail by a