How do I install the Reflecting On Sessions skill?

Run npx skillmds add majiayu000/reflecting-on-sessions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Reflecting On Sessions safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reflecting On Sessions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reflecting On Sessions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Reflecting On Sessions?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reflecting On Sessions by majiayu000

Name: Reflecting On Sessions
Rating: 4.2 (5 reviews)
Author: majiayu000

Reflecting On Sessions

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

majiayu000 49d0600 2 files · 3.9 KB Updated Sep 9, 2026 567 repo stars

File contents

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."

---name: reflecting-on-sessionsdescription: 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--- # 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 ```bash 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 ```bash 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."

Frequently asked questions