composio-community/awesome-claude-plugins / skill-bus/skills/reflecting-on-sessions
reflecting-on-sessions
VerifiedUse when completing a plan, finishing a development branch, wrapping up a session, or at any natural transition between work phases — reviews skill-bus telemetry to identify subscription gaps and suggest improvements
Reflecting on Sessions
Announce: "[skill-bus] Reflecting on this session's skill-bus activity."
When to Reflect
This skill is for natural transition moments:
- After executing a plan (all tasks complete)
- After finishing a development branch
- Before session wrap-up or handover
- At any natural pause between work phases
- When asked about skill-bus effectiveness
Process
Step 1: Check telemetry status
SB_CLI=$(ls ~/.claude/plugins/cache/*/skill-bus/*/lib/cli.py ~/.claude/plugins/repos/skill-bus/lib/cli.py 2>/dev/null | tail -1)
python3 "$SB_CLI" status --cwd "$PWD"
If telemetry is off, tell the user:
"Skill-bus telemetry is disabled for this project. To enable session reflection, add
"telemetry": trueto your skill-bus config. For full coverage visibility, also add"observeUnmatched": true."
Stop here if telemetry is off.
Step 2: Run stats for this session
SB_CLI=$(ls ~/.claude/plugins/cache/*/skill-bus/*/lib/cli.py ~/.claude/plugins/repos/skill-bus/lib/cli.py 2>/dev/null | tail -1)
python3 "$SB_CLI" stats --cwd "$PWD"
Step 3: Interpret and present
Present the stats output to the user with brief interpretation:
If there are suggestions, highlight the top 1-2:
- For uncovered skills: "I noticed [skill] ran N times without any subscription. Would you like to add one? I can run
/skill-bus:add-sub." - For condition skips: "[insert] was skipped N times due to conditions. This might mean the condition is too restrictive for your current workflow."
If everything looks healthy (matches > 0, no suggestions):
- "Skill-bus is working well this session — N skills intercepted, M inserts injected. No gaps detected."
If no telemetry data:
- "No telemetry data for this project yet. Have you invoked any skills this session?"
Step 4: Offer next steps
If there are actionable suggestions:
- "Would you like me to run
/skill-bus:add-subfor any of these?" - "Run
/skill-bus:reportanytime to check coverage."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |