agentleFS
Sign inStart free
qimen039-codeqimen039-code/claim-boundary-harness/skills/agent-error-memory/SKILL.md

agent-error-memory

Skill2 starsChanged 28 days agoMITView on GitHub

Use for an explicitly selected historical agent-error record or authorized durable recording of a material incident. Ordinary execution mistakes are fixed in the current task; they do not automatically invoke the incident-memory workflow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not hide agent-caused failure inside a success note.

    line 15

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 IDOuter retrieval surfacePaired solution
ERR-EXAMPLE-YYYY-MM-DDexample trigger wordsSOL-EXAMPLE-YYYY-MM-DD

Draft Field Guide

## 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:

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free