Quick Recap

Make completion state obvious at the end of every response.

Status Block

Every response that completes a unit of work must end with:

🟢 Actual concise status sentence

Rules:

Keep the status line under 100 characters.
Use 🟢 when the requested work is finished.
Use 🟡 when non-routine follow-up remains; name the pending item.
Use 🔴 only when blocked on user input.
Put the status line at the very end of the response.
Do not add ---, spacer lines, or any content after the status line.

Installer Behavior

This convention is only automatic when it is present in project or user instructions. When installing this skill, prefer adding the managed AGENTS.md / CLAUDE.md block unless the user opts out.

If you are following the convention manually, choose the status from the user's perspective: finished, pending a specific non-routine step, or blocked.

Examples

Finished work:

🟢 Updated quick recap docs with output examples

Non-routine follow-up remains:

🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks

Blocked on user input:

🔴 Need the production API key to continue

Files2

2 files · 2.5 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Safety

95

Quality

85

Clarity

90

Completeness

82

Summary

Quick Recap is a lightweight convention skill that adds a simple red/yellow/green status footer to agent responses to make completion state obvious. It defines clear rules for when to use each emoji status and provides guidance for manual adoption or automated installation into project instructions.

Detected Capabilities

prompt instruction modificationconvention definitiondocumentation generation

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

status footerresponse summarywork completion trackingagents.md setupquick status signal

Use Cases

) Clarifying agent work completion status in multi-agent projects where long responses make progress unclear
Adding visual status signals to responses for better UX and task tracking
Installing a managed convention into AGENTS.md or CLAUDE.md for automatic status footer behavior
Communicating when work is finished, pending a specific non-routine item, or blocked on user input

Quality Notes

Skill correctly focuses on response formatting conventions rather than code operations
Clear, concise rules for emoji status meanings with practical examples
Well-documented use cases and installation instructions
Provides both manual adoption path and automated installer guidance
README and SKILL.md are consistent and complementary

Model: claude-haiku-4-5-20251001Analyzed: Jul 11, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

quick-recap