ooda-loop
Skill133 starsChanged 7 days agoMITView on GitHub
OODA loop for website performance, scalability, cost, errors, and outages: Observe, Orient, Decide (pause for approval), Act, verify, repeat. Use for ooda-loop, incidents, latency, throughput, capacity, or cloud spend.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- deciqAI/knowledge-skillstheir own version, first seen Jul 7, 2026
- jackjin1997/ClawForgetheir own version, first seen May 25, 2026
- itzcull/thinking-skillstheir own version, first seen May 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- deciqAI/knowledge-skills★ 13same name
- jackjin1997/ClawForge★ 12same name
- itzcull/thinking-skills★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Observe, Orient, and Decide are read-only: No edits, deploys, restarts, scaling, or config/flag changes until Act, and only after the user …
- Distinctive: line 14
Before starting, pin one measurable objective the user owns (e.g.
- Very specific: line 20
Data gate: if you can't read live or exported signals, stop and ask for access by name: MCP/API/CLI for cloud systems, logs/tracing for …
- Distinctive: line 42
Stop and wait for explicit approval: If rejected, re-Orient or re-Decide.
- Distinctive: line 46
Do only the approved action.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OODA loop: website systems
Loop Observe → Orient → Decide → (pause) → Act → Observe until the objective is met or the user stops. Never skip a phase.
Observe, Orient, and Decide are read-only. No edits, deploys, restarts, scaling, or config/flag changes until Act, and only after the user approves. Anything that adds load or changes runtime state (load tests, cache warming, toggling debug logging or sampling) counts as an Act.
Objective
Before starting, pin one measurable objective the user owns (e.g. "p95 < 300 ms on /checkout", "cut infra cost 20% without SLO breach", "restore service"). If unclear, ask once.
1. Observe
Collect real, dated, sourced data covering the objective: latency, errors, saturation, traffic, queue depth, spend, alerts, traces, recent changes. Use MCPs, vendor CLIs/APIs, observability tools, or local logs. Never invent numbers; docs and architecture reasoning alone don't count.
Data gate: if you can't read live or exported signals, stop and ask for access by name: MCP/API/CLI for cloud systems, logs/tracing for local ones.
2. Orient
Summarize, separating fact, inference, and unknown:
- What is true now vs. the healthy/expected state
- What changed (deploy, traffic, config, dependency)
- Constraints (SLOs, budget, freeze windows, severity)
- Blind spots
- The dominant constraint: latency, errors, capacity, or cost
3. Decide, then pause
Propose one action, preferring the smallest reversible experiment that tests the Orient picture:
- Action
- Hypothesis: which metric improves, by how much
- Invalidation: what result means abort
- Risk / rollback
- Tradeoffs across perf, scale, cost, and reliability
Stop and wait for explicit approval. If rejected, re-Orient or re-Decide. Incidents pause too, unless the user already authorized a specific mitigation.
4. Act
Do only the approved action. Capture before/after on the Decide metrics, judge the outcome (good, mixed, bad) against the hypothesis, and note side effects. If invalidation trips, roll back and return to Observe; don't chain Acts.
Loop
- Objective met: stop; report outcome and residual risk
- Otherwise: Observe again with post-Act data, then Orient and Decide (pause)
- Blind spot blocked learning: close the measurement gap before any new Act
Report (each cycle)
## OODA cycle N: [objective]
- Observe: facts (source, window), gaps
- Orient: situation, dominant constraint, blind spots
- Decide: action / hypothesis / invalidation / risk / tradeoffs (approved | amended | rejected)
- Act: what ran, metric deltas, outcome, side effects / rollback
- Next: loop | stop | need decision on …Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.