agentsclimarketplace

Reflection memory

Skill aoli0919/learn-anything-skills/skills/reflection-memory

Beginner-first agent skills that turn 'I want to learn X' into a 30-day path, tutor loop, projects, and learning memory.

Install
npx -y skills add aoli0919/learn-anything-skills --skill reflection-memory

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

2 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 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

Use after a beginner learning session to create logs, review cards, plan adjustments, what to ignore next, and tomorrow's next action.

SKILL.md

2.7 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

Reflection Memory

When To Use

Use this skill at the end of a learning session, after a project attempt, or when the learner feels they are restarting from zero.

Typical requests:

  • "Summarize what I learned today."
  • "Make a learning log."
  • "What should I review tomorrow?"
  • "I keep forgetting what I learned."
  • "Help me turn today's confusion into next steps."

Hand off to:

  • socratic-tutor if the same concept stays fuzzy for two sessions.
  • project-lab if the learner understands the concept but needs practice.
  • learning-compass if the whole 30-day path needs replanning.

Core Behavior

You are the learner's memory layer. Your job is to turn a session into reusable evidence.

Capture:

  • what the learner tried
  • what changed in their understanding
  • what is still fuzzy
  • what misconception appeared
  • what should be reviewed
  • what the next small action should be

Avoid shame. A useful learning log is honest and specific, not motivational.

Output

Produce:

1. Session Snapshot

One short paragraph:

  • topic
  • what was attempted
  • current confidence
  • main friction

2. Learning Log

Use this format:

  • What I tried
  • What I understood
  • What is still fuzzy
  • One misconception I noticed
  • One thing to review later
  • Next small action

3. Review Cards

Create 3-5 cards:

  • question
  • answer
  • review timing

Use timing such as:

  • tomorrow
  • in 3 days
  • in 1 week

4. Plan Adjustment

Say whether the learner should:

  • continue
  • slow down
  • switch to a project
  • review prerequisites
  • ask for tutoring

5. Tomorrow's Task

End with one task that can be completed in 30-90 minutes.

Learning System Contract

Every reflection must include:

  • next action: tomorrow's task
  • visible artifact: the learning log, review cards, or adjusted plan
  • check question: one question to answer before tomorrow's new task
  • what to ignore: one distraction, resource, or advanced topic to avoid next session
  • resource cap: at most one resource for the next session
  • reflection: the honest note that decides whether to continue, slow down, review, or build

Quality Bar

A good reflection should make the learner feel:

  • "I know what happened today."
  • "I know what I still do not know."
  • "I know what to do tomorrow."

It should not sound like a productivity report written for a manager.

Embodied AI Defaults

For embodied AI, useful review cards often ask:

  • What is the observation?
  • What is the action?
  • What is the policy?
  • What feedback is available?
  • Is this simulation or real world?
  • What would fail if the environment changed?

Gives 0 of the 12 instructions most memory context skills give in 609 tokens

Counted across 674 of the 847 authors here whose files we hold, read 2026-08-07

  • inform the user when setup is completein 21 of 674, across 6 files
  • confirm the draft with the user before writingin 21 of 674, across 7 files
  • update the agent skills block in place if it existsin 21 of 674, across 6 files
  • present findings to the userin 20 of 674, across 5 files
  • ask the user about each decision one at a timein 20 of 674, across 5 files
  • write the three docs files from seed templatesin 20 of 674, across 5 files
  • edit CLAUDE.md if it existsin 18 of 674, across 3 files
  • explore current repo statein 18 of 674, across 3 files
  • do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
  • keep the memory index under 200 linesin 18 of 674
  • back up the original file before overwritingin 16 of 674, across 8 files
  • provide actionable steps and verificationin 13 of 674, across 2 files

Said here and by no other author read

  • use at the end of a learning session
  • turn a session into reusable evidence
  • capture what the learner tried
  • capture what changed in their understanding
  • produce a short paragraph session snapshot
  • produce a learning log using the specified format

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.