auto-go

Reinterpret `$auto-go` alias invocations as `@auto go` to route to the canonical router.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a thin alias shim that reinterprets the $auto-go request to load the canonical router and delegate to the detailed auto workflow, ensuring branding and context restoration are handled by the underlying skill.

Core Features & Use Cases

  • Reinterprets alias invocations like $auto-go into @auto go to route to the canonical router.
  • Preserves all flags and subcommand arguments to maintain expected behavior during delegation.
  • Delegates to the detailed auto workflow after context load and SPEC path resolution for end-to-end execution.

Quick Start

Invoke the alias with your arguments to load the canonical router and defer to the auto workflow.

Frequently Asked Questions about auto-go

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

FAQPage Schema
How do I set up an alias to route commands to a canonical workflow router?

An alias shim reinterprets command invocations like `$auto-go` into `@auto go` to route them to a canonical router. This delegates execution to the detailed workflow while preserving flags and handoff arguments for end-to-end automation.

What is a command alias shim and how does it handle workflow delegation?

A command alias shim is a minimal, failsafe mechanism that reinterprets an alias surface to load a canonical router. It delegates to a detailed workflow after context load and SPEC path resolution, preserving subcommand arguments during the handoff.

Do I need to install dependencies to use a thin alias shim for automation routing?

No dependencies are required to use this thin alias shim for automation routing. It provides a minimal mechanism that directly reinterprets your alias invocation to load the canonical router and defer to the underlying auto workflow.

Does the command alias preserve flags and subcommand arguments during workflow delegation?

Yes, the command alias preserves all flags and subcommand arguments to maintain expected behavior during delegation. It routes the complete invocation to the canonical router, ensuring the detailed workflow receives the full context.

Can I use this alias router with SPEC path resolution for end-to-end automation?

Yes, the alias router applies during invocation and delegates to the detailed workflow after context load and SPEC path resolution. This ensures your automation commands execute end-to-end through the canonical router.

Why does my alias invocation need to load the canonical router before executing the workflow?

Loading the canonical router before executing the workflow ensures branding and context restoration are handled by the underlying skill. The alias shim provides a failsafe mechanism to defer to the detailed workflow only after proper context is loaded.