Menu

Individual skill

reflect

Mine this session's transcript for lessons that will still hold in six months and turn each into an edit to a skill the session used, applied only after the user approves. Use at the end of a session, or on "reflect", "what should we learn from this", "capture lessons".

plugins/requie/endostack/skills/reflect/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# reflect

Three reviewers read this session's transcript through different lenses, a synthesizer filters what they find, and you apply only the rows the user approves. The output is a small number of skill edits that change what the next agent does. A one-off event is not a lesson, and a lesson that a lint rule or script could enforce goes to the backlog instead of into prose.

Run it only when the user asks. Skip it, and say why in one line, when the session was trivial, off-topic, or followed an existing skill correctly with nothing new surfacing.

Track a todo list with these seven items: locate, review, synthesize, enforce, approve, apply, summarize.

## 1. Locate the transcript

Find the transcript file for this conversation. Look only in the transcript directory the agent uses for the current workspace. The per-agent page under `docs/agents/<agent>.md` names that location. Never list or search transcript folders for other workspaces: they hold the user's private conversations about other projects, and reading them is a privacy breach even if nothing is reported.

Within that directory, list the most recently modified transcript files across whatever layouts the agent uses (single files, a folder per conversation, nested subagent transcripts). Take the newest ten or so and read the first record of each. Pick the one whose first user message matches the opening message of this conversation.