option

quick-recap

BuilderIO/skills BuilderIO/skills

Makes completion state obvious at the end of every response using a red/yellow/green status block.

...Expand all
0
Updated time September 6, 2026

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
View on GitHub
---
name: quick-recap
description: Makes completion state obvious at the end of every response using a red/yellow/green status block.
---

# 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:

```md
🟢 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:

```md
🟢 Updated quick recap docs with output examples
```

Non-routine follow-up remains:

```md
🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks
```

Blocked on user input:

```md
🔴 Need the production API key to continue
```

All Files

0 files

Install quick-recap

Download and extract the skill files to your .claude/skills/ directory.

Download ZIP

Clone the repository and copy the skill files to your project.

git clone https://github.com/BuilderIO/skills/tree/main/skills/quick-recap # Copy SKILL.md to your .claude/skills/ directory

Copy Copy
Quick Setup: Copy the skill folder to .claude/skills/ Claude will automatically detect and use the skill
Repository BuilderIO/skills

Related Skills

notion-automation
Updated time June 29, 2026
airtable-automation
Updated time June 29, 2026
seo-programmatic
Updated time June 29, 2026
revops
Updated time June 29, 2026
OR