Triggers deep architectural review across 15 Aspire-specific dimensions. Activated by requests for deep review, architectural review, pattern review, or PRs touching hosting core, Azure integrations, dashboard, CLI, or components.
npx skills add https://github.com/microsoft/aspire --skill reviewing-aspire-architecture
Aspire-specific architectural review via the reviewing-aspire-architecture agent. Catches domain patterns that generic code-review cannot.
Use: "deep review," "architectural review," "pattern review," PRs touching hosting core, Azure integrations, dashboard, CLI, components, new resource types, app model changes, deployment behavior.
Don't use: doc/config-only PRs → code-review · generic PR review → code-review · CI failures → ci-test-failures · flaky tests → fix-flaky-test · API surface → api-review
code-review covers generic bugs, security, perf, concurrency, and error handling. This skill covers only checks requiring Aspire domain knowledge. Some topic areas (Security, Performance, Error Handling) exist in both, but the checks are disjoint: generic patterns belong to code-review, Aspire-specific patterns belong here. Run code-review first for breadth, then this for domain depth.
| Folder | Dimensions |
|---|---|
| src/Aspire.Hosting/** | Resource Model, API Design, Pattern Conformance, Containers |
| src/Aspire.Hosting.Azure*/** | Azure Provisioning, Resource Model, API Design, Security |
| src/Aspire.Dashboard/** | Dashboard UI/UX, Security, Performance |
| src/Aspire.Cli/** | CLI Behavior, Error Handling, Platform Compatibility |
| src/Components/** | Pattern Conformance, API Design, Build & Contributor Workflow |
| tests/** | Test Quality + mirror dimensions of code under test |
| eng/, .github/ | Build & Contributor Workflow, Documentation & Naming |
Full review rules in the reviewing-aspire-architecture agent.
Query the OFR (Office of Financial Research) Hedge Fund Monitor API for hedge fund data including SEC Form PF aggregated statistics, CFTC Traders in Financial Futures, FICC Sponsored Repo volumes, and FRB SCOOS dealer financing terms. Access time series data on hedge fund size, leverage, counterparties, liquidity, complexity, and risk management. No API key or registration required. Use when working with hedge fund data, systemic risk monitoring, financial stability research, hedge fund leverage or leverage ratios, counterparty concentration, Form PF statistics, repo market data, or OFR financial research data.
Design and automate Extract, Transform, Load data pipelines for data integration and analytics
Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy disruptions, (3) assess "stealth tightening" effects, (4) compare shutdown episodes across different monetary policy regimes (QE vs QT), or (5) generate liquidity stress reports with historical context. Recommended usage frequency is weekly on Wednesdays after TGA/reserve data releases.
Auto-instrument Node.js applications with distributed tracing, metrics, and logs.
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
Take microsoft/reviewing-aspire-architecture from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.