Skill UI

Aspire is a code-first polyglot toolchain that orchestrates containers, executables, and cloud resources through an AppHost project, guiding creation, debugging, configuration, deployment, and troubleshooting for distributed applications across languages.

This skill provides expert-level control over a live Chrome browser. It enables full web automation (clicking, form filling, navigation), deep debugging (analyzing console logs, network requests), visual inspection (screenshots, snapshots), and detailed performance profiling. Ideal for QA engineers, web scraping, and front-end development testing.

This skill provides advanced debugging capabilities for failing Power Automate cloud flows using the FlowStudio MCP server. Unlike the limited status codes from the standard Graph API, this tool gives agents deep, action-level inputs and outputs, allowing users to find the true root cause of failures. It is essential for diagnosing complex issues like expression failures, connector authentication errors, or internal run errors.

This is the foundational plumbing layer connecting AI agents to the Power Automate platform via FlowStudio MCP. It provides essential capabilities such as secure authentication setup, robust tool discovery (`list_skills`, `tool_search`), and handling complex, oversized API responses. It serves as the prerequisite layer for specialized workflow skills (e.g., building, debugging, monitoring).

A structured methodology for coordinating multiple, simultaneous investigation threads to determine the root cause of complex system failures, performance regressions, or integration bugs. This skill decomposes a large problem into independent tracks (e.g., database, application code, infrastructure), assigns ownership, and manages structured sync points (Continue/Pivot/Converge) to converge on a solution faster than serial debugging. Essential for high-stakes production incident response.

The Phoenix CLI is a powerful tool for debugging complex LLM and agent workflows. It allows users to fetch detailed traces, spans, and sessions, analyze errors, and structure findings using open and axial coding techniques. It is essential for investigating complex LLM failures, building robust failure taxonomies, and guiding the next steps in application evaluation after initial instrumentation.

A comprehensive methodology for pinpointing the root cause of complex bugs, regressions, or unexpected behavior in large codebases. Techniques include binary search debugging, Git bisect for tracking regressions across commits, strategic data/control flow logging, component isolation, and advanced breakpoint strategies (conditional breakpoints, watch expressions). Ideal for scenarios where the bug source is unclear or difficult to reproduce.

This structured prompt guides an AI model to proactively analyze a user's question and systematically list all necessary files for accurate answering. It forces the AI to categorize required context into 'Must See' (critical), 'Should See' (helpful), 'Already Have,' and 'Uncertainties.' Ideal for complex coding tasks, debugging, or feature implementation that spans multiple codebase files.

A comprehensive CLI for managing the entire lifecycle of Windows applications. It handles initialization, building, packaging into MSIX, signing, debugging, and advanced UI automation via Microsoft UI Automation. Supports multiple modern frameworks including .NET, C++, Electron, Rust, and Flutter, streamlining the deployment process to the Microsoft Store.

This guide enforces a mandatory, multi-stage process for debugging complex software issues. It moves developers beyond merely patching symptoms by forcing them through Root Cause Investigation, Pattern Analysis, Hypothesis Validation, and proper Implementation with testing. It is crucial for solving production bugs, failed tests, and performance issues in a structured manner.

This skill guides the parallel assignment of specialized agents when debugging multiple, independent failure domains. Instead of using one agent for all issues, isolate each problem (e.g., a specific test file or subsystem) to its own dedicated agent. This allows agents to work concurrently without sharing context or interfering with each other, significantly accelerating the debugging process and maintaining context purity.

A comprehensive guide for diagnosing production performance issues in Qdrant vector databases. Learn how to systematically check the optimizer status, analyze high memory usage (OOM crashes), and troubleshoot slow query latencies using key metrics and dedicated API endpoints. Essential for maintaining optimal operational health.