auto-doctor

Route doctor alias requests to the Auto workflow while preserving flags.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim that routes doctor requests to the Auto workflow while preserving flags and delegating to the detailed router.

Core Features & Use Cases

  • Forwards $auto-doctor requests to the canonical @auto doctor router.
  • Preserves all invocation flags (--auto, --loop, --multi, --quality, --model, --variant, --team, --solo) and defers execution to the Auto workflow.
  • References the detailed workflow sources for full behavior and escalation.

Quick Start

Invoke the alias to route to the Auto workflow using the desired doctor command.

Frequently Asked Questions about auto-doctor

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

FAQPage Schema
How do I route command-line alias requests to a workflow router?

Command-line alias routing to a workflow router forwards requests to a canonical path while preserving invocation flags. This alias shim delegates execution to the detailed auto workflow for complete processing.

What flags are preserved when routing automation workflow commands?

Automation workflow command routing preserves flags like --auto, --loop, --multi, --quality, --model, --variant, --team, and --solo. These flags pass through the alias router directly to the detailed workflow execution.

How does command-routing integration handle workflow delegation?

Command-routing integration handles workflow delegation by loading the auto router and forwarding the request. The alias acts as a thin shim, deferring all execution logic to the detailed auto-doctor workflow.

Do I need to install dependencies to use this CLI integration alias?

No additional dependencies are required to use this CLI integration alias. The thin shim loads the existing auto router and forwards requests directly without external components.

Can I use this alias router with other command-routing tools?

This alias router is a specialized thin shim designed for the Auto workflow. Other command-routing tools in the same category may offer broader alias management but lack the integrated flag preservation and workflow delegation.

Why does my workflow alias not execute the doctor command directly?

A workflow alias does not execute doctor commands directly because it functions solely as a routing shim. It must load the detailed auto-doctor workflow source to perform the actual execution and escalation.