autopilotlisted

Use to run autonomous work on ANY project until a goal is actually met — «працю�� автономно», «продовжуй», /loop, a Ralph-style loop, an unattended campaign, or setting a repo up so an agent can drive it. Code, documents, data, research, infrastructure, ops: it discovers what «done» means here, arms itself with the skills AND the reach the work needs (public skills, MCP servers, plugins, connectors — writing the MCP server when none exists), and iterates as a real process that stops on a STOP file, a budget or thrash. Steerable mid-flight, carryable by launchd/cron/CI so it outlives the session, and on a full context it checkpoints into its ledger and compacts instead of stopping. Every check is run by something that is not writing the summary; every criterion is verified by someone that is not you; every win, failure and decision is recorded, and repeated wins become new skills.
vladyslav-betterme/autopilot-skill · ★ 1 · Data & Documents · score 72

Install: claude install-skill vladyslav-betterme/autopilot-skill

# Autopilot An autonomous loop that is portable because it **asks the work what «done» means** instead of assuming — and does not stop until that answer is satisfied. Three claims this skill exists to make impossible: - «It works» when nothing ran it. - «It's done» when the only judge was the one who did it. - «I worked on it» with no record of what was tried, what failed, and why. The subject does not matter. A refactor, a migration, a report, a dataset, a render farm, a cluster: the loop below is identical and only the **check** differs. ## 0. Bootstrap — once per project `<skill>` below is the directory this file sits in — `.agents/skills/autopilot` after a CLI install, or wherever it was cloned. Run everything from the PROJECT root. ```bash node <skill>/scripts/discover.mjs # checks, memory homes, danger signals node <skill>/scripts/bootstrap.mjs # creates the ledger if absent node <skill>/scripts/skills.mjs # the skill library — pick this project's niches node <skill>/scripts/tools.mjs # what this machine can already REACH: MCP servers, plugins ``` `discover` prints the project's own check command. **That command is the definition of done for every iteration below.** If it prints `checks: []`, **do not believe it yet.** Discovery only reads files that declare a check; a project's real check is often named in prose. Grep every path it listed in `memoryHomes`, plus the README and CI config, for a runnable command — one project's `ch