Agent skill
Agent workflow review
Review what your agent has been doing and suggest improvements for you to approve.
Use this skill
Install it into a project with the Skills CLI, or read the files below and adapt them to your own agent.
npx skills add shan8851/agent-skills --skill agent-self-improvementSKILL.md
View this file on GitHub---
name: agent-self-improvement
description: Weekly propose-only review that analyzes dumps, memory, context, skills, and crons to suggest agent workflow improvements.
---
# Agent Self-Improvement (Weekly)
Use when running a weekly improvement pass for agent behavior and workflow quality.
## Purpose
Produce evidence-backed, propose-only recommendations to improve workflows, context alignment, and automation hygiene.
## Trigger
- Weekly cadence (recommended via playbook/cron wrapper)
- Or manual run on demand
## Required sources
- `workspace/memory/**`
- `workspace/dump/**`
- Core context files: `SOUL.md`, `IDENTITY.md`, `USER.md`, `MEMORY.md`, `AGENTS.md`, `TOOLS.md`, `HEARTBEAT.md`
- Installed skills (for overlap/gap checks)
- Cron inventory
## Output contract
Return one concise weekly report with these sections:
1. Top recurring friction/failure themes
2. Candidate workflow improvements
3. Candidate cron/automation suggestions
4. Candidate new ideas
5. Context alignment suggestions
6. Kill/merge/tune hygiene suggestions
7. Recommended priority set for next week
## Item quality rules
Every recommendation must include:
- evidence (where it came from)
- why it matters now
- first 30-minute move
- pragmatic score: impact / recurrence / effort / confidence (H/M/L)
## Operating mode
- **Propose-only**
- Do not auto-edit core files
- Do not auto-create/update/delete crons
- Do not auto-send external/internal messages
## Format
Use the exact report structure in `references/report-template.md`.
Apply scoring guidance in `references/scoring.md`.
references/report-template.md
View this file on GitHub# Weekly Agent Self-Improvement Report Template
## 1) Top recurring friction/failure themes
- Theme:
- Evidence:
- Why now:
## 2) Candidate workflow improvements (top 3)
- Proposal:
- Evidence:
- First 30-minute move:
- Score: impact (H/M/L), recurrence (H/M/L), effort (H/M/L), confidence (H/M/L)
## 3) Candidate cron/automation suggestions (top 3)
- Proposal:
- Evidence:
- First 30-minute move:
- Score: impact (H/M/L), recurrence (H/M/L), effort (H/M/L), confidence (H/M/L)
## 4) Candidate new ideas (top 3)
- Idea:
- Evidence:
- First 30-minute move:
- Score: impact (H/M/L), recurrence (H/M/L), effort (H/M/L), confidence (H/M/L)
## 5) Context alignment suggestions (top 3)
- Suggestion:
- Evidence:
- Why this aligns better:
- First 30-minute move:
## 6) Kill / merge / tune hygiene suggestions
- Kill:
- Merge:
- Tune:
## 7) Recommended priority set for next week
- Priority 1:
- Priority 2:
- Priority 3:
references/scoring.md
View this file on GitHub# Pragmatic Scoring
Use H/M/L only.
- **Impact**: expected value if adopted
- **Recurrence**: how often this issue/opportunity repeats
- **Effort**: implementation effort (H = expensive, L = cheap)
- **Confidence**: quality of evidence supporting recommendation
Guidance:
- Prioritize high impact + high recurrence + low/medium effort.
- If confidence is low, include a short validation step before full adoption.