agentsclimarketplace

Learn

Skill isvlasov/rageatc-oss/plugins/rageatc-core-oss/skills/learn

Practical Claude Code / Cowork plugins for sharper thinking and structured problem-solving the slow way

Install
npx -y skills add isvlasov/rageatc-oss --skill learn

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

One thing to look at

  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Capture an observation — something that went wrong or worked well — to LEARNINGS.md for future reference. Quick in-session capture, not full analysis.

SKILL.md

1.3 KB, 257 tokens by cl100k_base, as published. Nobody here has run it

Learn

Capture an observation to LEARNINGS.md so it is preserved for future sessions and later /codify sweeps.

This is quick capture, not analysis — root cause analysis happens later, when the user runs /codify. Record what happened clearly enough that a future reader can understand it without this session's context.

Steps

  1. Locate or create LEARNINGS.md in the project root. If it does not exist, create it using the LEARNINGS.md template in the scaffolding-project skill (current frontmatter format lives there).
  2. Draft the entry from session context. With no arguments, the user is signalling "that was noteworthy — record it": draft your best understanding and ask "Here's what I'd capture — does this match how you see it?". With an argument, fold the user's pointer or perspective into the draft. Either way you write the entry; the user confirms or corrects — they should not have to explain the event from scratch.
  3. Append the entry following the format in the file's frontmatter comment. Distil, do not transcribe.
  4. Confirm — tell the user what was recorded and where. Nothing else needed.

Gives 0 of the 12 instructions most learn study skills give in 257 tokens

Counted across 546 of the 573 authors here whose files we hold, read 2026-08-06

  • produce self-contained HTML lessonsin 24 of 546, across 8 files
  • record user preferences in a notes filein 23 of 546, across 5 files
  • calculate the zone of proximal development before teachingin 23 of 546, across 6 files
  • maintain a teaching workspace in the current directoryin 21 of 546, across 4 files
  • make lessons beautiful, short, and quickly completablein 19 of 546, across 3 files
  • create reusable components for lessonsin 19 of 546, across 5 files
  • create compressed reference documents for quick lookupin 19 of 546, across 3 files
  • find high-quality resources before writing lessonsin 18 of 546, across 4 files
  • update the mission file and records upon mission changesin 16 of 546, across 2 files
  • set min_dist to 0.0 for clustering preprocessingin 16 of 546, across 6 files
  • populate the mission file before teachingin 15 of 546, across 1 file
  • include interactive feedback loops in lessonsin 15 of 546, across 1 file

Said here and by no other author read

  • Locate or create LEARNINGS.md in the project root
  • Draft the entry from session context
  • Fold any provided argument into the draft
  • Write the entry so the user only confirms or corrects
  • Append the entry following the frontmatter format
  • Distil the entry, do not transcribe

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. 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.