aspire

Orchestrate .NET Aspire distributed application lifecycles and observability via CLI.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mamu7211/feirb-mailclient --skill aspire-mamu7211
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire
Source: https://github.com/mamu7211/feirb-mailclient/tree/main/.claude/skills/aspire
Command: npx skills add https://github.com/mamu7211/feirb-mailclient --skill aspire-mamu7211

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill simplifies the management of distributed .NET applications by providing a unified interface for starting, monitoring, and debugging services orchestrated by .NET Aspire.

Core Features & Use Cases

  • Lifecycle Management: Start, stop, and restart distributed services with a single command.
  • Observability: Access structured logs, distributed traces, and resource health status directly from the CLI.
  • Integration: Easily add new Aspire integrations and manage resource dependencies.
  • Use Case: When developing a microservices architecture, use this skill to quickly spin up the entire stack, verify service health, and inspect logs for a specific containerized component without manual configuration.

Quick Start

Use the aspire skill to start the application in isolated mode and wait for the backend service to become healthy.

Frequently Asked Questions about aspire

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

FAQPage Schema
How do I manage the lifecycle of .NET Aspire distributed applications from the command line?

You can manage the .NET Aspire distributed application lifecycle by using the Aspire CLI to start, stop, and restart orchestrated services through the AppHost project. This provides a unified interface for local development workflows without manual configuration.

Can I inspect structured logs and distributed traces for microservices orchestrated with .NET Aspire?

Yes, you can inspect structured logs, distributed traces, and resource health status directly from the command line. The Aspire CLI facilitates observability for your containerized components, allowing you to verify service health during local development.

What is the best way to spin up a microservices stack and verify container health in .NET?

The best way to spin up a microservices stack in .NET is to use Aspire orchestration to start the application and wait for backend services to become healthy. This automates resource dependencies and provides immediate health status feedback.

Do I need the Aspire CLI to manage microservice orchestration and resource dependencies?

Yes, you need the Aspire CLI to interact with the AppHost project and the underlying container orchestration. It is required to manage resource dependencies and execute local development workflows for .NET Aspire distributed applications.

Does .NET Aspire orchestration work for adding new integrations to an existing microservices architecture?

Yes, .NET Aspire orchestration supports adding new integrations and managing resource dependencies within an existing microservices architecture. You can easily facilitate these integration management tasks directly through the command-line interface.