reflect
Skill0 starsChanged 18 days agoMITView on GitHub
Review the current conversation for durable lessons and prepare concrete edits to existing skills. Use when the user asks to reflect on a session.
172 other projects use a version of this.
Adopted by
Most recently taken up by
- Yeachan-Heo/oh-my-claude-sisyphustheir own version, first seen Nov 8, 2026
- Loner1024/skillstheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- endqwerty/endstacktheir own version, first seen Nov 8, 2026
- tristanphvn/keeltheir own version, first seen Nov 8, 2026
Other versions172 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 172
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- github/gh-aw★ 5.6ksame name
- backnotprop/pstack★ 3.8ksame name
- github/squad★ 3.4ksame name
- rilldata/rill★ 3ksame name
- microsoft/waza★ 1.5ksame name
- llama-farm/llamafarm★ 837same name
- haddock-development/claude-reflect-system★ 373same name
- egregore-labs/egregore★ 293same name
162 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 repository58 other files it gives its agents.
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- figure-it-outSkill
- howSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- no-commentsSkill
- poteto-helpSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-type-system-disciplineSkill
- recallSkill
- scala-akka-best-practicesSkill
- setup-pstackSkill
- sharpenSkill
- show-me-your-workSkill
- statechartSkill
- swarmSkill
- tddSkill
- teachSkill
- technical-writingSkill
- typescript-best-practicesSkill
- unslopSkill
- whySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 163 edited versions we read keep these.
5
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
- Distinctive: line 6
Read the Codex runtime adapter once per session before using this skill.
- Distinctive: line 12
Use the current context or a host-supplied transcript path.
- Distinctive: line 20
Use permitted native reviewers when available, otherwise apply the lenses sequentially.
- Distinctive: line 22
Prefer architecture, types, lint, metadata, or a script over adding another instruction.
- Distinctive: line 26
Use skill-creator for substantial authoring and validate changed skills.
“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.
Files
Read the Codex runtime adapter once per session before using this skill. Its tool, model, history, and authorization mappings apply to all linked instructions.
Reflect
Find durable lessons in the current conversation and turn them into reviewable changes.
Use the current context or a host-supplied transcript path. A scoped Codex chat read is useful when available. Do not search private session stores. Label a digest when full tool history is unavailable.
Review through three lenses using the packaged prompts when useful:
- Judgment.
- Tooling.
- Divergent.
Use permitted native reviewers when available, otherwise apply the lenses sequentially. Reviewers remain read-only even when they can access MCP tools. Synthesize with the synthesizer prompt.
Prefer architecture, types, lint, metadata, or a script over adding another instruction. Accept a lesson only when concrete evidence supports it and it has a real destination. Route a missed trigger to the skill description. Reject one-off preferences presented as universal rules.
Prepare exact proposed edits and their destinations, plus rejected and backlog items. Apply edits when the user has already authorized those skill changes. Otherwise present the concrete patch for selection before changing durable behavior. Never edit a plugin cache. Use a requested source location or an editable local skill copy.
Use skill-creator for substantial authoring and validate changed skills. Keep backlog items local unless the user explicitly authorized filing them externally. Report applied changes, pending choices, and evidence limitations.
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.