autopilot-predict
Use learned patterns and current state to predict the optimal next action
Profile →npx skills add ruvnet/ruflo --skill autopilot-predict --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.
Predict what to work on next using Ruflo autopilot intelligence: 1. Call `mcp__plugin_ruflo-core_ruflo__autopilot_predict` for the recommended next action 2. If confidence > 0.7, execute the prediction directly 3. If confidence < 0.7, check `mcp__plugin_ruflo-core_ruflo__autopilot_progress` for task breakdown 4. Pick the highest-priority incomplete task 5. After completing work, call `mcp__plugin_ruflo-core_ruflo__autopilot_learn` to update patterns ### Learning Pipeline - `mcp__plugin_ruflo-core_ruflo__autopilot_learn` -- discover success patterns from completed tasks - `mcp__plugin_ruflo-core_ruflo__autopilot_history({ query: "KEYWORD" })` -- search past completions - Patterns are stored in AgentDB for cross-session recall ### Integration with /loop When running inside a `/loop`, the predict skill guides each iteration: - High confidence prediction -> execute immediately - Low confidence -> fall back to task list priority order - No tasks remaining -> disable autopilot and exit loop
- Learning Pipeline
- Integration with /loop
What does the autopilot-predict skill do?
Use learned patterns and current state to predict the optimal next action
How do I install it?
Run `npx skills add ruvnet/ruflo --skill autopilot-predict --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.