Reflecting On Sessions

Session-end reflection that mines skill-bus telemetry for coverage gaps

Works with setup

Test report

Verdict
Works with setup
Score
7.2/10
Tested
Jul 20, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · 49d0600

Fetched the real SKILL.md plus skill-bus plugin.json, cli.py, dispatcher.py, and telemetry.py from the repo; the `status`/`stats` commands it invokes genuinely exist (stats subparser at cli.py line 1126). Security scan clean: telemetry.py only appends to a local .claude/skill-bus-telemetry.jsonl, dispatcher's sole subprocess is `git branch`, no network/base64/secrets/exfiltration. OUTPUT NOT measured (not a measured loss): the skill is a thin orchestrator over the skill-bus CLI and needs the plugin installed, telemetry enabled, and hook-collected session data before it emits anything — none of which I install or run; INSTALL docked 1 point because SKILL.md is inert without that plugin runtime. TRIGGER 5/5 (all correct): SHOULD fire — "We've finished every task in the plan, let's wrap up this session", "How effective has skill-bus been this session?", "I'm done with this feature branch, anything to reflect on before I merge?"; should NOT — "Add a subscription for the seo skill to skill-bus" (that's /add-sub, not reflection), "Reflect on my career goals for next year" (reflection but not skill-bus telemetry).

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 4/5
  • Triggers reliably 5/5
  • Output vs. baseline 5/10
  • Docs & honesty 4/5

What Reflecting On Sessions does

A skill-bus companion skill that, at natural work transitions, runs the skill-bus CLI over project telemetry to surface skill-subscription coverage gaps and suggest fixes. Triggers when you finish a plan, wrap a branch, close a session, or ask how effective skill-bus has been.

How to install Reflecting On Sessions

Ships inside the skill-bus plugin (v0.7.0, MIT, by Joey Nguyen). Install the plugin — add ComposioHQ/awesome-claude-plugins as a plugin marketplace, or clone joeymnguyen/skill-bus into ~/.claude/plugins — then enable telemetry by adding "telemetry": true (optionally "observeUnmatched": true) to the skill-bus config. The skill and its runtime (lib/cli.py, dispatcher.py, telemetry.py, hooks) come with the plugin; copying SKILL.md alone is inert.

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Reflecting On Sessions

  • /reflecting-on-sessions Session-end reflection that mines skill-bus telemetry for coverage gaps

It also activates on plain-language prompts like these:

  • Reflect on this session before I close the branch
  • Check the skill-bus telemetry for gaps
  • Wrap up this session and suggest improvements

Frequently asked questions

Is the Reflecting On Sessions skill free?
Yes. The skill itself is free from ComposioHQ/awesome-claude-plugins. SkillProof publishes the install command and an independent test verdict at no cost.
Does Reflecting On Sessions work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 20, 2026. Verdict: Works with setup. Fetched the real SKILL.md plus skill-bus plugin.json, cli.py, dispatcher.py, and telemetry.py from the repo; the `status`/`stats` commands it invokes genuinely exist (stats subparser at cli.py line 1126). Security scan clean: telemetry.py only appends to a local .claude/skill-bus-telemetry.jsonl, dispatcher's sole subprocess is `git branch`, no network/base64/secrets/exfiltration. OUTPUT NOT measured (not a measured loss): the skill is a thin orchestrator over the skill-bus CLI and needs the plugin installed, telemetry enabled, and hook-collected session data before it emits anything — none of which I install or run; INSTALL docked 1 point because SKILL.md is inert without that plugin runtime. TRIGGER 5/5 (all correct): SHOULD fire — "We've finished every task in the plan, let's wrap up this session", "How effective has skill-bus been this session?", "I'm done with this feature branch, anything to reflect on before I merge?"; should NOT — "Add a subscription for the seo skill to skill-bus" (that's /add-sub, not reflection), "Reflect on my career goals for next year" (reflection but not skill-bus telemetry).
What is the Reflecting On Sessions SkillProof Score?
7.2/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.
How do I install Reflecting On Sessions?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Reflecting On Sessions with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.