auto-setup

Redirect alias invocations to the canonical auto workflow while preserving flags.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns alias invocations with the canonical auto workflow by loadable routing through the auto skill, minimizing setup friction and ensuring consistent behavior across environments.

Core Features & Use Cases

  • Thin alias shim that preserves flags and forwards to the detailed workflow.
  • Canonical router surface for the Autopus plugin, enabling seamless handoff to the full setup process.
  • Use Case: developer wants to initialize project context and load ARCHITECTURE.md and .autopus/project docs via the detailed workflow.

Quick Start

Invoke the alias shim with your preferred flags to load the full auto workflow.

Frequently Asked Questions about auto-setup

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

FAQPage Schema
How do I route an alias to a canonical workflow in an automation setup?

A thin alias shim redirects alias invocations to a canonical workflow by resolving context and loading the detailed router. It seamlessly hands off to the advanced setup process while preserving all passed flags.

What is an alias shim and how does it handle setup flags?

An alias shim is a lightweight routing layer that redirects invocations to a canonical workflow. It preserves all passed flags to ensure full control over the setup behavior without adding overhead.

Can I initialize project context and load ARCHITECTURE.md through an automated workflow?

Yes, you can initialize project context and load ARCHITECTURE.md and .autopus/project docs by invoking the alias shim. It routes the request to load the full auto workflow for detailed setup.

Does the Autopus plugin setup require any specific dependencies?

No, the Autopus plugin setup does not require specific dependencies. The lightweight alias shim operates within the autopus-adk project to load the canonical router without external requirements.

Why does my alias invocation not preserve flags during workflow routing?

If your alias invocation does not preserve flags during routing, you may be bypassing the canonical router. A proper alias shim ensures all passed flags are forwarded to maintain full setup control.