aspire-orchestration

Manage Aspire AppHost lifecycles and recover from file locks and port conflicts.

Updated May 21, 2026

Search Tags:#orchestration #resource management #error recovery #lifecycle management #aspire

Ready to run

npx skills add https://github.com/nymankla/archery --skill aspire-orchestration-nymankla

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspire-orchestration
Source: https://github.com/nymankla/archery/tree/main/.agents/skills/aspire-orchestration
Command: npx skills add https://github.com/nymankla/archery --skill aspire-orchestration-nymankla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aspire-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage the lifecycle of Aspire AppHosts and recover from common issues like file locks, port conflicts, and orphaned processes.

Core Features & Use Cases

Lifecycle Management: Start, stop, wait, and restart Aspire AppHosts.
Error Recovery: Handle file lock errors, port conflicts, and other common issues.
Resource Management: Wait for resources to be ready before interacting with them.
Use Case: If you encounter a "file lock error" or "port already in use" while working with an Aspire project, this Skill can help you recover and continue working.

Quick Start

Use the aspire-orchestration skill to start the Aspire AppHost.

Frequently Asked Questions about aspire-orchestration

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

FAQPage Schema

How do I recover from a file lock error in an Aspire AppHost?▼

To recover from a file lock error in an Aspire AppHost, you can use orchestration workflows designed to detect locks, clear conflicts, and restart the affected resources automatically.

Why does my Aspire AppHost fail to start because of a port conflict?▼

An Aspire AppHost port conflict occurs when a required port is already in use. Orchestration tools can identify the conflicting process, terminate it, and restart the lifecycle cleanly.

Can I wait for Aspire resources to be ready before running scripts?▼

Yes, you can wait for Aspire resources to be ready before running scripts. The orchestration lifecycle management feature monitors resource states and pauses execution until dependencies are fully initialized.

Do I need the Aspire CLI to manage AppHost lifecycle and error recovery?▼

Yes, you need the Aspire CLI to manage AppHost lifecycle and error recovery. It serves as the required dependency for executing commands, managing resources, and applying recovery workflows.

What is the best way to clean up orphaned processes in Aspire projects?▼

The best way to clean up orphaned processes in Aspire projects is using dedicated orchestration recovery workflows. These workflows identify leftover processes, terminate them safely, and free locked resources.

How do I restart an Aspire AppHost after an error?▼

To restart an Aspire AppHost after an error, use the lifecycle management commands to stop the affected resources, resolve the underlying issue like a file lock, and start the AppHost again.