Claude Skills by hybridlabor-api

Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Superseded AOS-era version of the writing-plans skill, kept for reference and for its terse plan template. Prefer `writing-plans` (superpowers v6.4.2) for all new plans: it adds a spec-coverage self-review, per-task interface contracts, and a Review Focus section. Reach for this one only when you specifically want the shorter template or are comparing the two.

Turn a GitHub issue into a tested fix on a branch with an open PR: read the issue as the contract, find the root cause, write the failing test first, fix, prove it, review the diff against the issue, push and open the PR only after GO. Merging stays with pb-ship. Use for "fix issue 42", "bug fix from this issue", "turn this issue into a PR".

Fix red CI or set up GitHub Actions end to end: read the failing run, find the root cause, patch and validate the workflow, push only after GO, and watch the run go green on the pushed commit. Use for "CI is red", "the build fails on GitHub", "set up CI for this repo", "fix the workflow".

Turn a look brief and reference images into a finished social clip: concept, TouchDesigner look and palette, ComfyUI stills, a recorded take, a cut in DaVinci Resolve or Remotion, 9:16 and 16:9 exports, publish only after GO. Use for "moodboard to clip", "make a social clip from these references", "look brief to video".

Build a crew call sheet and a load-in / load-out plan for one show day from your event tracker or brief and your crew list, and send it to the crew only after your GO. Use for "call sheet", "crew call times", "load-in plan", "load-out schedule".

Deploy a SaaS app to the BDB fleet: preflight of the fleet skills, a guardrail plan, green CI, the deploy after GO (Incus via Forgejo CI, or direct rsync), and a health URL check. Use for "deploy this to the fleet", "deploy the SaaS app", "ship to the Incus instance".

Publish a project's docs as a static HTML manual on GitHub Pages: check that Pages is enabled, bring the wiki up to date, list the doc gaps, build the site, preview it locally and push it after GO. Use for "publish the docs", "docs site", "put the manual on GitHub Pages".

Build one spreadsheet for an event covering guests, vendors, timeline and budget, from your event brief and vendor list, and draft the vendor messages for your GO. Use for "event tracker", "plan this event", "track vendors and budget", "event spreadsheet".

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.

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".

Change the agent harness itself (AOS, AO or CBS hooks, gates, memory, permissions, delegation, plugins, bootstrap) the safe way: look up the matching harness pattern, design against its gotchas, build with /startcycle and a live trail, check every harness, open a PR after GO. Use for "change a hook", "fix the go-gate", "harness work", "plugin change".

Weekly health report over the BDB repos: git and npm version drift and CI status as an HTML report with auto-remediation off, red CI routed to pb-ci-fix, non-release remediation steps run one at a time after GO. Use for "weekly health check", "ecosystem health", "are all repos green and in sync".

Turn an idea into a deployed prototype: a spec from brainstorming, a visual plan of the ComfyUI workflow, a prototype built with startcycle, one hero image, green CI, then push and deploy after separate GOs. Use for "idea to launch", "from idea to a live prototype", "build and deploy this idea".

Turn one reference image into a cleaned, scaled 3D asset: your own image-to-3D ComfyUI workflow makes the mesh, Blender decimates it to a poly budget, fixes scale, origin and material, and exports a .glb. Use for "image to 3D", "make a 3D model from this picture", "photo to glb".

Sort an email backlog into reply, delegate, archive and ignore, and draft the replies. Nothing is sent without your GO. Use for "inbox zero", "sort my mail", "clear my email backlog", "draft replies to my mail".

Check invoices and receipts line by line against your offers and list what matches, what differs and what has no offer. Nothing is paid or sent. Use for "check my invoices", "match invoices to offers", "does this invoice match the quote".

Build and launch a landing page: confirmed copy without invented claims, a generated page in your brand tokens, UI and SEO review, deploy only after GO, then a check on the live URL. Use for "landing page", "launch page for this product", "ship a one-pager".

Turn a live app or landing page into a short launch video: composition brief, render in Hyperframes or Remotion, an ffprobe check per format, publish hand-off only after GO. Use for "launch video", "make a video of the shipped app", "promo clip for the landing page".

Bring a new machine to a verified AOS installation: read-only doctor baseline, install after GO, MCP servers wired per harness with the configs backed up first, memB and OpenWiki checks, and a second doctor run for the delta. Use for "set up this machine", "onboard a new computer", "install AOS on this laptop".

Run one control session over several Claude Code, Codex or OpenCode sessions: roster, status board, GO board, GO <session> tokens, idle notices and a handover file. Use for "master session", "supervise my sessions", "run several agents", "one control window".

Turn a meeting transcript into clean notes, the decisions, and who does what by when, then draft the follow-up mail and send it only after your GO. Use for "meeting notes", "action items from this meeting", "who did what in this transcript", "who does what after the call".

Turn a pb-ship recap, a changelog range or a quick recap into a newsletter email draft where every claim cites a source line, and send it only after GO. Use for "newsletter from the recap", "write the release newsletter", "email update from the changelog".

Draft a client offer with line items priced only from your price list, and send it only after your GO. Use for "write an offer", "quote for this client", "draft a quote", "price this job".

Prepare a project for open sourcing: a sanitized fork with secrets and internal references stripped, a sanitizer verdict, README and LICENSE, then a new PRIVATE GitHub repo created and pushed only after GO. The playbook never makes the repo public. Use for "open source this project", "make a sanitized fork", "prepare a public release".

From a KiCad board to a parametric enclosure that fits it: ERC and DRC clean, board dimensions extracted, an OpenSCAD case with your clearance, Gerbers exported, fab hand-off only after GO. Use for "PCB to enclosure", "case for this board", "KiCad to OpenSCAD case".

Start a new private GitHub project the AOS way: create the private repo, bootstrap AOS (project card, AGENTS.md, wiki, memory, CI choice), push after GO, and confirm the first CI run is green and the repo is still private. Use for "new project", "start a repo", "bootstrap a project".

Overhaul one app's UI against an audit: UX audit and UI review of the running app, current versus proposed design tokens, a before/after visual plan, a startcycle build, point fixes, accessibility and browser tests, delivered as a PR after GO. Use for "redesign this app", "design overhaul", "audit and fix the UI", "give the app a new look".

Release a new AOS version to npm through the release-please PR: check the commit subjects, review and gate the release PR, merge it only after GO, watch the release workflow and check version drift. Use for "release AOS", "cut an AOS release", "merge the release PR", "publish a new AOS version".

Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".

Ship the day's work in one repo: triage new issues, review every open PR (description, visual recap, adversarial reviewer, shipping pre-flight and quality gate), merge only after GO, then post a status recap. Use for "ship it", "ship day", "merge the ready PRs", "end of work block".

Build a show across lights (grandMA3), media (Resolume) and generative visuals (TouchDesigner) from one cue list, offline first. A lane whose console or app is not running is skipped and logged while the others continue; the live rig is touched only after GO. Use for "build the show", "cue list to grandMA3 Resolume and TouchDesigner", "show programming".

Turn a release or ship recap into a social pack: posts per platform where every claim traces to a facts file, clip cut-downs per aspect ratio cut with ffmpeg and checked with ffprobe, hand-off for publishing only after GO. Use for "social pack for the release", "posts and clips for this launch", "announce the release".

Turn one sentence into a task line in the right to-do list, with project, priority and optional due date. Use for "add a to-do", "remember to ...", "put this on my list", "quick task". Nothing leaves your computer.

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.

Clean up git worktrees across your repos: list every worktree, classify it as merged, remote-only, local-only or dirty, recap what each holds, and remove only the merged clean ones after GO. Use for "clean up worktrees", "what is in my aos-wt folders", "land my worktrees", "prune worktrees".