structured-progress-update
Use this skill when summarizing progress on an ongoing project or multi-step task. Give a clear, scannable status report whenever asked for an update or at the end of a work session.
68
Quality
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Structured Progress Update
When reporting on work in progress, use a consistent structure:
Format:
- Done: List completed items concisely.
- In progress: What is currently being worked on and expected completion.
- Blocked: Any items waiting on external input — state exactly what is needed.
- Next: The immediately next action item.
Principles:
- Be specific:
Completed API integration for /users endpointnotworked on API. - Surface blockers proactively — don't wait to be asked.
- Keep it scannable: bullets over paragraphs.
- Repository
- aiming-lab/MetaClaw
- Commit
922caf3
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.