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.
- License 许可
- CC0-1.0
- 最近更新
- 2026-09-07
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- quick-recap
- description
- 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.
02 资源文件 1
- 参考文档README.md1.4 KB
03 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
04 同仓库更多 Skills
implement-skill
Resolves a named FE7 skill to its file pack and edits only those paths. Use when the user wants to implement, enable, port, wire, fix, add, install, or debug a skill (Nullify, Provoke, Adept, etc.).
documentation-style-docs
Use when creating or updating project documentation in the same architecture and writing style as FogStages.md: title + visual block, index, introduction, implementation plan, code locations table, TODO, and limitations/bugs. Trigger on requests like create docs, write documentation, add design document, feature spec, system write-up, or architecture note.
caveman
Ultra-compressed communication AND thinking. Always use extreme (ultra) caveman to minimize tokens in both reasoning and replies. Cuts output ~65% and thinking tokens by skipping recap, option-lists, and filler thought. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", "extreme caveman", or invokes /caveman. Also auto-triggers when token efficiency is requested.
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.
implement-skill
Resolves a named FE7 skill to its file pack and edits only those paths. Use when the user wants to implement, enable, port, wire, fix, add, install, or debug a skill (Nullify, Provoke, Adept, etc.).
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.