Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Makes agent corrections persistent and reusable. When you override, reject, or correct an agent's output, this skill logs the correction and automatically in...
Makes agent corrections persistent and reusable. When you override, reject, or correct an agent's output, this skill logs the correction and automatically in...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When you correct an agent, that correction evaporates after the session. Next time you spawn the same agent type, it makes the same mistake. There's no memory of what you've already taught it.
lib/correction-tracker.js β logs corrections per agent type to memory/corrections/[AgentType].jsonl Hook into agent-context-loader.js β correction preamble prepended to spawns automatically (if intent-engineering is also installed)
cp references/correction-tracker-template.js $OPENCLAW_WORKSPACE/lib/correction-tracker.js Verify it runs: node $OPENCLAW_WORKSPACE/lib/correction-tracker.js
If lib/agent-context-loader.js is installed (from intent-engineering skill), correction injection is automatic β no wiring needed. The loader checks for correction-tracker.js at startup and loads it if present. If you are NOT using intent-engineering, add this to your spawn logic manually: const { buildCorrectionPreamble } = require('./lib/correction-tracker'); const agentType = 'CoderAgent'; // or whatever agent you're spawning const corrections = buildCorrectionPreamble(agentType, workspaceRoot); const fullTask = corrections ? corrections + '\n\n---\n\n' + originalTask : originalTask;
const { logCorrection } = require('./lib/correction-tracker'); logCorrection( 'CoderAgent', // agent type 'Used ESM import instead of require()', // what was wrong 'Always use require() for Node.js stdlib modules', // correct behavior workspaceRoot, { session_channel: 'discord' } // optional metadata );
Just tell the main agent: "Note that [AgentType]: [what it did wrong] β [correct behavior]" The main agent will log it programmatically.
On every subagent spawn, agent-context-loader detects the agent type from the task description and prepends: ## Corrections from Previous Sessions The following corrections were logged for CoderAgent. Apply these behaviors: 1. **[2026-03-01] Issue:** Used ESM import instead of require() **Correction:** Always use require() for Node.js stdlib modules Only corrections from the last 30 days are injected. Older corrections expire automatically β stale rules don't accumulate.
# All corrections for an agent type cat $OPENCLAW_WORKSPACE/memory/corrections/CoderAgent.jsonl | jq . # List all agent types with corrections ls $OPENCLAW_WORKSPACE/memory/corrections/ # Count corrections per agent for f in $OPENCLAW_WORKSPACE/memory/corrections/*.jsonl; do echo "$(basename $f .jsonl): $(wc -l < $f) corrections" done
The loader auto-detects agent type from the task description. Default rules: Task keywordsAgent typecode, coder, impl, debugCoderAgentwrit, author, novel, chapterAuthorAgentworld, buildWorldbuilderAgent(anything else)general To add custom agent types, edit detectAgentType() in agent-context-loader.js.
references/correction-tracker-template.js β Full implementation of correction-tracker.js
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.