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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Make completion state obvious at the end of every response.
Every response that completes a unit of work must end with:
🟢 Actual concise status sentence
Rules:
🟢 when the requested work is finished.🟡 when non-routine follow-up remains; name the pending item.🔴 only when blocked on user input.---, spacer lines, or any content after the status line.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.
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
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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, independently investigate the same problem to form your own hypotheses and approach, inspect what the agent actually changed and verified, compare the two investigations, report gaps and add-on directions, and optionally make scoped fixes when the user authorizes repair.
The English summary is being prepared. Showing the original description.
Open and operate Agent-Native workspace apps through Dispatch MCP, with inline app surfaces, browser-session authentication, and current screen state.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
The English summary is being prepared. Showing the original description.