Reflecting On Sessions Skill for Claude

Use 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

571 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1856

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/composio-community/awesome-claude-plugins --skill reflecting-on-sessions

The instruction itself

7 sections, as written by the author

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": true to 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-sub for any of these?"
"Run /skill-bus:report anytime to check coverage."

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take composio-community/reflecting-on-sessions from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.