Community编程与开发github.com

BuilderIO/快速总结

在每次响应的末尾使用红/黄/绿状态块来明确任务完成状态,尤其适用于安装受管理的 AGENTS.md 或 CLAUDE.md 指令时。

快速总结 是什么?

这个 AI 代理技能旨在强制在每次响应结束时使用标准化的状态块,使任务的完成状态一目了然。它通过引入红、黄、绿三种颜色状态(🟢 完成、🟡 后续待办、🔴 阻塞)来替代模糊的描述,帮助用户和 AI 快速理解当前工作的进展。该技能主要面向 Claude Code、Cursor 等支持代理工作流的平台,其核心机制是要求每条消息末尾附加一个简短的状态行,并规定了严格的格式限制(如少于 100 字符、禁止后续内容)。技能本身是“安装器行为”——当它在项目的 `AGENTS.md` 或 `CLAUDE.md` 文件中出现时,代理会自动遵循该约定;否则用户可以手动遵循。通过这种方式,它极大提升了代理响应的清晰度、可读性和协作效率。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/BuilderIO/skills/tree/main/skills/quick-recap

Installed? Explore more 编程与开发 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

快速总结 是做什么的?

在每次响应的末尾明确任务的完成状态。

状态块

每个完成某项工作的响应必须以如下格式结尾:

🟢 实际简洁状态描述

规则:

  • 状态行保持 100 字符以内。
  • 工作完成时使用 🟢。
  • 非例行后续待办时使用 🟡;指明待办事项。
  • 仅在因用户输入阻塞时使用 🔴。
  • 状态行必须放在响应的最末尾。
  • 状态行后不要添加 ---、分隔行或其他任何内容。

安装器行为

此约定仅在项目或用户指令中存在时自动启用。安装此技能时,除非用户明确拒绝,否则优先添加受管理的 AGENTS.md/CLAUDE.md 块。

如果你手动遵循此约定,请从用户的角度选择状态:完成、待处理特定非例行步骤或阻塞。

示例

工作完成:

🟢 更新了快速总结文档,包含输出示例

非例行后续待办:

🟡 代码已更新,测试 webhook 前请设置 PROVIDER_WEBHOOK_SECRET

因用户输入阻塞:

🔴 需要生产环境 API 密钥才能继续

Individual skills in this repo

This repo contains 10 individual skills — each has its own dedicated page.

BuilderIO/adding-a-skill

Use in the BuilderIO/skills repo whenever adding, updating, publishing, documenting, validating, or wiring a public skill. Covers the repo-local skill files, root catalog docs, plugin metadata, @agent-native/skills dynamic install path, optional managed AGENTS/CLAUDE instruction blocks in ../agent-native/framework, and generated/synced Plan skill gotchas.

BuilderIO/agent-watchdog

Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, inspect what the agent actually changed and verified, report gaps, and optionally make scoped fixes when the user authorizes repair.

BuilderIO/efficient-fable

Use when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy lifting.

BuilderIO/efficient-frontier

Apply the same orchestration as `/efficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.

BuilderIO/plan-arbiter

Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.

BuilderIO/plow-ahead

Use when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done", "finish while I am away", "do not ask questions unless truly blocked", or similar. Convert ordinary ambiguity into stated assumptions, proceed through implementation and validation, stop only for true blockers, and end with a clear recap of decisions, changes, verification, and residual risk.

BuilderIO/read-the-damn-docs

Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces Codex to web-search for current official docs and read primary docs before assuming from memory.

BuilderIO/stay-within-limits

Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.

BuilderIO/visual-plan

Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.

BuilderIO/visual-recap

Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.

相关技能