auto-test

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim that routes alias invocations to the canonical auto router to enable consistent end-to-end automation workflows within Autopus.

Core Features & Use Cases

  • Thin alias shim that preserves the original invocation surface, delegating to the detailed auto workflow.
  • Reinterprets the alias into a canonical router call, then loads the auto skill and its full workflow.
  • Ensures branding, context loading, and SPEC path resolution are handled before handing off to the detailed workflow.

Quick Start

Invoke the alias shim $auto-test with your usual flags to route to the canonical auto skill and load its detailed workflow.

Frequently Asked Questions about auto-test

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

FAQPage Schema
How do I route alias invocations to a canonical automation workflow?

To route alias invocations to a canonical automation workflow, you can use a thin alias shim that preserves flags like --auto and --loop during handoff to the canonical auto router.

What is an alias shim for end-to-end workflow execution?

An alias shim for end-to-end workflow execution is a thin routing layer that reinterprets alias invocations into canonical router calls, ensuring context loading and SPEC path resolution before transferring control.

How do I preserve command flags when handing off to an auto router?

To preserve command flags when handing off to an auto router, invoke the alias shim with your usual flags like --auto, --loop, and --multi, and the shim will maintain them during the routing handoff.

When do I need context loading and SPEC path resolution in an automation workflow?

You need context loading and SPEC path resolution in an automation workflow when delegating to a detailed auto skill, ensuring the router processes these steps before transferring control to the workflow.

Does the auto-test workflow routing require any dependencies?

No, the auto-test workflow routing does not require any dependencies, acting as a standalone thin shim that delegates directly to the canonical auto router for end-to-end execution.

Why use a thin shim instead of calling the canonical auto router directly?

You use a thin shim instead of calling the canonical auto router directly to preserve the original invocation surface, ensuring consistent branding and routing behavior while delegating to the detailed workflow.