agentleFS
brianbolzebrianbolze/truffle/.claude/skills/agent-learning-mine/SKILL.md

agent-learning-mine

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Retroactively mine past Claude Code session transcripts into raw learning-loop observations — the optional, fenced capture feeder the learning-system proposal anticipated. Use to seed or backfill `learning/observations/` from friction already on disk (Brian corrections, `/overwhelmed` firings, reviewer catches) that in-band capture missed. One sighting per file, never a fix — defers to `learning/AGENTS.md` for every rule. NOT the review/consolidate pass (that's learning-review); it never proposes a fix or a lesson.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    Report and stop: Do not consolidate or propose.

    line 36

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

$ARGUMENTS

Purpose

Mine past session transcripts for friction and write it into learning/observations/ as raw observation files. This is retroactive capture — a sibling to the in-band capture a run does live, feeding the same observations/ folder under the same rules. It catches what live capture misses: friction in older sessions, and the quiet kind an agent never self-reported.

It is the proposal's "optional, fenced mine.py feeder" — best-effort, and degrades gracefully. The markdown observations are the durable layer; they survive even if transcript access ever vanishes.

What this is not

  • Not the review/consolidate pass — it never clusters, proposes, or writes a lesson. That is learning-review, run separately afterward.
  • Not a fix-proposer — it writes raw observations only; the no-fix rule is the whole point.
  • Not live infrastructure — you run it by hand, it writes evidence, it stops.

Required context — defer to these, don't restate them

The observation contract lives in the learning folder; this skill carries only the mining procedure. Read these first and obey them for the card shape, the five kinds, and the no-fix / immutable / one-file-per-sighting rules:

  • learning/AGENTS.md — the contract.
  • learning/observations/_TEMPLATE.md — the exact file you write (frontmatter, Saw. / Not claiming., no fix slot).

Task

  1. Ground in the contract above. The rules are theirs; this skill is only the procedure.
  2. Distill the corpus. Run python3 .claude/skills/agent-learning-mine/scripts/extract.py (optionally --since YYYY-MM-DD). It turns the raw transcripts (1+ GB) into small per-session digests — human turns verbatim, /overwhelmed firings, and friction-flagged assistant lines — in a scratch dir outside the repo, and prints that path. It fails loud if the transcript format has drifted; if it does, stop and report — don't mine garbage.
  3. Read existing observations in learning/observations/ so you don't re-nominate what's already captured.
  4. Nominate candidates from the digests. For a large corpus, fan out reader subagents (Sonnet is plenty — this is extraction against a clear rubric) over digest batches. Each candidate is one sighting + a verbatim quote as its evidence + a proposed kind — and no fix (defer to the template). You hold synthesis: dedup identical sightings (keep genuine cross-session repeats — those are the signal), drop weak or fix-smuggling ones, and verify each quote against the digest before trusting it.
  5. Write raw observation files per the template — one file per sighting, immutable shape. Stamp the run: field with the session id it came from, marked as mined (the template allows a session id when there is no packet).
  6. Report and stop. Do not consolidate or propose. Run /learning-review agentic-build separately when you want the clustering pass.

Hard lines

  • Raw observations only — no fix, no lesson, no routing decision (the template's three rules govern).
  • Fenced + best-effort — the transcript store is an undocumented Claude Code internal; fail loud on drift, never silently emit empty or malformed cards.
  • Digests are scratch — they hold transcript content; leave them in the temp dir, never commit them.
  • Mining sees only noticed friction — say so in your report; a confident-but-wrong run no one caught leaves no trace, so absence from the log is not proof.

Final response

End with:

  • the scratch digest dir + how many sessions it distilled
  • how many observations you wrote, by kind, and from which sessions
  • the honest blind-spot line (mining sees only what was noticed)
  • No lesson was proposed and nothing was consolidated — run /learning-review agentic-build for that.

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.