aspire

Route tasks to Aspire sub-skills via AppHost detection and guardrails.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/tombly/ancela --skill aspire-tombly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/tombly/ancela/tree/main/.agents/skills/aspire
Command: npx skills add https://github.com/tombly/ancela --skill aspire-tombly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Aspire is a workflow router at the top level for Aspire 13.4 distributed apps. It detects the AppHost, enforces safety guardrails, and routes to the right sub-skill (aspire-init, aspireify, aspire-orchestration, aspire-deployment, aspire-monitoring) based on signals and context.

Core Features & Use Cases

  • Detects the AppHost and routes to the correct sub-skill based on signals and context.
  • Enforces safety guardrails during delegation to prevent unsafe operations.
  • Supports use with Aspire AppHost, Aspire CLI, and common workflows like aspire start/stop/wait, deploy, destroy, describe, logs, and monitoring.

Quick Start

Provide the repository context and let the Aspire router delegate tasks to the matching sub-skill (aspire-init, aspireify, aspire-orchestration, aspire-deployment, or aspire-monitoring).

Frequently Asked Questions about aspire

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

FAQPage Schema
How do I route tasks in Aspire 13.4 distributed apps based on AppHost detection?

Aspire routing detects the AppHost and dispatches tasks to the correct sub-skill based on signals and context. It evaluates your repository environment to determine the appropriate delegation target for workflows like start, stop, wait, deploy, and monitoring.

What safety guardrails apply when delegating Aspire orchestration tasks?

Safety guardrails prevent unsafe operations during Aspire task delegation by validating routing signals before dispatching to sub-skills. These guardrails enforce constraints during the handoff to ensure secure execution across orchestration, deployment, and resource management workflows.

How do I start and stop Aspire AppHost resources using a CLI workflow?

Starting and stopping Aspire AppHost resources is handled by routing the request to the aspire-orchestration sub-skill. The router recognizes your start, stop, or wait signals and delegates the command execution to manage the distributed app lifecycle.

Does the Aspire router support deployment and monitoring workflows for distributed apps?

Yes, the Aspire router supports deployment and monitoring by dispatching to dedicated aspire-deployment and aspire-monitoring sub-skills. It recognizes the specific workflow signals from your input and routes the task to the matching sub-skill for execution.

When do I need to use the Aspire router instead of calling sub-skills directly?

You need the Aspire router when your tasks require AppHost detection and safety guardrails before delegation. It acts as the top-level entry point for Aspire 13.4 workflows, ensuring signals are correctly interpreted and routed to the proper sub-skill.

What Aspire sub-skills are available for routing distributed app initialization and management?

Available sub-skills include aspire-init, aspireify, aspire-orchestration, aspire-deployment, and aspire-monitoring. The router delegates to these sub-skills based on detected signals, handling initialization, orchestration, deployment, and monitoring tasks respectively.