agentleFS
Sign inStart free
educlopezeduclopez/mallard/skills/reflect/SKILL.md

reflect

Skill4 starsChanged 13 days agoMITView on GitHub

Mine the current session for durable learnings and route each to a concrete edit of an existing skill, command or agent, waiting for approval before applying anything. Use when the user says "reflect", "reflexiona", "qué hemos aprendido", "mejora las skills con lo de hoy", "esto debería ir a una skill", or closes a session that exposed a repeated mistake or a missing step.

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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 163 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use what is already in the conversation.

    line 24
  2. Distinctive:

    Prefer the structural route over adding more prose.

    line 45

“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

Adapted from pstack's reflect. One pass, no parallel reviewers, no model switching. It does not save preferences or session state (that is engram) and does not touch the wiki (that is second-brain).

1. Skip when

The session was trivial, off-topic, or the skill that applied was followed correctly. One-offs are not learnings.

2. Collect

Use what is already in the conversation. If more is needed, read only this session's transcript under ~/.claude/projects/<slug>/ where <slug> is the working directory with each / turned into -. Never read other projects' transcripts.

3. Find candidates

A candidate needs evidence from the session:

  • The user corrected the same thing twice.
  • A skill step was wrong, stale or missing and you worked around it.
  • A skill did not fire when it should have (description problem).
  • A command or path failed in a way the skill did not warn about.

4. Route each candidate

KindRoute
A rule a script could enforceBacklog item: lint or check, see docs/skill-rules.md
Wrong or stale fact in a skillTrivial edit of that skill
New step, pattern or sectionSubstantive edit, use skill-author
Skill did not triggerTune its description
Nothing fits and it will recurNew skill via skill-author

Prefer the structural route over adding more prose.

5. Approval

Show a table: candidate, evidence, destination file, proposed change. Reject weak ones with a one-line reason. Wait for the user's OK, then apply only the approved rows. Never edit installed copies under ~/.claude/skills/ (they are symlinks into this repo; edit the repo). Never commit, push or open a PR.

6. Report

Edits applied (file, one line), backlog items, dropped candidates with reason.

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