skills.rest
Insajin
InsajinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

auto-why

Delegate alias requests to the canonical auto router with preserved invocation flags.

106|74|Updated Mar 20, 2026
Search Tags:#automation#workflow#handoff#router#alias#command-routing
One-click install
npx skills add https://github.com/Insajin/autopus-adk --skill auto-why
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-why
Source: https://github.com/Insajin/autopus-adk/tree/main/.autopus/plugins/auto/skills/auto-why
Command: npx skills add https://github.com/Insajin/autopus-adk --skill auto-why

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim to centralize routing to the auto workflow and avoid duplicating logic.

Core Features & Use Cases

  • Thin alias surface that delegates to the detailed auto workflow.
  • Preserves all invocation flags (--auto, --loop, --multi, --quality, --model, --variant, --team, --solo).
  • Ensures consistent branding and flow control across alias invocations.

Quick Start

Invoke the alias surface to delegate to the canonical auto router.

Frequently Asked Questions about auto-why

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

FAQPage Schema
How does command routing work for alias invocations in an automated workflow?▼

Command routing delegates alias invocations to a canonical auto router, centralizing workflow handling. This prevents duplicated logic by ensuring consistent routing control across all alias-triggered automation tasks.

When do I need an alias shim for workflow automation?▼

You need an alias shim when users issue alias invocations that must resolve to a core auto workflow. It centralizes routing to avoid duplicating logic across multiple command entry points.

Can I preserve invocation flags like --auto and --multi when routing commands?▼

Yes, the alias shim preserves all invocation flags including --auto, --loop, --multi, --quality, --model, --variant, --team, and --solo during command routing to the auto workflow.

How do I centralize workflow handling for multiple command aliases?▼

Centralize workflow handling by routing alias requests to a single canonical auto router. The shim delegates execution after context restoration and SPEC path resolution, ensuring consistent flow control.

Does the alias shim require any dependencies to route commands?▼

No, the alias shim has no dependencies. It acts as a thin surface that delegates directly to the detailed auto workflow, requiring no additional components or modules to function.

What's the difference between using an alias shim and duplicating workflow logic?▼

An alias shim centralizes routing to a canonical router, preventing logic duplication. Duplicating logic risks inconsistent branding and flow control, while the shim ensures unified execution across all alias invocations.

Related Skills

Explore More Software Engineering Skills→
InsajinInsajin
106

auto-test

Route $auto-test alias invocations to the canonical auto router.

Community
Basic
InsajinInsajin
106

auto-map

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

Community
Intermediate
InsajinInsajin
106

auto-setup

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

Community
Basic
InsajinInsajin
106

auto-secure

Audit code changes against OWASP Top 10 security risks.

Community
Basic