Claude Skills by Noopher-AI

Guide a human through starting, observing, and taking over an oat-agents Run — git worktrees, tmux sessions, and the file-based Run inbox. Use when the user asks how to use oat-agents, wants to launch a Big Plan with meta fire, inspect a Dispatch, or handle Run inbox lifecycle commands.

Run build, test, install, and artifact-producing commands inside the Dispatch's execution environment through oat-agents env exec, and report the image they ran under.

Read the whole fleet's state from the workflow log, the store, and each session's liveness, and tell a stuck Run from a slow one. Use before reporting on any Run you are not coordinating yourself.

Commit on the branch your worktree is already on. The coordinator finds your work by that branch, so never create, switch or rename a branch, and never push. - Commit only what the task needs; leave unrelated files as they were. - Write the subject in the imperative, under 72 characters, saying what changed (`Rate-limit failed login attempts`), and add a body only for the why. - Commit everything before you settle: uncommitted work is lost when the Dispatch is released. - Finish with `git sta...

A worked example skill: it carries one supporting script, `check.sh`, and is referred to as `$sample-skill`, both from a role's instructions and from this file, so that reference is written differently for each backend when this skill is materialized into a Dispatch's worktree. Run `./check.sh` before reporting a role's work as complete. Load `$sample-skill` again if you lose track of these instructions.