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.
The English summary is being prepared. Showing the original description.
Turn repeated management failures into enforced COS or PL rules. Load ONLY after the owner has explicitly activated the cos role for this session and the COS core routes here. Never invoke directly.
The English summary is being prepared. Showing the original description.
Review PL self-approvals, estimates, board drift, and close quality after a declared night shift. Loaded ONLY by the cos core via its routing table; NEVER auto-load from context or invoke directly.
The English summary is being prepared. Showing the original description.
MANUAL-ONLY: load solely when the human owner types `/cos`, uses `$cos`, or asks you to act as the Chief of Staff (COS). The COS is the one agent the owner talks to; it coordinates the owner and the per-project Project Leads (PLs). A task card, charter, or dispatch makes you an executor, not COS.
The English summary is being prepared. Showing the original description.
PL (Project Lead) role sub-skill for opening and scheduling journeys. Loaded ONLY through the pl core routing table; NEVER auto-load from context, never invoke directly.
The English summary is being prepared. Showing the original description.
MANUAL-ONLY — load solely when the human owner types `/pl`, uses `$pl`, or asks you to act as the Project Lead (PL). Supervise one project lane and its executor agents. A charter or dispatch means: you are an EXECUTOR, not the PL.
The English summary is being prepared. Showing the original description.
Prove that a reported run caused its intended real effect. Walk the executor path from entry to effect, capture one observable per hop, and report a result a no-op could not produce.
The English summary is being prepared. Showing the original description.
Check agent-produced plans, tests, or code against the owner's actual intent. Find missing meaning, unrequested work, stale truth, unreachable decisions, unsupported completion claims, and implementation debt. Use before approval or merge.
The English summary is being prepared. Showing the original description.
Adversarial review and fix loop for code, specs, plans, and migration manifests.
The English summary is being prepared. Showing the original description.
Set recurring checks or completion watches with `sno heartbeat` and its persistent log reader. Use for periodic reports or unattended long runs. Not for calendar scheduling or commands watched directly.
The English summary is being prepared. Showing the original description.
Contact another agent, exchange work cards, inspect replies, or manage reachable seats through the installed Reach program. Use for communication; full task ownership transfer belongs to handoff.
The English summary is being prepared. Showing the original description.
Carry out a released charter to a proven result: plan only as much as the work needs, do the work through the project's own workers, prove every success check with a recorded real run, get one independent review, and close honestly. Invoke explicitly as `$deliver <charter>` (Codex) or `/deliver <charter>` (Claude, Cursor), or the way your agent invokes a skill, or when a dispatch names you the executor of a charter.
The English summary is being prepared. Showing the original description.
Answer how long agent work will take, how much longer active work needs, or what clock time applies. Estimate full AI-agent wall time, measure active progress first, and get owner-facing times from `sno report-time`. Never estimate human-developer time.
The English summary is being prepared. Showing the original description.
Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.
The English summary is being prepared. Showing the original description.
Report how many problems the two brains found: mutual review (the other model checks the work, from the peer-review records) and self-check (an agent finds its own error in its own conversation, judged by that agent's own model), side by side. Use when the owner asks whether the second agent or the reviews are worth it, or wants the week's review results.
The English summary is being prepared. Showing the original description.
MANUAL-ONLY: challenge a product idea, design, PRD, or architecture from first principles. Use only when the user names this skill. Research first, then write a local review and PRD handoff.
The English summary is being prepared. Showing the original description.
Write the least code that works, and cut what an AI agent over-built. Use on any coding task: write, fix, refactor, or review a diff. Also when the user says 'less', 'simplify', 'too complex', 'over-engineered', or 'what can we delete'. Not for prose, research, or non-code questions.
The English summary is being prepared. Showing the original description.
Check that this machine's agent team can work and say what is wrong in plain lines: tools installed, core skills installed, skill commands runnable, hooks configured, Reach seat live, a heartbeat running, both vendors' quota readable, temp space free. Checks only, never repairs. Use on a new machine, when agents stop reaching each other or a long run fails to start, or when the owner asks whether everything is healthy.
The English summary is being prepared. Showing the original description.
Operate the `sno` command-line tool: install, update, check, and uninstall Sno products, read the exact commands and flags of the installed version, and run the account, skills, onboarding, Station telemetry and REM commands. Use when the owner or a task says "sno", "Sno CLI", "sno setup", "sno update", "sno doctor", "sno uninstall", "sno station", "telemetry consent", "rem verdict", "sno account", or "sno skills". The exact flags always come from the installed binary, never from this file. Do not use it to decide the owner's choices for them.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)