Learn
Skill isvlasov/rageatc-oss/plugins/rageatc-core-oss/skills/learn
Capture an observation — something that went wrong or worked well — to LEARNINGS.md for future reference. Quick in-session capture, not full analysis.From its SKILL.md
npx -y skills add isvlasov/rageatc-oss --skill learnAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 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.
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
- Locate or create
LEARNINGS.mdin 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). - 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.
- Append the entry following the format in the file's frontmatter comment. Distil, do not transcribe.
- Confirm — tell the user what was recorded and where. Nothing else needed.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.