auto-status

Route alias status requests to the canonical auto router for SPEC status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route alias-based status requests to the canonical auto router, enabling consistent SPEC status retrieval via the detailed workflows.

Core Features & Use Cases

  • Thin alias shim that delegates to the detailed auto-status workflow.
  • Supports alias forms such as $auto-status, @auto status, and $auto status.
  • Ensures proper Context Load, SPEC Path Resolution, and handoff to the detailed workflow before execution.

Quick Start

Invoke the alias to route a status query through the canonical auto workflow.

Frequently Asked Questions about auto-status

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

FAQPage Schema
How do I route alias-based status requests to a canonical workflow router?

Yes, it supports alias forms such as $auto-status, @auto status, and $auto status. The shim routes these invocations to the canonical auto router to retrieve consistent SPEC status.

Do I need a detailed auto-status workflow to use this router integration?

Yes, using this router integration requires the presence of the detailed auto-status workflow and the canonical auto router surface to execute properly and retrieve SPEC status.

Can I preserve workflow flags like --auto and --model when checking SPEC status?

Yes, routing status requests through this alias shim preserves relevant workflow flags such as --auto, --loop, --multi, --quality, --model, --variant, --team, and --solo during SPEC status retrieval.

What is the best way to ensure proper Context Load before executing a SPEC status query?

The best way to ensure proper Context Load is to invoke this alias shim, which handles Context Load, SPEC Path Resolution, and handoff to the detailed workflow before execution.

Why does my Autopus workflow status alias fail to return SPEC results?

Your Autopus workflow status alias likely fails because the detailed auto-status workflow or the canonical auto router surface is missing, both of which are required dependencies for this shim.