What you can do with Sno Station Skills

5 use cases

• Get a cold second review from the other vendor's agent

  Have a fresh agent from the other vendor check your change before it lands.

  • Sno Station Skills
  • Claude Code
  • Codex
  • Software and DevOps
  • Intermediate
  View prompt

  In the repo <repo-path>, use the peer-review skill from Sno Station Skills on the latest uncommitted change, preferring the other vendor's CLI in a fresh session. Output the findings list with each finding's trigger, impact and refutation attempt. Verify that the first line of the report states whether the review was same-vendor.

  Share Save

• Keep an overnight build going when one agent runs out of quota

  Arm a handover so a second vendor's agent continues the task from the exact commit.

  • Sno Station Skills
  • Claude Code
  • Codex
  • Software and DevOps
  • Advanced
  View prompt

  In the repo <repo-path>, arm the rotate-agent skill from Sno Station Skills so that the task in <task-file> hands over to the other vendor's agent when quota reaches the threshold. Output the handover brief and the commit to continue from. Verify that the receiving agent confirmed the brief before touching any file.

  Share Save

• Read a one-page brief when you come back to the desk

  Get one page of what got done, what is stuck, and what waits for your answer.

  • Sno Station Skills
  • Claude Code
  • Codex
  • Software and DevOps
  • Intermediate
  View prompt

  In the repo <repo-path>, produce an away brief with the away brief skill from Sno Station Skills covering the last <time-window> of agent activity. Output at most 60 lines with done, stuck, waiting-for-you and quota-cost sections. Verify that every stuck item names a reason.

  Share Save

• Hand off a job with a charter that defines done

  Write one charter with success checks, then let any agent deliver it.

  • Sno Station Skills
  • Claude Code
  • Codex
  • Software and DevOps
  • Intermediate
  View prompt

  In the repo <repo-path>, write a charter with the work-orders skill from Sno Station Skills for the job described in <job-description>. Output one charter file with deliverables, out-of-bounds areas, decided items and a proof method for each success check. Verify that every success check names a real run that can pass or fail.

  Share Save

• Review nightly lessons from your own sessions before they stick

  Let the nightly loop propose lessons and skill changes, and accept only the ones you want.

  • Sno Station Skills
  • Claude Code
  • Codex
  • Software and DevOps
  • Intermediate
  View prompt

  In the repo <repo-path>, run the rem-reflect skill from Sno Station Skills over the last <day-count> days of Claude Code and Codex sessions. Output a list of proposed lessons and skill changes, each with the session evidence. Verify that no change is applied until it is explicitly accepted.

  Share Save

How to use Sno Station Skills

1. Check you have what it needs: A shell and curl on the machine; Claude Code or Codex already installed; Optional: both Claude Code and Codex CLIs, so peer review can use the other vendor.
2. Open sno-ai/sno-station-skills on GitHub and read the README and license.
3. Install the skills with sh -c 'sno_installer_body=$(curl -fsSL https://sno.ai/install) && printf "%s\n" "$sno_installer_body" | sh'
4. If you add another agent later, run sno setup to connect it.
5. In your agent, finish a change and say "peer-review this".
6. Read the findings. The author fixes root causes and the review repeats until it is clean.

These steps come from our top use case, Get a cold second review from the other vendor's agent, which also has a copy-paste agent prompt.

Sno Station Skills alternatives · Best AI repos for Software and DevOps

About this repo

• Who it is forDevelopers and engineering leads who already run Claude Code or Codex and want the agents to work as a team with review, handoff and proof of done.
• Why it is hot
• LanguageShell
• Sourcegithub.com/sno-ai/sno-station-skills · Back to Hot repos

Requirements

• A shell and curl on the machine
• Claude Code or Codex already installed
• Optional: both Claude Code and Codex CLIs, so peer review can use the other vendor

Related repos

• #1 this week Harness2 Harness² is a Python framework from Google Research that refines the harness around a fixed model (prompts, tools, memory, skills, orchestration) so it performs better on agent tasks.
• #8 this week iFixAi iFixAi is an open-source Python tool that audits whether an AI agent is doing the job it is supposed to do, using 60 inspections that combine red-teaming with operational checks.
• #9 this week Orca Orca is a desktop app, with a mobile companion, for running several CLI coding agents side by side, each in its own git worktree, and tracking them in one place.