improving-agent-reflection
Skill2 starsChanged 2 months agoBSD-3-ClauseView on GitHub
Proposes focused, high-value improvements to your active rules and skills. What this does is reflect on the user feedback and guidance, then suggests changes in Cline rules and skills. Use this when you are about to complete a task that involved user feedback provided at any point during the conversation, or involved multiple non-trivial steps (e.g., multiple file edits, complex logic generation).
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- addressing-pull-request-commentsSkill
- analyzing-github-issueSkill
- applying-ruby-conventionsSkill
- applying-test-conventionsSkill
- committing-changesSkill
- creating-pull-requestSkill
- editing-filesSkill
- enforcing-project-rulesSkill
- implementing-github-issueSkill
- running-cli-in-wsl-portableSkill
- syncing-branch-with-baseSkill
- updating-docSkill
- validating-production-qualitySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. About 0 are common, 22 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When improving agent reflection, follow those steps.
- Distinctive: line 16
Before executing anything, create a checklist named improving-agent-reflection Execution Checklist with all steps of these instructions.
- Distinctive: line 18
After completing each step of these instructions, mark the item in the improving-agent-reflection Execution Checklist as completed.
- Distinctive: line 19
Do not skip any item.
- Distinctive: line 20
If an item cannot be executed, explicitly explain why.
- Distinctive: line 21
Never mark the task as completed while any item from the improving-agent-reflection Execution Checklist remains open.
- Distinctive: line 25
Always tell the user "SKILL: I am improving agent reflection" to inform the user that you are running this skill.
- Very specific: line 29
Always use agent: ask_followup_question to ask whether reflection is warranted for this task:
- Distinctive: line 36
If "No - skip", conclude briefly and stop this skill.
- Very specific: line 40
Always use agent: ask_followup_question to confirm the user wants reflection and proposals:
- Very specific: line 51
Always use the agent: read_file tool to read the file AGENTS.md, and all the referenced *..md files referenced from it.
- Very specific: line 61
Always use the agent: list_files tool to list all skills that are present:
- Very specific: line 76
If the content is referencing other files (*.md), always use the agent: read_file tool to read them:
- Distinctive: line 86
Always summarize relevant user feedback (explicit and implicit)
- Distinctive: line 87
Always identify where rules and skills helped or hindered flow
- Distinctive: line 88
Always propose targeted improvements focused on:
- Distinctive: line 96
Always provide a concise list of suggested changes per file (no diff blocks).
- Very specific: line 100
Always use agent: ask_followup_question to ask the user how to proceed:
- Distinctive: line 110
If "Apply now": implement updates for accessible files
- Distinctive: line 111
If "Show recommendations only": present a clean summary for manual application
- Distinctive: line 112
If "Cancel": make no changes
- Distinctive: line 116
Always summarize what changed or what to change next, then finish.
- Distinctive: line 120
Before declaring the task complete:
- Distinctive: line 124
If any step was not executed, execute it now.
- Distinctive: line 128
Do not offer reflection if:
- Distinctive: line 129
No rules or skills were active.
- Very specific: line 134
Always use it every time another skill specifically mentions skill: improving-agent-reflection.
- Distinctive: line 135
Always use it every time the user asks you to improve rules or skills.
- Distinctive: line 136
Always use it before attempting completion of a task that involved user feedback on active skills and rules.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Improving agent reflection
Offer opportunities to continuously improve agent rules and skills, based on user interactions and feedback.
Sequential steps to be followed when using this skill
When improving agent reflection, follow those steps.
Create the improving-agent-reflection Execution Checklist (MANDATORY)
- Before executing anything, create a checklist named improving-agent-reflection Execution Checklist with all steps of these instructions.
- The improving-agent-reflection Execution Checklist must include all numbered steps explicitly.
- After completing each step of these instructions, mark the item in the improving-agent-reflection Execution Checklist as completed.
- Do not skip any item.
- If an item cannot be executed, explicitly explain why.
- Never mark the task as completed while any item from the improving-agent-reflection Execution Checklist remains open.
1. Inform the user
- Always tell the user "SKILL: I am improving agent reflection" to inform the user that you are running this skill.
2. Applicability Check
- Always use
agent: ask_followup_questionto ask whether reflection is warranted for this task:<ask_followup_question> <question>Did this task involve user feedback at any point OR multiple non-trivial steps (e.g., several file edits, complex logic generation)?</question> <options>["Yes - proceed", "No - skip"]</options> </ask_followup_question> - If "No - skip", conclude briefly and stop this skill.
3. Offer Reflection
- Always use
agent: ask_followup_questionto confirm the user wants reflection and proposals:<ask_followup_question> <question>Before I proceed, would you like me to reflect on our interaction and suggest potential improvements to the active rules and skills?</question> <options>["Yes - reflect", "No - skip"]</options> </ask_followup_question> - If "No - skip", conclude briefly and stop this skill.
4. Identify Active Rules
- Always use the
agent: read_filetool to read the fileAGENTS.md, and all the referenced *..md files referenced from it. This file contains rules that are always active.<read_file> <path>AGENTS.md</path> </read_file>
5. Identify Active Skills (Best‑Effort)
- Skills directory:
.cline/skills - Always use the
agent: list_filestool to list all skills that are present:<list_files> <path>.cline/skills</path> </list_files>
6. Load Accessible Skill Files
- For each accessible skill that you want to consider, always use the
agent: read_filetool to read the SKILL.md file of the skill, and all the referenced *..md files referenced from it.<read_file> <path>.cline/skills/{skill-name}/SKILL.md</path> </read_file> - If the content is referencing other files (*.md), always use the
agent: read_filetool to read them:<read_file> <path>.cline/skills/{skill-name}/references/{referenced-file}.md</path> </read_file>
7. Review and Synthesize Opportunities
Using the current task's conversation context:
- Always summarize relevant user feedback (explicit and implicit)
- Always identify where rules and skills helped or hindered flow
- Always propose targeted improvements focused on:
- Addressing user feedback directly
- Improving clarity and conciseness
- Consolidating overlapping guidance
- Removing outdated or low-impact sections
8. Present Proposals
- Always provide a concise list of suggested changes per file (no diff blocks). Keep focus on practical, high-value edits.
9. Approval to Act
- Always use
agent: ask_followup_questionto ask the user how to proceed:<ask_followup_question> <question>Would you like me to apply these improvements now where possible, or just present recommendations?</question> <options>["Apply now", "Show recommendations only", "Cancel"]</options> </ask_followup_question>
10. Execute or Report
- If "Apply now": implement updates for accessible files
- If "Show recommendations only": present a clean summary for manual application
- If "Cancel": make no changes
11. Conclude
- Always summarize what changed or what to change next, then finish.
Final Verification (MANDATORY)
Before declaring the task complete:
- Re-list all numbered steps from the improving-agent-reflection Execution Checklist.
- Confirm each one was executed.
- If any step was not executed, execute it now.
Constraint
Do not offer reflection if:
- No rules or skills were active.
- The task was very simple and involved no feedback.
When to use it
- Always use it every time another skill specifically mentions
skill: improving-agent-reflection. - Always use it every time the user asks you to improve rules or skills.
- Always use it before attempting completion of a task that involved user feedback on active skills and rules.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

