Skills / fleet-dispatcher / Alternatives
Other · 12 alternativesfleet-dispatcher is dispatches work to headless worker machines and checks on them using project-local fleet state. Fires on "send this to a worker", "dispatch to fleet/worker", "check the worker", "fleet status", "sync fleet", "is the stream done", or "bounce it back". Provider-neutral. Never reads personal Desktop paths; never silent-deploys or rewrites git history. Below are the other other skills in the directory, with the 1 that have a published proof first. A proof means the skill was run on a fixed brief with and without it and both results are online, so you can judge the output rather than the star count.
internal-comms has proofs you can open now. If you want evidence before installing, pick from those. If you need something more specific to your stack, the rest of the list is ranked by how widely the source repository is used. fleet-dispatcher does not have a proof yet; its author can order one for $49.
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
Replace with description of the skill and when Claude should use it.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Use when executing implementation plans with independent tasks in the current session
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 starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
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
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
Gate fine-tuned checkpoints with drift budgets, paired comparison, and forgetting checks before promotion. Use after a training run produces a checkpoint, when deciding whether a tuned model ships, or when a promoted model needs re-gating against updated goldens.
Skills belong to their authors. Descriptions are taken from each SKILL.md, star counts from the source repository, and nothing here is paid placement. See the whole category: best other skills.
Use This Skill