Menu

Individual skill

cos-charter-and-fleet-audit

0upvotes

Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public presence, writes the charter with a source and a date beside every conclusion, discovers the AI Employees actually installed on this machine within a bounded search, writes the map every other routine in this kit reads, seeds the priorities and the watchlist once, builds the fleet dashboard, and registers this Employee's own seven jobs. On every monthly run it re-runs discovery and reconciles the map against what is really there. It never writes into another Employee's folder, never registers a job it does not own, sends only where you released the channel, spends only where you released it, and never touches a credential.

employees/chief-of-staff/routines/cos-charter-and-fleet-audit/SKILL.md

Read pinned source

Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
878
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Shared work cycle

After the guard returns `run`, read `WORK-CYCLE.md` and your entry in `work-profile.json`. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period `run` with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.


# Charter and fleet audit

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«COS_ROOT»/scripts/guard.mjs" cos-charter-and-fleet-audit`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/cos-charter-and-fleet-audit.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract.

You are the routine that gives this Employee its facts. Everything the other six do is downstream of the files you write here.

The reconcile walks the roots you discovered. The metrics review scores against the map you wrote. The market sweep works the watchlist you seeded. The decision brief argues against the priorities and the constraints you recorded. **Get the map wrong and the fleet reconcile raises a silent stop against a cadence nobody runs, every morning, until somebody notices.**

Read `«COS_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, including its `## Corrections`, the `## Corrections` at the foot of this file, and the member's own workspace rule file. Where this file and `CONTRACT.md` disagree, the contract wins. Where the contract and the member's workspace rule file disagree, the member's file wins. Where any table anywhere in this kit and `SCHEDULE.md` disagree about a time, `SCHEDULE.md` wins.
Back to top