kit-autopilot

Automate unattended kit planning with multi-account rotation and deterministic restarts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/primovera12/Master-Kit --skill kit-autopilot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kit-autopilot
Source: https://github.com/primovera12/Master-Kit/tree/main/Master-Starter-Kit/tools/skills/kit-autopilot
Command: npx skills add https://github.com/primovera12/Master-Kit --skill kit-autopilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates unattended kit planning by running a self-restarting autopilot that persists through context-window limits and rotates across Claude accounts to avoid rate limits, eliminating manual, around-the-clock planning bottlenecks.

Core Features & Use Cases

  • Overnight execution: plans and progresses steps 3-33 without user input once intake is complete.
  • Multi-account rotation: cycles through pre-authenticated Claude profiles to maximize throughput under rate limits.
  • Status & setup helpers: provides start, pause, status, and setup commands for controlling the autopilot and configuring accounts in batches.

Quick Start

Start the kit autopilot to run unattended overnight with multi-account rotation.

Frequently Asked Questions about kit-autopilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate overnight workflow planning without hitting Claude rate limits?▼

Overnight workflow planning automation is achieved by running a self-restarting autopilot that cycles through pre-authenticated Claude profiles, bypassing rate limits while executing long-running steps without manual input.

How does multi-account rotation work for unattended automation sessions?▼

Multi-account rotation cycles through pre-authenticated Claude profiles to maximize throughput, automatically switching accounts when rate limits are reached to keep unattended automation sessions running continuously.

Can I pause and check the status of an autonomous planning session?▼

Yes, you can pause and check the status of an autonomous planning session using dedicated start, pause, and status helper commands that control the autopilot execution flow.

How does deterministic restart maintain state after a context-window limit crash?▼

Deterministic restarts maintain state by tracking progress through session-context.md, state.json files, and log files, allowing the autopilot to resume long-running planning sessions exactly where they stopped.

Do I need pre-authenticated profiles to set up multi-account automation?▼

Yes, pre-authenticated profiles are required for multi-account automation, configured in batches via the setup helper command to enable seamless rotation across Claude accounts during overnight execution.

What are the limitations of using a self-restarting autopilot for unattended planning?▼

The self-restarting autopilot is limited to executing steps 3-33 after intake is complete, requiring pre-configured authenticated profiles and depending on deterministic state files for recovery during context-window exhaustion.