autopilot-loop
Run an autonomous /loop iteration -- check progress, work on next task, schedule next wake
Profile →npx skills add ruvnet/ruflo --skill autopilot-loop --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Run one autopilot iteration using Claude Code's native /loop: 1. Check status: `mcp__plugin_ruflo-core_ruflo__autopilot_status` 2. If all tasks complete or max iterations reached, call `mcp__plugin_ruflo-core_ruflo__autopilot_disable` and stop 3. Get prediction: `mcp__plugin_ruflo-core_ruflo__autopilot_predict` for the optimal next action 4. Execute the predicted task (spawn agent, edit code, run tests, etc.) 5. Log via `mcp__plugin_ruflo-core_ruflo__autopilot_log` 6. Schedule next: `ScheduleWakeup({ delaySeconds: 270, reason: "next autopilot iteration" })` ### Cache-Aware Scheduling Always use delay 270s (under 300s cache TTL) to keep the prompt cache warm between iterations. ### Task Sources Autopilot discovers tasks from: - **team-tasks**: Claude Code TaskList entries - **swarm-tasks**: MCP task_list entries - **file-checklist**: Markdown checkbox items in tracked files Configure: `mcp__plugin_ruflo-core_ruflo__autopilot_config({ taskSources: ["team-tasks", "swarm-tasks"] })`
- Cache-Aware Scheduling
- Task Sources
What does the autopilot-loop skill do?
Run an autonomous /loop iteration -- check progress, work on next task, schedule next wake
How do I install it?
Run `npx skills add ruvnet/ruflo --skill autopilot-loop --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.