Agent Skill
2/7/2026reflect
Analyze and improve skills based on session outcomes. Use when: user says "reflect", "improve the skill", "what went wrong with the skill", "optimize skills", or wants to analyze skill effectiveness after using one. Triggers: "reflect", "skill improvement", "fix the skill", "update skill based on session".
T
tobiasbak
0GitHub Stars
1Views
npx skills add TobiasBak/dotfiles
SKILL.md
| Name | reflect |
| Description | Analyze and improve skills based on session outcomes. Use when: user says "reflect", "improve the skill", "what went wrong with the skill", "optimize skills", or wants to analyze skill effectiveness after using one. Triggers: "reflect", "skill improvement", "fix the skill", "update skill based on session". |
name: reflect description: | Analyze and improve skills based on session outcomes. Use when: user says "reflect", "improve the skill", "what went wrong with the skill", "optimize skills", or wants to analyze skill effectiveness after using one. Triggers: "reflect", "skill improvement", "fix the skill", "update skill based on session".
Reflect
Analyze conversation context to identify used skills, evaluate effectiveness, and apply improvements.
Workflow
- Check for skill usage - Scan context for
Skilltool calls or<command-name>tags. If none found, inform user "No skills were used this session" and stop. - Analyze context - Identify issues and outcomes from the skills that were used
- Gather feedback - Use AskUserQuestion if issues aren't clear from context
- Read skill files - Glob for
~/.claude/skills/*/SKILL.md, read relevant ones - Identify gaps - Compare skill instructions vs actual behavior vs user expectations
- Apply changes - Edit skill files, preserve YAML frontmatter + markdown structure
- Report - Summarize what was analyzed, identified, and changed
Common Issues to Look For
- Missing/wrong trigger phrases in description
- Unclear or ambiguous workflow steps
- Missing edge case handling
- Overly verbose instructions (violates "concise is key")
- Missing tool usage patterns
Guidelines
- Be conservative - only fix clear issues
- Focus on root causes, not symptoms
- Consider if issue was with skill or how it was invoked
Skills Info
Original Name:reflectAuthor:tobiasbak
Download