agentsclimarketplace

Learn

Skill boshu2/agentops/skills/learn

Optionally analyze collections of durable verdicts for recurring evidence after the critical path. Triggers: "learn from verdicts", "mine validation history".From its SKILL.md

Install
npx -y skills add boshu2/agentops --skill learn

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.2 KB, as published. Nobody here has run it

Learn

Learn is an optional, off-path consumer of durable verdict.v2 collections. It may summarize recurring evidence and propose a candidate deterministic check for later human or caller evaluation.

Learn does not run during RPI, validate a subject, alter a verdict, mutate a plan, promote a rule, choose continuation, or mint lifecycle artifacts. Missing Learn output never changes whether a candidate is valid.

When invoked, bind every observation to verdict and finding digests, distinguish repeated objectives from repeated reviews of one objective, disclose the sample size, and stop at advisory evidence.

Overweight failures: a NOT_PROVEN or FAIL verdict carries more teaching value than a PASS, because it names a rule the loop lacked. Harvest kernels from failed lanes first — the canonical example is the mutating-check quarantine in skills/validate/SKILL.md, a durable rule minted from a NOT_PROVEN-then-PASS verdict pair.

Prune for provenance decay: every cited artifact must still resolve — the file exists or the verdict digest is present under .agents/ao/verdicts/. A citation that no longer resolves gets pruned rather than paraphrased, and confidence in a lesson that has not been reproduced since its source decayed goes down, not sideways.

When the caller asks for a durable artifact, write the observations under .agents/scratch/learn/ and return the path; otherwise return them inline. The write is advisory and TTL'd — it is never a source of record, and its absence never changes whether a candidate is valid.

What ships with it: 2 files

815 B alongside SKILL.md, 1 of them executable

references/

scripts/

Gives 0 of the 12 instructions most learn study skills give

Counted across 545 of the 593 authors here whose files we hold, read 2026-09-06

  • Treat the current directory as a teaching workspacein 20 of 545, across 17 files
  • Teach knowledge first then practice skillsin 19 of 545, across 16 files
  • Design lessons which build long-term retentionin 15 of 545, across 12 files
  • Save each lesson as a self-contained HTML filein 15 of 545, across 12 files
  • Question the user on why they want to learn thisin 15 of 545, across 12 files
  • Reuse components from the assets directoryin 14 of 545, across 11 files
  • Never trust your parametric knowledgein 13 of 545, across 10 files
  • Record user preferences in NOTES.mdin 11 of 545, across 8 files
  • Ground all teaching in the MISSION.md documentin 11 of 545, across 8 files
  • Save each lesson to the lessons directoryin 8 of 545
  • Question the user if the mission is unclearin 7 of 545
  • Gather primary sources onlyin 7 of 545, across 4 files

Said here and by no other author read

  • Bind every observation to verdict and finding digests
  • Distinguish repeated objectives from repeated reviews
  • Disclose the sample size
  • Stop at advisory evidence
  • Harvest kernels from failed lanes first
  • Prune citations that no longer resolve

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,373. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.