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-week-plan
Turn your scattered to-do lists and notes into one prioritised plan for the week, with at most 3 must-do items per day. Use for "plan my week", "what should I do this week", "sort my to-dos", "weekly plan from my notes". Nothing leaves your computer unless you opt in to steps 4 or 8.
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.
Plan my week
What you get: one prioritised plan for this week, built from your scattered to-do lists and notes.
Inputs
- Folders with your to-dos and notes — you name them
- A calendar file (.ics) — optional, exported from your calendar app
- A save folder — asked once; default
./pb-week-plan-<date>/
Steps
- Ask once — save folder, folders with to-dos and notes, optional calendar file →
run-log.md— the folders exist - Read the to-dos and notes →
inbox.md, every open item with its source file and line — at least one item, otherwise stop and ask - memb-skill — search open commitments and deadlines → added to
inbox.mdtagged[memB]— skipped and logged if memB is not installed - github — only if you opt in and
gh (external)is installed: your own open pull requests → added toinbox.md— your choice recorded - Read the calendar file →
calendar.mdwith the fixed appointments — skipped if none was given - concise-planning —
inbox.mdandcalendar.md→week-plan.md, per day Must (max 3), Should, Could — every line traces to a line ininbox.mdorcalendar.md; nothing invented - Show
week-plan.mdin full and apply your edits until you approve — approval logged - memb-skill — optional, ask first: store the approved Must items — memory ids logged
Nothing in this plan is sent anywhere, so there is no GO step. It only reads the files you named and writes into the save folder, except the opt-in steps 4 (gh queries GitHub) and 8 (writes memB).
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.
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