Summary
When Claude responds using a skill from .claude/skills/, there's no indication to the user that a skill is being applied. It would be helpful to see which skill (if any) is guiding the response.
Current Behavior
- Skills are loaded silently from
.claude/skills/
- Responses that use skills look identical to responses inferred from context
- No way to verify if a skill was actually used
/skills command doesn't exist to list loaded skills
Desired Behavior
Some indication when a skill is active, e.g.:
> Reggie, how's my backlog?
⏺ Using skill: reggie-backlog-health
⏺ Bash(python reggie.py health --all)
...
Or a /skills command to list loaded skills and their trigger patterns.
Why This Matters
- Debugging: Hard to tell if a skill isn't working or just not triggering
- Trust: Users can't verify their skill customizations are being applied
- Development: When building skills, feedback on activation helps iteration
Environment
- Claude Code v2.0.69
- macOS
Summary
When Claude responds using a skill from
.claude/skills/, there's no indication to the user that a skill is being applied. It would be helpful to see which skill (if any) is guiding the response.Current Behavior
.claude/skills//skillscommand doesn't exist to list loaded skillsDesired Behavior
Some indication when a skill is active, e.g.:
Or a
/skillscommand to list loaded skills and their trigger patterns.Why This Matters
Environment