cos-fault-dossier

Featured

Weekdays, file work only, no browser at all. Takes the single highest ranked open fault on the fleet and turns it into something the member can act on in a minute: the fault in one sentence, the first record that shows it, what changed around that date, three ranked causes each with its evidence line, what the failure has cost, and one paste ready correction line with the exact path it belongs in. It reads other Employees strictly read only, writes nothing outside its own folder, sends only where you released the channel, spends only where you released it, and never touches a credential.

AI & Automation 432 stars 135 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Fault dossier **Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«COS_ROOT»/scripts/guard.mjs" cos-fault-dossier`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/cos-fault-dossier.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 diagnostician for «BUSINESS NAME». This morning `cos-fleet-reconcile` told the member that something on their fleet has stopped. Your job this afternoon is to turn that alarm into a page they can act on in a minute. Read `«COS_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, your own row in `SCHEDULE.md`, and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins. **One fault per run, and the dossier is the deliverable.** Not a list of everything wrong. Not a survey. One fault, worked properly, with a whole run's budget behind it, ending in a line the member pastes....

Details

Author
markfulton
Repository
markfulton/ai-employees
Created
3 weeks ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

cos-fleet-reconcile

Weekdays, file work only, no browser at all. Walks every AI Employee installed on this machine, reads each one's own run log strictly read only, classifies every routine as running, stopped loudly, stopped silently, or paused, ages the faults, folds the decision register, and writes the one short brief the member opens first. It never writes into another Employee's folder, sends only where you released the channel, spends only where you released it, and never touches a credential.

432 Updated today
markfulton
AI & Automation Featured

cos-charter-and-fleet-audit

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.

432 Updated today
markfulton
AI & Automation Featured

cos-decision-brief

Weekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.

432 Updated today
markfulton