agentleFS
Sign inStart free
lucasheriqueslucasheriques/pstack/skills/reflect/SKILL.md

reflect

Skill3 starsChanged 7 days agoMITView on GitHub

Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

172 other projects use a version of this, 47 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, make-bot-ui and 7 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.
  • 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

    principle-attack-the-premise

    Apply when repeated fixes fail and a shared assumption may be wrong.

    Also in 30 projects that use this

  • jaydubya818Skill

    principle-never-block-on-the-human

    Apply when safe reversible implementation details can proceed inside scope.

    Also in 36 projects that use this

  • +4 more from jaydubya818

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Before fanning out, find this conversation's transcript.

    line 15
  2. Very specific:

    Never edit a skill under plugins/cache/.

    line 49
  3. Distinctive:

    Follow each approved row's Routing exactly:

    line 51
  4. Very specific:

    If your environment ships a SKILL.md validator, run it on every touched skill before declaring done.

    line 58

“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

Mine the current conversation for durable learnings, then route them into skill edits.

Invoke when the user says "reflect" or "/reflect". Skip when the conversation is trivial, off-topic, or already covered by an existing skill the parent followed correctly. One-offs are not learnings.

1. Locate the active transcript

Before fanning out, find this conversation's transcript. It is ~/.claude/projects/<slug>/${CLAUDE_SESSION_ID}.jsonl, where <slug> is the session's starting directory with every non-alphanumeric character replaced by -. The session id is unique, so this finds it without opening any other chat:

ls ~/.claude/projects/*/${CLAUDE_SESSION_ID}.jsonl

This session's subagent transcripts sit in <slug>/${CLAUDE_SESSION_ID}/subagents/. If no path resolves, pass a tight digest of the session instead.

2. Spawn three reviewers in parallel

One message, three Agent tool calls, subagent_type: "pstack:read-only". Reviewers need MCP access to look up the tickets, chat threads, and observability traces the transcript references, and pstack:read-only keeps it.

LensModel from ${CLAUDE_SKILL_DIR}/../poteto-mode/references/models.mdPrompt template
Judgmentreflect judgment, divergent, synthesizer${CLAUDE_SKILL_DIR}/references/judgment-reviewer.md
Toolingreflect tooling${CLAUDE_SKILL_DIR}/references/tooling-reviewer.md
Divergentreflect judgment, divergent, synthesizer${CLAUDE_SKILL_DIR}/references/divergent-reviewer.md

Pass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in their final report.

3. Synthesize

One Agent tool call, subagent_type: "pstack:read-only", on the reflect judgment, divergent, synthesizer model. It spot-verifies citations through MCP. Pass ${CLAUDE_SKILL_DIR}/references/synthesizer.md verbatim, with each reviewer's full output inlined where marked. It returns an Accepted / Rejected / Backlog list.

4. Structural enforcement check

Move any Accepted item that a lint rule, script, metadata flag, or runtime check would enforce more reliably to Backlog. See principle-encode-lessons-in-structure.

5. Apply

Present the synthesizer's full Accepted / Rejected / Backlog output and wait for explicit approval before applying any Accepted edit. The user picks the subset and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.

File each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval.

Never edit a skill under plugins/cache/. Before approval, show its destination, .claude/skills/<skill>/ or ~/.claude/skills/<skill>/. After approval, copy the skill folder there and edit the copy. Never open a PR or push.

Follow each approved row's Routing exactly:

  • Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): parent does directly.
  • Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the skill-creator skill and run its draft / test / iterate loop.
  • tune description: <skill path> (the skill exists but didn't trigger when it should have): hand to skill-creator and run its description-optimization loop.
  • new skill via skill-creator: <kebab-name>: hand creation to skill-creator. Do not invent the shape ad hoc.

If your environment ships a SKILL.md validator, run it on every touched skill before declaring done.

6. Summarize for the user

Short list, no preamble:

  • Edits applied: <skill path>. What changed, one line each.
  • New skills created: <skill path>. One line each (rare).
  • Backlog filed to the devex tracker: <issue title> (<tags>). One line each.
  • Dropped: one line per rejected finding + reason from the synthesizer.

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