Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
無料GitHub で公開
quick-recap
Use when the user wants each agent response to end with a red/yellow/green status line showing whether the work is finished, pending a follow-up, or blocked on input.
含まれるファイル（1）
- SKILL.md1.3 KB
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.
Activation
The convention applies only while this skill is loaded or the user asks for it.
AOS does not inject a managed AGENTS.md / CLAUDE.md block for it.
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
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新