builderio/skills

quick-recap

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.

First seen Jun 11, 2026

Installation

$ npx skills add builderio/skills --skill quick-recap

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from builderio/skills · top by installs.

npx skills add builderio/skills

Browse all from builderio/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4.2K
License LICENSE
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,420 B
  • docs SUMMARY.md 386 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 535 installs

SKILL.md

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