Quick Recap

From the author

Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions.

— the description by Builder.io

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Quick Recap provides a structured communication protocol for AI agents to signal the completion state of a task. By utilizing a simple red, yellow, or green status block at the end of every response, agents can clearly communicate whether work is finished, requires follow-up, or is blocked by user input. This skill is designed to be integrated into project-level instruction files like AGENTS.md or CLAUDE.md to ensure consistent reporting across interactions.

What it does

Defines a standardized status block format for AI responses
Uses color-coded emojis to represent completion states
Provides clear rules for when to use green, yellow, or red indicators
Supports integration into project-specific instruction files
Ensures status updates are concise and placed at the end of responses

When to use it

When you want to ensure consistent status reporting in agent interactions
When managing complex tasks that require clear hand-offs or follow-up steps
When you need to clearly signal to users when an agent is waiting for input
When configuring project instructions to improve agent communication habits

Advantages

Improves clarity by making completion states immediately visible
Reduces ambiguity regarding whether a task is fully complete or requires action
Standardizes communication patterns across different agent sessions
Easy to implement via project-level configuration files

Usage examples

“Summarize the project status using the quick-recap convention.”: The agent provides a summary and ends with '🟢 Project documentation is fully updated and ready for review.'
“I need to deploy the service, what is the status?”: The agent explains the deployment steps and ends with '🟡 Deployment script ready, please provide the environment variables to proceed.'

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/builderio/quick-recap/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip quick-recap.zip -d .agents/skills

Documentation by Builder.io

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

Files

ATTRIBUTION.mdAdded by AutoGineer847 B
LICENSELicence file added by AutoGineer1.0 KiB
README.md1.4 KiB
SKILL.md1.4 KiB

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Wait What
Matt Pocock· Community
A meta-skill designed to force an agent to re-evaluate and re-pitch its previous output using specific linguistic constraints.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Context Engineering
Addy Osmani· Community
A framework for curating and structuring information to improve AI agent performance and output accuracy.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Prompt Engineering Patterns
Seth Hobson· Community
A collection of patterns and techniques for designing, optimizing, and structuring LLM prompts.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository42.3k
Prompt Engineer
Seth Hobson· Community
An expert prompt engineer providing structured, production-ready prompt designs and optimization strategies for LLMs.
Agent toolingClaude Code
MITGitHub stars of the source repository42.3k
Project Workflow Analysis Blueprint Generator
GitHubOfficial
A generator for creating comprehensive, technology-agnostic prompts to document application workflows and architectural patterns.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository40.9k
Boost Prompt
GitHubOfficial
An interactive workflow for refining and structuring high-quality AI prompts.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository40.9k