sno-ai/sno-station-skills / skills/T-delegation-and-work-orders/cos/skills/cos
cos
VerifiedMANUAL-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.
| File | Kind | Size |
|---|---|---|
| LEARNING.md | markdown | 6.1 KB |
| SKILL.md | skill md | 76.0 KB |
| references/card-template.md | markdown | 10.9 KB |
| references/digest-template.md | markdown | 4.9 KB |
| references/owner-profile.md | markdown | 5.3 KB |
| references/pocket-card.md | markdown | 1.6 KB |
| scripts/cos-claim.shexecutable | script | 31.4 KB |
| scripts/cos-claim.texecutable | script | 13.4 KB |
| scripts/cos-roster.shexecutable | script | 40.5 KB |
| scripts/cos-roster.texecutable | script | 7.6 KB |
| scripts/cos-screen.shexecutable | script | 4.8 KB |
| scripts/cos-screen.texecutable | script | 2.5 KB |
| scripts/cos-since.shexecutable | script | 3.6 KB |
| scripts/exec-sentinel.shexecutable | script | 6.1 KB |
| scripts/exec-sentinel.t | other | 2.4 KB |
| scripts/exec-tree-check.shexecutable | script | 2.6 KB |
| scripts/selftest/run-selftest.shexecutable | script | 204 B |
| scripts/selftest/text-check.py | script | 1.0 KB |
LEARNING.md
View on GitHub# COS Learning — management judgment only
**What lives here:** when to block, when to let run, how to shape a process.
**What never lives here:** bugs. A broken script, a wrong path, a protocol hole is fixed
where the code lives and it disappears. Writing it down instead leaves the bug *and* adds
a line nobody can act on. A bug is a bug: fix it now, never bank it as experience.
**Nor does law.** Where a rule is already written into a skill file, this file keeps the
**evidence** — what happened, what it cost — and points at the law rather than restating
it. A body that reproduces a section of `SKILL.md` is padding: it doubles the maintenance
and the copy goes stale silently.
**How it gets read** — storage is not reading, so three injection points, all load-bearing:
① the boot ritual reads the index; ② **every wake tick re-reads the index** (≤64 lines,
effectively free — this is what defeats stale-cache drift inside a long session);
③ **every outgoing card pastes the relevant lines inline**, because a PL will never open
this file.
**Therefore every index line must be executable standing alone.** The index is the only
text guaranteed to be re-read; a line that cannot be obeyed without opening its body has
failed, however elegant it reads. Bodies exist for the audit trail, not for the rule.
**How it grows** — `cos-evolve` owns the pen and holds the promotion ladder; it is not
repeated here. Three facts a *reader* needs.
**Entries are never deleted and never struck out.** What can happen is that an entry
**leaves the index**: once its rule is enforced by a check that cannot be bypassed, you no
longer need to remember it, so its line is retired and its body stays forever as the audit
trail. That is the only legal way to free a slot. The index is the working set; the bodies
are the archive.
**The index holds at most 64 lines**.
At 64 lines the re-read is roughly two thousand tokens a tick — cheap enough that machine
burden is not what the number is protecting. What it protects is the pressure to
mechanize: reaching the cap forces a retirement, and a retirement requires a real check.
**And at most 16 of them may run on prose alone** — an entry with no `**Enforced by**`
line. That is the limit that actually bites, because prose is what has demonstrably
failed: a rule written into this file does not survive contact with a plausible-looking
green state. The 17th does not get added; something gets mechanized first. This set should shrink, but **it will never
empty** — some of these are pure judgment, and inventing a check for judgment is machinery
for its own sake.
The index below is a starter set: index lines only, with no bodies, and exempt from both
caps until the first retirement. From then on both caps apply.
Shared by every COS instance for this user. This is the shipped seed; at run time the
working copy is `~/.local/state/cos/LEARNING.md`. Append under `flock`; never rewrite
wholesale.
**Entry shape**
```markdown
## <one-line claim, stated as a rule>
**Situation** — what was in front of the supervisor.
**What went wrong** — the decision actually taken, and its cost, with numbers.
**The rule now** — imperative, checkable. One or two sentences.
**Enforced by** — the script, required field, or numbered step. Omit until it exists.
**Hits** — one line each. Increment on every recurrence.
```
---
## Index
- [mail] · Delivery is the sender's — send rings the window; unabsorbed = failure, not slow reading
- [intervene] · Report a static alarm once with the action that clears it, then stop
- [intervene] · Give facts and the rule broken; the PL picks the fix — overrule in 3 cases only
- [intervene] · One role can have two live sessions — check ledger and process list before ruling
- [evidence] · Verify the load-bearing claim on disk yourself; never rule from a summary
- [evidence] · Never authorise N repairs off one measurement — measure the real rate first
- [evidence] · "Most cases undetermined" means audit the instrument, not condemn the product
- [evidence] · Report the number; name the fact that would settle its cause, never guess it
- [docs] · Fix the stale document first, then card the agent with the evidence
- [authority] · An artifact a journey wrote cannot authorize it — check the author before the size
- [authority] · If the main loop won't run without it, it is the next dispatch, never a debt row
- [schedule] · Order anything that freezes, hashes or measures a file after everything that edits it
- [schedule] · Settled small work prices several times too high — discount it; never order the estimator to shrink
- [run] · Read the first minutes yourself; on the first red root-cause now, and cap any continue
- [run] · No relaunch of an expensive run without a named delta — canary first, full run as the gate
- [owner] · No repo, charter filename, and what changes either way → the question does not get asked
- [owner] · Close with the next step priced and its check planned — their cost must be one word
- [close] · Every close: too little, too much, never stopped, wrong repo — three of four look green
- [close] · Drain the inbox before a seal; dispose the window only once the charter itself is done
- [process] · Catching yourself noticing instead of acting proves a machine check is missing
- [alive] · No turn lock = no turn (Codex on Linux with systemd; otherwise judge by the seat and inbox), so ring it; a heartbeat armed is still not a turn started or work done
- [intervene] · Read the journey's decision thread before any deletion alarm — no exception
- [timing] · After launch send only stop-the-bleeding; buffer the rest, ride their next card
- [authority] · Confirm a new KIND of work; never the next step of work already ordered
- [feed] · Parked is not a state — re-task against what the blocker actually forbids
- [evidence] · A described next step is not a started one — demand its on-disk start proof
- [evidence] · Never hand-write a liveness or did-it-move check — cos-roster.sh and cos-since.sh only
- [authority] · A general owner go-ahead never clears a row blocked on a specific question — re-ask in one line
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |