- Backdoor DeploymentValidate a container image change via backdoor deployment. Use when: deploying test image to a cluster, comparing data volume between deployments, comparing resource consumption, backdoor deploy, validate container image, image regression testing, build and deploy branch.microsoft/Docker-Provider173
- Multiline ValidationValidate multi-line log stitching behavior for an ama-logs image change. Enables multiline in the configmap, deploys the OLD (production) image, captures stitching baselines, deploys the NEW (test) image, captures the same metrics, and produces an A/B comparison per language and OS. Use when: validating a fluent-bit upgrade, validating a parser/configmap change, comparing multiline stitching between two images, multi-line A/B test, stacktrace stitching test.microsoft/Docker-Provider173
- Upgrade TelegrafUpgrade Telegraf to a new version in the dalec-build-defs repo. Creates a new spec file, updates version/commit/changelog, and prepares a branch for PR. Use when someone says 'upgrade telegraf', 'new telegraf version', 'bump telegraf', or 'update telegraf package'. DO NOT USE FOR: patching existing versions, modifying build targets, or non-telegraf packages.microsoft/Docker-Provider173
- Azure Monitor RcaInvestigate Azure Monitor incidents using application, database, and network evidence without changing workload resources.microsoft/sre-agent170
- Connectivity TriageUse for any Zava Learning incident where students cannot reach the platform or actions fail at the network/edge layer — quiz launches failing, portal 5xx, requests timing out, or backends appearing unhealthy. Traces the full request path (Application Gateway -> NSG -> Container Apps internal load balancer -> APIs) from telemetry and Azure config, finds the broken hop, and remediates within the permitted-action boundary.microsoft/sre-agent170
- Cost AnalysisUse when an operator or a scheduled task requests a periodic cloud-cost / spend audit of the Zava Learning resource group — identify the top cost drivers, week-over-week trend, idle or oversized resources, and concrete savings opportunities. Read-only; produces findings for a report.microsoft/sre-agent170
- Deploying DemoDeploy the SRE Agent demo end-to-end. Use when asked to set up, deploy, or get this demo running.microsoft/sre-agent170
- Deployment Compliance CheckChecks whether Azure Container App deployments comply with the organization's CI/CD-only deployment policy. Uses three signals: Activity Log caller identity, Docker image labels (tamper-proof), and resource tags. QueryLogAnalyticsByWorkspaceIdmicrosoft/sre-agent170
- Email Incident FollowupDraft an opted-in incident email and request approval before sending, with best-effort duplicate checks.microsoft/sre-agent170
- Evidence Before AfterUse to build the before-and-after visual evidence for a Zava Learning incident. First classify the fault, then render the ONE visual that actually explains what changed — a before/after path or topology diagram for connectivity/config/RBAC faults, or time-series comparison charts for performance/availability faults — plus a state/metric delta table. Never plot a metric that does not tell the story. Its output is used in the RCA and the zava-reporting deliverables.microsoft/sre-agent170
- Github Issue FollowupDraft an opted-in GitHub incident follow-up and request approval before publishing, with best-effort duplicate checks.microsoft/sre-agent170
- Managing Sre AgentManage Azure SRE Agent configuration for this demo: connectors, skills, guarded custom agents, response plans, and the knowledge base. Use when asked to create, list, update, or delete SRE Agent resources.microsoft/sre-agent170
- Nsg AuditUse when an operator or a scheduled task requests a periodic Network Security Group (NSG) and connectivity-path audit of the Zava Learning resource group — enumerate every NSG and its rules, trace the full path (NSGs, UDRs / route tables, Private Endpoints, DNS, and any firewall), flag overly-permissive, shadowed, unused, or orphaned rules, and recommend least-exposure corrections. Read-only; produces findings for a report.microsoft/sre-agent170
- Onboarding LabSet up, resume, inspect or operate the Azure SRE Agent onboarding lab in this checkout. Use when a learner asks for help preparing the lab, understanding a setup failure, or saving their reviewed learner artifact.microsoft/sre-agent170
- Pagerduty Incident UpdateUse to keep the triggering PagerDuty incident in sync with the investigation and to close it out — acknowledge on engagement, mark the incident Mitigated the moment the live fix lands, post a concise symptom-only status/summary note (diagnosis, mitigation, links to the PR / Change Request), and resolve the incident only after the RCA and summary report are complete and recovery is verified. This is the PagerDuty communication and closure layer for a Zava Learning incident.microsoft/sre-agent170
- Performance InvestigationUse for Zava Learning incidents where the platform is reachable but a compute tier is degraded — elevated 5xx from the APIs, slow quiz responses, exceptions, an API with no healthy instances, or a back-office batch job failing on the reporting-worker VM (e.g. nightly grade exports). Diagnoses from Application Insights / Log Analytics / Syslog and remediates the application or worker tier.microsoft/sre-agent170
- Pr DeliveryUse to deliver a durable Zava Learning fix as a GitHub pull request once an incident has been root-caused — for either an Infrastructure-as-Code change (Bicep under infra/) or an application code change (under src/). The single skill that creates pull requests; applies after live mitigation and root-cause confirmation. The resulting PR URL is what the ServiceNow Change Request references.microsoft/sre-agent170
- Proactive Health CheckAssess ticket reservation availability, failures, latency, dependencies, and Azure resource health using read-only evidence.microsoft/sre-agent170
- Rbac AuditUse when an operator or a scheduled task requests a periodic RBAC / least-privilege audit of the Zava Learning resource group — enumerate the real role assignments effective on the group, correlate each identity against actual Activity-Log usage to find standing access that is never used, flag over-privileged and directly-assigned (versus group-governed) identities and stale troubleshooting access, and recommend least-privilege corrections. Read-only; produces findings for a report.microsoft/sre-agent170
- Rca AnalysisUse to produce the root-cause analysis narrative for a resolved or mitigated Zava Learning incident — the incident timeline, the trigger vs. latent root cause (5-Whys), contributing factors, and how to present them. Defines the RCA section format; its output is used in the before/after, recommendations, and reporting deliverables.microsoft/sre-agent170
- Recommendations Next StepsUse to produce the forward-looking recommendations and next steps for a Zava Learning incident — prioritized preventive, detective, and process actions with owners, target dates, and the risk of inaction. Its output is used in the zava-reporting deliverables.microsoft/sre-agent170
- Redaction GuardUse whenever you are about to emit operator-visible content — a chat/thread message, a PagerDuty or ServiceNow note, a commit message or pull-request body, or any report artifact (HTML, PowerPoint, Teams card). Deterministically masks secrets, credentials, tokens, private keys, URI-embedded passwords, and PII so they never appear in the thread or in any deliverable. This is a cross-cutting guardrail invoked by the output-producing skills, not a runbook step.microsoft/sre-agent170
- Running DemoRun break/fix demo scenarios with browser verification. Use when asked to demo, break the app, or show the SRE Agent working.microsoft/sre-agent170
- Servicenow Change ManagementUse whenever a Zava Learning investigation produces a durable fix that needs change management — after a GitHub PR is opened for an Infrastructure-as-Code or application code root cause, raise a ServiceNow Change Request referencing the PR and attach the RCA report. The single owner of ServiceNow Change Request and attachment operations.microsoft/sre-agent170
- Ticketing Pr ValidationValidate ticket reservation pull requests using repository evidence and optional read-only production baselines.microsoft/sre-agent170
- Zava Audit ReportUse to package a completed Zava Learning weekly governance audit (NSG / network security, RBAC / least-privilege, or cloud cost) into a single branded, downloadable PowerPoint deck in the Zava house style. The calling audit agent passes its findings (a list of rows with severity) and a short posture summary; this skill renders the deck, applies redaction, and returns the attachment download link. Produces the artifact; it does not send it.microsoft/sre-agent170
- Zava ReportingUse to package a completed Zava Learning incident analysis for the audience. First present a branded in-thread executive summary (markdown with the before/after visuals inline), then produce the downloadable deliverables — a PowerPoint deck, an HTML email, and a Teams notification — using the Zava corporate template. The calling agent may narrow this to a subset (e.g. only the HTML report). Produces content and artifacts; it does not send them. Assembles the output of rca-analysis, evidence-befomicrosoft/sre-agent170
- Analyze PromptRuns Chat Customizations Evaluations analysis for the active customization file and summarizes the findings from the Problems panel.microsoft/vscode-chat-customizations-evaluation142
- Fix Customization Evaluation DiagnosticsFixes diagnostics reported by the Chat Customizations Evaluations extension on the active prompt file. Reads the current diagnostics from the editor and applies suggested improvements.microsoft/vscode-chat-customizations-evaluation142
- Cross Platform PathsCritical patterns for cross-platform path handling in this VS Code extension. Windows vs POSIX path bugs are the #1 source of issues. Use this skill when reviewing or writing path-related code.microsoft/vscode-python-environments141
- Debug Failing TestDebug a failing test using an iterative logging approach, then clean up and document the learning.microsoft/vscode-python-environments141
- Generate SnapshotGenerate a codebase health snapshot for technical debt tracking and planning. Analyzes git history, code complexity, debt markers, and dependencies to identify hotspots and refactoring priorities.microsoft/vscode-python-environments141
- Python Manager DiscoveryEnvironment manager-specific discovery patterns and known issues. Use when working on or reviewing environment discovery code for conda, poetry, pipenv, pyenv, or venv.microsoft/vscode-python-environments141
- Run E2e TestsRun E2E tests to verify complete user workflows like environment discovery, creation, and selection. Use this before releases or after major changes.microsoft/vscode-python-environments141
- Run Integration TestsRun integration tests to verify that extension components work together correctly. Use this after modifying component interactions or event handling.microsoft/vscode-python-environments141
- Run Pre Commit ChecksRun the mandatory pre-commit checks before committing code. Includes lint, type checking, and unit tests. MUST be run before every commit.microsoft/vscode-python-environments141
- Run Smoke TestsRun smoke tests to verify extension functionality in a real VS Code environment. Use this when checking if basic features work after changes.microsoft/vscode-python-environments141
- Settings PrecedenceVS Code settings precedence rules and common pitfalls. Essential for any code that reads or writes settings. Covers getConfiguration scope, inspect() vs get(), and multi-workspace handling.microsoft/vscode-python-environments141
- Code ReviewReview a pull request in this repository (the vscode-containers / Container Tools extension) when the automated reviewer has already supplied the diff and changed files. Checks localization, async/resource correctness, TypeScript conventions, command-line construction, telemetry, settings, and cross-platform issues distilled from this repo's review history. For an on-demand review by PR number, URL, or current branch, use review-pr instead.microsoft/vscode-containers139
- Review PrReview a specific vscode-containers pull request on demand from the CLI (or any interactive agent), the way a Container Tools maintainer would. Use when asked to review a PR by number, URL, or "the current branch", to produce a written review and, only when explicitly asked, post comments on the PR. Fetches the PR with the GitHub CLI and applies the shared review rubric.microsoft/vscode-containers139
- KqlKQL language expertise for writing correct, efficient Kusto queries using the Fabric RTI MCP tools. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries — even simple ones — because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Tmicrosoft/fabric-rti-mcp132
- Azureml K3s Compute Target SetupSet up a K3s cluster on an NVIDIA GPU host, connect it to Azure Arc, and configure Azure ML to use it as a Kubernetes compute target. Includes GPU smoke-test and validation instructions for Azure ML jobs on the Arc-connected cluster - Brought to you by microsoft/physical-ai-toolchainmicrosoft/physical-ai-toolchain121
- Fleet DeploymentDeploy trained robot policies to edge fleets via FluxCD GitOps, image automation, and deployment gatingmicrosoft/physical-ai-toolchain121
- Fleet IntelligenceMonitor robot fleet telemetry via Azure IoT Operations, drift detection, Grafana dashboards, and Fabric analyticsmicrosoft/physical-ai-toolchain121
- InfrastructureDeploy and manage Azure infrastructure for the Physical AI Toolchain including Terraform IaC, Kubernetes setup, GPU configuration, and network topologymicrosoft/physical-ai-toolchain121
- Osmo Lerobot TrainingSubmit, monitor, analyze, and evaluate LeRobot imitation learning training jobs on OSMO with Azure ML MLflow integration and inference evaluation - Brought to you by microsoft/physical-ai-toolchainmicrosoft/physical-ai-toolchain121
- Synthetic DataGenerate synthetic training data using NVIDIA Cosmos world foundation models for SDG pipelinesmicrosoft/physical-ai-toolchain121
- Api DesignGuide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.microsoft/haste107
- Copilot Cli ModesComprehensive guide to all Copilot CLI running modes: Interactive, Plan, Autopilot, Fleet, Research, Chronicle, and Delegate. Use when asked about CLI modes, workflows, or how to use Copilot CLI effectively.microsoft/haste107
- Debug Test FailuresSystematic debugging workflow for test failures. Use when tests are failing, a CI build is red, or when asked to debug test issues.microsoft/haste107
- Dependency UpdateGuide for safely updating project dependencies. Use when asked to update packages, upgrade dependencies, or check for outdated libraries.microsoft/haste107
- Deterministic ScriptsDeterministic script execution skill for HASTE. Execute scripts instead of free-form LLM behavior for consistent, repeatable operations. Use when: 'run preprocessing', 'convert format', 'parse metadata', 'generate tiles', 'build wheel', 'deploy functions'. Prevents hallucinated scripts.microsoft/haste107
- Imagery Provider AdaptationImagery provider adaptation skill for HASTE. Encapsulates provider-specific logic for satellite imagery sources (Planet, Vantor, Airbus, etc.). Use when: 'new imagery provider', 'add source type', 'satellite provider', 'Planet', 'Vantor', 'Airbus', 'Pleiades', 'WorldView', 'SkySat', 'imagery ingestion', 'provider adapter'.microsoft/haste107
- Release NotesGenerate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release.microsoft/haste107
- Security AnalysisDependabot and security analysis skill for HASTE. Parse alerts, group related vulnerabilities, apply severity rules, and produce structured reports. Use when: 'Dependabot alert', 'security scan', 'vulnerability triage', 'dependency audit', 'npm audit', 'pip audit', 'CVE analysis'.microsoft/haste107
- Validation DiagnosticsValidation and diagnostic skill for HASTE. Compare planned vs implemented work, generate diagnostic reports, and feed misses back into skill refinement. Use when: 'validate implementation', 'compare to spec', 'diagnostic report', 'drift analysis', 'coverage check', 'implementation review'.microsoft/haste107
- BootShorthand alias for the /promptkit skill. Use this when the user wants to assemble a task-specific prompt using PromptKit, or says "boot" to start the PromptKit composition engine.microsoft/PromptKit106
- BootstrapAlias for the /promptkit skill. Use this when the user wants to assemble a task-specific prompt using PromptKit, or says "bootstrap" to start the PromptKit composition engine.microsoft/PromptKit106
- Ingest Cwe TaxonomiesIngest the official MITRE CWE database and generate per-domain security audit taxonomies for PromptKit. Use this skill when the user wants to update CWE taxonomies, ingest a new CWE version, or regenerate domain mappings from the CWE corpus.microsoft/PromptKit106
- PromptkitPromptKit composition engine. Use this skill when the user wants to assemble a task-specific prompt, write a requirements doc, investigate a bug, review code, plan an implementation, author agent instructions, create a Copilot prompt file, build an agentic workflow, or perform any engineering task that PromptKit has a template for. Also use when the user mentions PromptKit, asks about available templates or personas, or wants to compose prompts from reusable components.microsoft/PromptKit106