Empty template for paired agent error memory. Use to record agent-caused execution, diagnosis, safety, routing, or process failures after they are solved and ready for reuse.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add qimen039-code/claim-boundary-harness --skill agent-error-memory --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Agent Error Memory?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qimen039-code-agent-error-memory)More formats (shields.io, HTML) on the badges page.
---
name: agent-error-memory
description: Empty template for paired agent error memory. Use to record agent-caused execution, diagnosis, safety, routing, or process failures after they are solved and ready for reuse.
---
# Agent Error Memory
This file starts empty by design. Add real records only after a solved incident.
## Pairing Rule
- Error records live here.
- Solution records live in `bug-solution-memory`.
- Each error point must include `paired_solution_ids`.
- Do not hide agent-caused failure inside a success note.
## Storage Contract
The table and field list below document the record shape; they are not the
writable memory store. New records use `cbh.semantic_memory_record.v3` and are
appended with `../embedded-harness/semantic_memory.py` to the adopting lane's
private `memory-v3/` directory. The canonical `records.jsonl` is append-only;
`meta.jsonl` is a compact, rebuildable navigation surface. Existing Markdown
records, when present in an older deployment, stay read-only and are exposed
through hash-bound legacy links instead of being copied or rewritten.
## Reference Index Shape
| Error ID | Outer retrieval surface | Paired solution |
| --- | --- | --- |
| `ERR-EXAMPLE-YYYY-MM-DD` | example trigger words | `SOL-EXAMPLE-YYYY-MM-DD` |
## Draft Field Guide
```text
## ERR-EXAMPLE-YYYY-MM-DD
status:
point_kind: agent_error_solid_point
purpose_anchor:
meaning_anchor:
outer_retrieval_surface:
event_summary:
agent_fault:
why_it_was_wrong:
impact:
evidence:
applicable_boundaries:
non_applicable_boundaries:
risk_failure_conditions:
paired_solution_ids:
prevention_rule:
not_to_repeat:
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!