auto

Route user subcommand requests to the correct Autopus workflow surface.

106|74|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Insajin/autopus-adk --skill auto-insajin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto
Source: https://github.com/Insajin/autopus-adk/tree/main/.autopus/plugins/auto/skills/auto
Command: npx skills add https://github.com/Insajin/autopus-adk --skill auto-insajin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and dispatch user requests to the correct Autopus sub-workflow (e.g., setup, status, plan, go, fix, review, sync, idea, map, why, verify, secure, test, dev, canary, doctor) so complex automations load the right context and run the appropriate routine.

Core Features & Use Cases

  • Thin router surface that delegates to specialized workflows: auto-setup, auto-status, auto-plan, auto-go, auto-fix, auto-review, auto-sync, auto-idea, auto-map, auto-why, auto-verify, auto-secure, auto-test, auto-dev, auto-canary, auto-doctor.
  • Context-aware: resolves SPEC paths and loads project context files before execution to ensure correct scope.
  • Flexible invocation: supports both @auto and $auto forms and automatically wires to the corresponding detailed surface.

Quick Start

Ask @auto to run plan for a SPEC and route execution to the appropriate detailed workflow surface.

Frequently Asked Questions about auto

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

FAQPage Schema
How do I route automation commands to the correct workflow without losing project context?

The auto router resolves SPEC paths and loads project context before delegating user commands to the appropriate specialized workflow surface for execution.

What is the best way to dispatch sub-commands like plan and go to specialized workflows?

Using a thin router surface allows you to dispatch sub-commands like plan and go, automatically delegating them to dedicated sub-skills such as auto-plan and auto-go.

How does context loading work before executing a delegated workflow routine?

Context loading works by resolving SPEC paths and loading project context files prior to execution, ensuring the delegated workflow routine operates within the correct scope.

Can I use different invocation formats to trigger the routing workflow?

Yes, you can trigger the routing workflow using both @auto and $auto invocation forms, which automatically wire to the corresponding detailed workflow surface.

Does the workflow router support dynamic loading for different automation surfaces?

The workflow router supports dynamic loading of the appropriate workflow surface, handling Codex invocation and sub-skill delegation to ensure consistent context across routines.

When should I avoid using a thin router for sub-skill delegation?

You should avoid using a thin router for sub-skill delegation if your automation task does not require resolving SPEC paths or loading complex project context before execution.