Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yeachan-heo/autopilot
Full autonomous execution from idea to working code
Passed 11 of 17 test cases with the skill, and 3 of 17 without it.
and 13 more in the full report
11 fixed3 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
At Phase 0 entry, project configuration specifies "companyContext.tool": "mcp_internal_docs". What action should be taken regarding project guidelines?
| Checked | Without skill | With skill |
|---|---|---|
| Calls the specified MCP tool with a query summarizing task details and constraints | Missed | Passed |
| Treats returned context solely as advisory context without running it as executable instructions | Missed | Passed |
The instructions your model reads when the skill loads.
<Use_When>
<Do_Not_Use_When>
plan skill insteadralph or delegate to an executor agentplan --review<Why_This_Exists> Most non-trivial software tasks require coordinated phases: understanding requirements, designing a solution, implementing in parallel, testing, and validating quality. Autopilot orchestrates all of these phases automatically so the user can describe what they want and receive working code without managing each step. </Why_This_Exists>
<Execution_Policy>
/oh-my-claudecode:cancel at any time; progress is preserved for resume
</Execution_Policy><Workflow_Profiles>
Select a configured profile only with /autopilot --workflow <name> <task>. A profile is an autopilot-owned stage schedule, not a command, mode, plugin, filename, or separate state identity. Without --workflow, autopilot retains its legacy lifecycle and behavior.
Named workflow profiles require Linux with the flock utility in v1 because their transcript evidence boundary uses Linux no-follow file-descriptor traversal and their recoverable mutation lock uses kernel advisory locking. Unsupported environments reject explicit --workflow activation before state mutation; use legacy autopilot instead.
Profiles are configured in project or user JSONC as autopilot.workflows.<slug>. Every v1 profile has exactly version: 1 and stages; no other profile keys are accepted. The only admitted stage sequences are:
test cases passed, vs 3 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.