auto-idea

Route alias invocations to the canonical auto router for brainstorming workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim that routes alias invocations like $auto-idea to the canonical auto router, enabling reuse of the full brainstorming workflow without duplicating logic.

Core Features & Use Cases

  • Thin alias shim: routes the immediate invocation to the canonical router surface, avoiding duplication.
  • Preserves flags: --auto, --loop, --multi, --quality, --model, --variant, --team, and --solo, ensuring compatibility with the detailed workflow.
  • Delegates to the detailed auto-idea workflow after context restoration and SPEC path resolution.

Quick Start

Invoke the alias shim with your chosen flags to load the full auto workflow.

Frequently Asked Questions about auto-idea

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

FAQPage Schema
How do I route shorthand alias invocations to a unified brainstorming workflow?

Alias routing redirects shorthand invocations like $auto-idea to a canonical auto router, applying context load and SPEC path resolution before delegating to the full brainstorming workflow.

Can I pass workflow flags like --loop and --multi through an alias shim?

Yes, the alias shim preserves flags like --auto, --loop, --multi, --quality, --model, --variant, --team, and --solo, ensuring full compatibility with the detailed auto-idea workflow.

Why use an alias shim instead of duplicating idea-generation workflow logic?

Using a thin alias shim avoids logic duplication by routing the immediate invocation to the canonical router surface, enabling reuse of the full brainstorming workflow across providers.

How does context load and SPEC path resolution work in idea-generation routing?

Context load and SPEC path resolution execute during the alias invocation, restoring the necessary environment state before handing off to the detailed auto-idea workflow pipeline.

Do I need any dependencies to use the auto-idea alias routing shim?

No dependencies are required to use the alias routing shim, as it operates as a thin shim that redirects invocations to the canonical auto router without external packages.

Does the alias shim support solo and team brainstorming workflows?

Yes, the alias shim supports both --team and --solo flags, routing the chosen mode to the detailed auto-idea workflow for collaborative or individual idea generation.