What happens next
Later sessions decide whether a staged skill stays. You are never asked: three raw counters settle it.
The counters
Section titled “The counters”Every session in which the skill loaded and its predicate matched is counted. In the example, the next session counted as:
matched 1 · recurrence 0 · harm 0| Counter | Goes up when |
|---|---|
| matched | a session’s repo, file types and task words matched the skill’s trigger |
| recurrence | the same kind of correction happened again while the skill was loaded |
| harm | a new cluster of tool errors, a takeover, or you disabled it, while it was loaded |
The outcomes
Section titled “The outcomes”| After | Status | What it means |
|---|---|---|
| 4 matched sessions, 0 recurrence, 0 harm | kept | copied into ~/.omp/agent/skills/; loads natively from then on |
| 2 recurrences or 2 harms | retired | archived with its evidence, never deleted, never loaded |
| 12 matched sessions without a decision | dormant | archived; returns when its trigger matches again |
So three more sessions like the example keep it. Two more corrections of the same kind retire it. The full rule set: counters and the kill criterion.
Watch it
Section titled “Watch it”rematch library ls --textEvery entry with its raw counts:
provisional skill foo [repo] matched 2 · recurrence 0 · harm 0The other views, and how to retire an entry, roll it back or turn rematch off, are in day to day.
Next: day to dayEverything optional you can do from here.
How it decidesThe loop, step by step.