Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月11日 更新
無料GitHub で公開
pb-focus-chunks
Split one big task into chunks of at most 25 minutes, each with a done-check, and place the demanding ones in your high-energy hours. Use for "split this task", "break it into chunks", "I can't start this", "focus plan". Nothing leaves your computer.
含まれるファイル（1）
- SKILL.md1.9 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Focus chunks
What you get: one big task split into 25-minute chunks, ordered by your energy level, each with a done-check.
Inputs
- One task, in your own words, with your total time estimate
- Your energy pattern — asked once, e.g. morning high / afternoon low
- A save folder — asked once; default
./pb-focus-chunks-<date>/
Steps
- Ask once — save folder, task, total estimate, energy pattern →
run-log.md— all answered - concise-planning — task and estimate →
chunks.md: numbered chunks of at most 25 minutes, each with minutes, a done-check and an energy tag (high / low) — every chunk is <= 25 min and has a done-check; the minutes add up to your estimate - Order
chunks.mdso high-energy chunks fall into your high-energy slots and low-energy chunks into the rest → slot named per chunk — no high-energy chunk sits in a low slot - Show
chunks.mdin full and apply your edits until you approve — approval logged
Nothing in this plan is sent anywhere, so there is no GO step. It only writes into the save folder.
Run log: run-log.md in the save folder. One line per step as it completes (N. done|skipped|failed — file — check result). If a check fails, stop, write the failure into the log and tell the user.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月11日 更新
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月11日 更新
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月11日 更新
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月11日 更新
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月11日 更新