think-reflect
Retrospective learning from a completed experience. Takes a project, incident, decision that played out, or time period; gathers ground truth (observations) separately from recollections; spawns reflectors applying different lenses (what-worked-vs-got-lucky, what-didn't, what-surprised, system-rewards-vs-intent, decisions-that-aged, what-to-tell-past-self, patterns-that-recur) in isolation; synthesizes into updated mental models as first-class output. Produces feedback only — no code, no tickets, no artifacts.
Profile →npx skills add majiayu000/claude-skill-registry --skill think-reflect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Think-Reflect - Retrospective Learning from Completed Experience Extracts learnings from something that already happened. Unlike every other `/think-*` skill, the input is a *past experience* — a project that shipped, an incident that resolved, a decision that played out, a time period that ended — not a decision to be made. The output is **updated mental models**: changed beliefs about how the world works, surfaced through lens-based reflection. **This skill produces no tangible artifacts.** It is a consultant, not an implementer. No code, no tickets, no commits. The output is a structured reflection report with updated mental models as the headline contribution. ## Roles **Judge (you, running this skill):** - Scope the experience being reflected on - Gather ground truth, rigorously separating observation from recollection - Load any external sources the user points to (logs, timelines, meeting notes, git history) - Choose appropriate reflection lenses - Spawn reflectors in isolation - Synthesize into a report with updated mental models prominent **Reflectors:** Each receives a specific reflection lens (what-worked-vs-got-lucky, what-didn't, what-surprised, system-rewards-vs-int
- Roles
- Workflow
- 1. Scope the Experience
- 2. Gather Ground Truth — Separate Observation from Recollection
- 3. Choose Reflection Lenses
- 4. Spawn Reflectors (Parallel, Isolated)
- 5. Synthesize
- 6. Report
- 7. No Iteration
- Constraints
- When to Use
- Relationship to Other Skills
- Philosophy
What does the think-reflect skill do?
Retrospective learning from a completed experience. Takes a project, incident, decision that played out, or time period; gathers ground truth (observations) separately from recollections; spawns reflectors applying different lenses (what-worked-vs-got-lucky, what-didn't, what-surprised, system-rewards-vs-intent, decisions-that-aged, what-to-tell-past-self, patterns-that-recur) in isolation; synthesizes into updated mental models as first-class output. Produces feedback only — no code, no tickets, no artifacts.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill think-reflect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.