reflect
Skill293 starsChanged 11 days agoMITView on GitHub
Use when the user says 'we decided', 'I realized', or 'that's a pattern' — captures a share-ready decision, finding, or pattern in canonical organizational memory. Use /note for private or half-baked thoughts and /archive for reusable AI-steering techniques.
183 other projects use a version of this.
Adopted by
Most recently taken up by
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- TencentBlueKing/bk-litetheir own version, first seen Nov 16, 2026
- GoBeromsu/craft-skillstheir own version, first seen Nov 16, 2026
- gfunc/skillstheir own version, first seen Nov 16, 2026
- shiwenbin1617/pstacktheir own version, first seen Nov 16, 2026
- anis-dr/skillstheir own version, first seen Nov 16, 2026
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.
ianclearySkillpoteto-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
bnemaSkillsetup-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
eryzerzSkillmake-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
ianclearySkillprinciple-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
jaydubya818Skillautomate-me
Use when the user wants working preferences captured in a reusable mode skill.
Also in 39 projects that use this
jaydubya818Skillpoteto-mode
Use when non-trivial work should follow the smallest rigorous Jstack workflow.
Also in 27 projects that use this
- +6 more from jaydubya818
Other versions183 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 183
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- github/gh-aw★ 5.6ksame name
- backnotprop/pstack★ 4.2ksame name
- github/squad★ 3.4ksame name
- rilldata/rill★ 3ksame name
- microsoft/waza★ 1.5ksame name
- osmlab/name-suggestion-index★ 893same name
- llama-farm/llamafarm★ 837same name
- haddock-development/claude-reflect-system★ 373same name
173 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 173 edited versions we read keep these.
3
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
- Distinctive: line 12
Use when the user says 'we decided', 'I realized', or 'that's a pattern' — captures a share-ready decision, finding, or pattern in …
- Distinctive: line 16
No arguments: use a short Socratic flow grounded in this session.
- Very specific: line 39
No pattern fits and the insight recurs or generalizes: create the pattern first, then the evidence linked to the artifact_id in its receipt.
- Distinctive: line 64
Use returned evidence for dedupe.
- Very specific: line 82
Add repeated --topic, --subtype evidence, --relationship "RELATION:TARGET", --situation-*, or --supersedes "ARTIFACT_ID" arguments only …
- Very specific: line 93
Do not run /save, Git, index, embedding, graph, telemetry, publish, share, or notification mechanics separately.
“Common” is measured: kept by at least 6 in 10 of the 173 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.
Files
Reflect
Turn a settled insight into one to three typed, share-ready knowledge artifacts.
When to invoke
Use when the user says 'we decided', 'I realized', or 'that's a pattern' — captures a share-ready decision, finding, or pattern in canonical organizational memory. Use /note for private or half-baked thoughts and /archive for reusable AI-steering techniques.
Modes
- No arguments: use a short Socratic flow grounded in this session.
about <topic>: focus the flow on that topic.[decision|finding|pattern]: <content>: honor the explicit type.- Other arguments: quick capture; infer the type, defaulting to
finding.
Context
Reuse attached EGREGORE_ORG_CONTEXT_V1 evidence. When it is sufficient, do
not reopen sources. If a named gap remains, make one
bash bin/search.sh find "<concept>" --kind hybrid -n 6 call and open only the
missing canonical source through bash bin/search.sh open. Never query
implementation infrastructure or storage directly.
Two layers
Knowledge is saved as a pattern (a general motif) and evidence (the
specific, dated, sourced case, a finding with subtype evidence) linked by
instance-of. Before classifying, search existing motifs once:
bash bin/search.sh find "<motif in general words>" --kind hybrid --prefix memory/knowledge/patterns -n 5.
- A pattern fits: create only the evidence, linked to that pattern's id (or
canonical path).
bash bin/knowledge.sh instances <pattern-id>lists what already instances it. - No pattern fits and the insight recurs or generalizes: create the pattern
first, then the evidence linked to the
artifact_idin its receipt. - A one-off fact or a decision needs no pattern.
A pattern reads as a general motif: no organization or people names and no
dates in the motif sentence; the evidence keeps the specifics. Pattern body
sections: Motif, Where it lives, When it shows up, How to recognise it, The
move, When it doesn't apply, Situations (for discovery). Name the first case in
one line under Instances; the live list is the instances command. Situations
go in as repeatable flags: --situation-domain (a field such as meta-harness
design), --situation-path (repository-relative glob), --situation-activity
(what someone is doing). A matching later session gets one offer line,
Patterns that may apply: …; knowledge.sh situated runs it on demand.
Relationships: instance-of (evidence → pattern), responds-to (decision →
the evidence it answers), applies (decision → the pattern it acts on),
supersedes, relates-to. Other relations are kept with a warning.
Flow
- Extract the title, exact insight, context, rationale, two to four topics, workstream, explicit relationships, and superseded artifact IDs when known.
- Classify each distinct insight as
decision,finding, orpatternand place it in the two layers above. Create at most three artifacts. Do not infer supersession or authority from recency. - Use returned evidence for dedupe. If a likely duplicate exists, open it through the Runtime boundary and ask whether to supersede it or create a distinct artifact.
- Preview every proposed artifact, the pattern and its evidence together, and
wait for
y, edits, orskip. Nothing is canonical before this acceptance. - For each accepted artifact, render its complete Markdown body to a temporary
file under
tmp/and call exactly one domain command;{artifact-file}is that file and the other values come from the accepted artifact:
bash bin/knowledge.sh create \
--type '{artifact-type}' \
--title '{title}' \
--input '{artifact-file}' \
--topic '{topic}' \
--workstream '{workstream}'Add repeated --topic, --subtype evidence, --relationship "RELATION:TARGET",
--situation-*, or --supersedes "ARTIFACT_ID" arguments only when they apply.
The Runtime resolves ActorContext, authorizes, assigns stable
identity/provenance, persists canonical Markdown, records Git provenance,
refreshes retrieval, starts background embedding, and emits content-free
telemetry. Report receipt warnings and partial projection honestly; the
canonical artifact remains authoritative.
Boundaries
- Reflection is share-ready organizational knowledge, not a private note.
- Do not run
/save, Git, index, embedding, graph, telemetry, publish, share, or notification mechanics separately. - A graph is an optional downstream projection and cannot override Markdown.
- Publishing, external sharing, and notification each require their own action permission and explicit consent; reflection never implies them.
Report the artifact type, title, canonical path, and writeback status. Keep the
existing compact ◎ REFLECTION confirmation style when rendering rich output.
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
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.

