agentleFS
Sign inStart free
GusevV1987GusevV1987/ai-workspace-kit/skills/reflect/SKILL.md

reflect

Skill2 starsChanged 8 months agoMITView on GitHub

Review repeated corrections, preferences, and guardrails from recent sessions. Use when: "/reflect", "review my corrections", or "apply the repeated lessons".

172 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use poteto-help, setup-pstack and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 24 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 19 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 26 projects that use this

  • jaydubya818Skill

    automate-me

    Use when the user wants working preferences captured in a reusable mode skill.

    Also in 39 projects that use this

  • jaydubya818Skill

    poteto-mode

    Use when non-trivial work should follow the smallest rigorous Jstack workflow.

    Also in 27 projects that use this

  • +6 more from jaydubya818

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 163 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If it is missing or empty, tell the user there are no queued corrections.

    line 28
  2. Distinctive:

    When applying a correction:

    line 54
  3. Distinctive:

    place it in an existing section when possible

    line 57
  4. Distinctive:

    use bullet points, not long paragraphs

    line 58
  5. Distinctive:

    Remove the items that were applied.

    line 62
  6. Distinctive:

    Leave unapproved items in place.

    line 64
  7. Distinctive:

    Only promote patterns that are truly repeated.

    line 81

“Common” is measured: kept by at least 6 in 10 of the 163 edited versions of this file we could read. “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

Reflect

Purpose

Move repeated corrections out of chat memory and into durable files.

Queue File

Default queue:

memory/corrections-queue.json

This repo includes an empty starter file. You can fill it manually or automate it later.

Step 1: Read The Queue

Read memory/corrections-queue.json.

If it is missing or empty, tell the user there are no queued corrections.

Step 2: Show The Candidates

List each queued item with:

  • type
  • confidence
  • message
  • timestamp

Then ask:

Which ones should I apply?

Step 3: Route Each Approved Item

Kind of correctionPut it in
long-term behavior ruleMASTER.md
stable preferenceMASTER.md or MEMORY.md
important decisionMEMORY.md
one-off noteleave it out of long-term files

Step 4: Write Clearly

When applying a correction:

  • keep it short
  • place it in an existing section when possible
  • use bullet points, not long paragraphs

Step 5: Clean The Queue

Remove the items that were applied.

Leave unapproved items in place.

Step 6: Confirm

Example:

Reflect complete.
- Applied: 2
- Left in queue: 1
- Updated: MASTER.md, MEMORY.md

Rule

Only promote patterns that are truly repeated.

One complaint is not a rule.

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.

Check your setup, free