quick-recap
BuilderIO/skills
在每次响应结束时,通过红色/黄色/绿色状态块清晰显示完成状态。
...展开全部简要回顾
在每次响应的结尾处明确显示完成状态。
状态块
每个完成一项工作的响应都必须以以下内容结尾:
🟢 Actual concise status sentence
规则:
- 状态行长度应控制在100个字符以内。
- 当
🟢表示所请求的工作已完成。 - 当
🟡表示仍有非常规后续工作;请说明待办事项。 - 仅在
🔴仅在因用户输入而受阻时使用。 - 将状态行放在响应的最后。
- 请勿在
---、分隔行或任何内容。
安装程序的行为
只有当项目或用户
说明中包含此约定时,它才会自动生效。安装此技能时,应优先添加受管
AGENTS.md / CLAUDE.md ,除非用户选择不使用。
如果您是手动遵循该约定,请从用户的 角度选择状态:已完成、正在等待某个非例行步骤,或被阻塞。
示例
已完成的工作:
🟢 Updated quick recap docs with output examples
尚有非常规后续工作:
🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks
因用户输入而受阻:
🔴 Need the production API key to continue
---
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
```





首页
