auto-map

Resolve alias invocations to the canonical auto router in Autopus environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim to route short commands to the canonical auto router, ensuring consistent handling and branding across local Autopus environments.

Core Features & Use Cases

  • Thin alias shim that preserves all flags and payloads.
  • Delegates execution to the detailed auto workflow after context load and SPEC resolution.
  • Use Case: when a user types $auto-map, the system resolves it to the full auto routing workflow without exposing internal router details.

Quick Start

Invoke the alias with your desired arguments and it will load the canonical auto router to run the detailed workflow.

Frequently Asked Questions about auto-map

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

FAQPage Schema
How do I route short command aliases to a canonical workflow in a local automation plugin?

To route short command aliases to a canonical workflow, use a thin alias shim to resolve invocations and delegate execution to the detailed auto router. This preserves invocation flags and resolves context for consistent command handling.

What does an alias shim do when resolving command routing in a codebase?

An alias shim resolves short command invocations to a canonical auto router without exposing internal routing details. It loads context, resolves specifications, and hands off to the full workflow while maintaining branding.

Can I preserve command flags and payloads when mapping an alias to a full workflow?

Yes, you can preserve command flags and payloads when mapping an alias to a full workflow. The alias shim acts as a thin pass-through, ensuring all invocation flags and payloads are maintained during context load and routing.

How do I set up consistent command handling for short aliases in my local environment?

To ensure consistent command handling for short aliases, invoke the alias with your desired arguments. The system loads the canonical auto router and runs the detailed workflow, ensuring uniform execution and branding across local plugin environments.

Why use a thin alias router instead of calling the full workflow directly?

Use a thin alias router to hide internal router details and simplify user invocations. It ensures consistent handling and branding across local environments while delegating the heavy execution logic to the canonical detailed auto workflow.

Does the auto-map alias workflow require any specific dependencies to run?

No, the auto-map alias workflow has no external dependencies. It operates as a standalone thin shim within local plugin environments to resolve context and route commands directly to the canonical auto workflow.