Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
FreePublished on GitHub
pb-handover
Write a handover note for a colleague from the state of a project folder: what is done, what is open, what is risky, the next 3 steps and where things live. Sent only after your GO. Use for "handover note", "hand this project over", "I'm going on leave, brief my colleague".
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md2.5 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Handover note
What you get: a handover note for a colleague from the state of a project folder.
Inputs
- A project folder
- The colleague's name
- A save folder — asked once; default
./pb-handover-<date>/
Steps
- Ask once — save folder, project folder, colleague name →
run-log.md— the folder exists - Read the folder and its git log (read-only); github — only if
gh (external)is installed: your open pull requests for this repo → list of files, recent commits and open PRs inrun-log.md— if gh is missing, skipped and logged - quick-recap — folder state and recent commits → what is done, what is in progress — each point cites a file or commit
- memb-skill — search open commitments for this project → added tagged
[memB]— skipped and logged if memB is not installed - Write
handover.md: done, open, risks, next 3 steps, where things live — every open item cites a file, commit or PR; nothing invented, unknown is? - Show
handover.mdin full and apply your edits until you approve — approval logged - [GO] Send the handover through a connector you name, or send it yourself — show the recipient (name + address,
?blocks sending until you fill it) and the full text first. The run stops here until the human types GO. The GO covers exactly the recipient and message shown and nothing else; a different or added recipient needs a fresh GO. The go-gate hook does not guard sending: this [GO] is the only guard.
Run log: run-log.md in the save folder. One line per step as it completes (N. done|skipped|failed — file — check result), and WAITING FOR GO: <step> at the gate. Anything other than the literal GO (case-insensitive) is not a GO. If a check fails, stop, write the failure into the log and tell the user.
Reviews
No reviews yet. Tell others what you thought.
Comments
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.
More skills from this repository
agent-memory-mcp
FreeUse when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
agent-pipeline
FreeReference 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.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
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.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
agenttrail
Freeagenttrail: 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.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026