REPO PACKAGE
microsoft aspire
OFFICIAL23skills
4ready to use
LABSCO SUMMARY
The list runs from code review and PR creation to CI failure triage, flaky-test reproduction and quarantine, dependency updates, backporting fixes to release branches, triggering the internal Azure DevOps pipeline on the dnceng mirror, dashboard and CLI end-to-end test authoring, and VS Code extension debugging. Some are explicit about their own boundaries: reviewing-aspire-architecture triggers only on an explicit request for a deep architectural review, not on every PR that touches Aspire code, and hosting-integration-authoring is for someone building a new Aspire.Hosting integration package for the project, not for someone consuming one in their own app.
This is for an engineer with commit access, or push access to a fork, working inside microsoft/aspire day to day — filing backports, chasing CI flakiness, updating container image pins, keeping the VS Code extension and the dashboard's Blazor components tested. If what you actually want is help writing an apphost.cs or apphost.ts file that wires together a Redis cache, a Node API, and a Vite frontend — the thing Aspire's own README demonstrates — none of these 23 skills teach that; they assume you're already inside the engineering process, not consuming the product.
READ THE FULL ANALYSIS
What it costs to start. Ten of the 23 need an account or credential before they do anything — Azure DevOps access for the internal pipeline, GitHub push or admin rights for backports and PR creation, NuGet lookups for dependency updates. Seven more need a local tool already installed, and one needs an MCP connection. Only five install and run with nothing further — a smaller ready share than most packages this size.
ALSO IN THIS PACKAGE
AGENT PERSONALITIES
2 itemsAGENT PERSONALITY
agentic workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing
AGENT PERSONALITY
reviewing-aspire-architecture
Use only for an explicit deep Aspire architectural or pattern review of an existing PR or diff, or a named Aspire-domain question escalated by a generic reviewer that cannot resolve it. Do not use for ordinary review, implementation, debugging, explanation, or design discussion—even when a PR is referenced—and never select it from changed file paths alone.
MCP SERVERS
2 itemsMCP SERVER
hex1b
stdio · dnx Hex1b.McpServer@0.133.0 --yesMCP SERVER
github
Official GitHub MCP server for repository search, issues, pull requests, code context, and GitHub workflows in MCP-compatible AI clients.
http · https://api.githubcopilot.com/mcp/WHAT'S INSIDE
23 showing · 23 totalReady to use
Nothing else to set up — install it and go.
23 of 23
SETUP
Showing all 23 skills
api-review
Reads the new and changed public functions and types a code change adds to Aspire, flags the ones that break .NET's naming and design conventions, and tags whoever wrote each one.
azdo-internal
Aspire's official build runs on a Microsoft-internal server mirrored from GitHub; this covers pushing a branch there, starting a build, watching it, and trying out pipeline changes without publishing anything for real.
backport-pr
Takes a fix that already landed in the main line of development and gets it onto an older release that is still supported, with the approval form filled in and ready for the release board.
ci-test-failures
When the automated tests fail on the build server, this pulls the logs down, works out which tests failed, and files or updates the ticket that tracks them.
cli-channel-debugging
Makes a copy of the Aspire command-line tool that you built yourself pretend to be any published version, so a bug reported against one specific build can be reproduced and fixed on the spot.
cli-e2e-testing
Tests that drive Aspire's command-line tool through a real terminal the way a person would type at it, recording the whole session so a failure can be replayed afterwards.
code-review
A code review that reports problems only — bugs, security holes, missing tests — with no style nitpicks and no praise, and nothing is posted until you pick which findings to send.
connection-properties
Gives every database or service an app connects to the same standard set of details — host, port, user, password, web address — in the code and in the documentation table beside it.
create-pr
Opening a pull request the way this repository expects it — its own template filled in properly, rather than a free-form note nobody can review against.
dashboard-testing
Writing tests for the Aspire Dashboard, the web page that shows a running app: which of the two test projects a piece of code belongs in, and the hand-written stand-ins the team uses instead of a mocking library.
dependency-update
Updating the outside libraries Aspire depends on: find what the newest version is, get it copied into Microsoft's internal store first, then move the project onto it.
deployment-e2e-testing
Tests that really do deploy a sample app to Azure, check it works up there, and then delete everything they created — the slow, expensive kind that catches what a local test cannot.
deprecate-integration
Retires a shipped add-on gently — everything it offers starts warning that it is going away, it stops appearing in the list of things you can add, and it ships one last time before anyone deletes the code.
fix-flaky-test
A test that fails only some of the time gets reproduced first, then diagnosed, then fixed and proved on the build server — and stays quarantined until it has been quiet for three weeks.
hex1b
Drives any program that runs in a terminal from the outside — starts it invisibly, reads what is on its screen, types into it, and records the whole session for replay.
hosting-integration-authoring
The rulebook for teaching Aspire about a new service — a database, a cache, a cloud resource: first work out which kind of thing it is, then follow the conventions for that kind.
issue-investigation
Takes a bug report filed against Aspire and finds out what is really going on — rebuilding the reporter's setup, trying to make the bug happen, and writing up the evidence either way — without jumping to a code fix.
pr-testing
A proposed change to Aspire is not judged here by reading it: the build that actually contains the change gets installed and put through what a real user would do. The write-up says what worked, what broke, and where.
reviewing-aspire-architecture
A second, specialist pass over a proposed change to Aspire, looking only for the house patterns that a general-purpose code reviewer has no way of knowing about — and only when somebody has asked for it.
startup-perf
Records where the seconds actually go while Aspire is starting up, so a slow start can be held against an earlier recording and the piece that got slower can be pointed at.
test-management
When one of Aspire's tests starts failing at random and holds everyone up, this is how it gets switched off properly: marked through the repository's own tool, tied to the issue that tracks it, and put up as its own pull request.
update-container-images
Aspire pins an exact version of every ready-made service it can start for you, such as Redis or Postgres. Those pins go stale, and this is the roughly monthly round of moving them forward without breaking anything.
vscode-extension
The VS Code add-on that ships with Aspire sits in its own corner of the repository, and these are the ground rules for working on it: build that part alone rather than the whole product, keep every visible word translatable, test it end to end, and keep it talking to the older command-line tool people already have installed.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (23 skills)
npx skills add microsoft/aspireSINGLE SKILLOr install a single skill
npx skills add microsoft/aspire --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.