- Shell UseDrive, inspect, assert on, record, and watch a real terminal from the command line with the shell-use CLI. Use when running shells (bash, zsh, fish, PowerShell, pwsh, cmd, xonsh, elvish, nushell) or TUI programs (vim, less, top, etc.) in a headless PTY; sending keystrokes, key combos, or mouse input; resizing, writing raw bytes, or signaling the child; waiting for a command to finish or the screen to settle; asserting on terminal text, colors, exit codes, output, or snapshots; capturing text or microsoft/shell-use192
- Code ReviewReview a GitHub pull request for problems and consistency with project conventions. Use when asked to review a PR, do a code review, check a PR for issues, or review pull request changes.microsoft/dcp177
- Update DependenciesUpdate packages that DCP executables depend on. This skill is used infrequently, usually just once at the start of a new development cycle. Should only be used when requested explicitly, never as part of a regular change or PR.microsoft/dcp177
- Ama Logs Update Charts Release NotesPrepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry. Use when: cutting a new ama-logs release, '3.X.Y release notes', 'bump ciprod image tag', 'release PR for Docker-Provider', creating release notes for a new ciprod build. DO NOT USE FOR: MDSD or Windows AMA bumps in isolation, hotfix patches, or anything that does not increment the ciprod image tag.microsoft/Docker-Provider171
- 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-Provider171
- 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-Provider171
- 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-Provider171
- Duroxide Code CoverageMeasure and improve code coverage in the Duroxide durable execution runtime. Use when asked about coverage, testing coverage, running llvm-cov, or improving test coverage percentages.microsoft/duroxide168
- Dv AdminEnvironment-level Dataverse administration — bulk delete, retention/archival, organization settings, OrgDB settings, recycle bin, audit, and the 37 allowlisted PPAC toggles. Use when the user wants to clean up data at scale, configure audit, change environment settings, or manage retention policies.microsoft/Dataverse-skills160
- Dv ConnectOne-step setup for a Dataverse environment — installs tools, authenticates, registers the MCP server, and writes `.env`. Use when starting a new project, switching environments, fixing authentication, or troubleshooting an MCP connection that won't come up.microsoft/Dataverse-skills160
- Dv DataRecord-level CRUD and bulk operations via the Python SDK — create, update, delete, upsert, CSV import, multi-table foreign-key loads, AI-generated sample data. Use when the user wants to write, modify, seed, or import data records into Dataverse tables.microsoft/Dataverse-skills160
- Dv MetadataDataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views. Use when the user wants to define or evolve the data model — add a column, create a table, set up a lookup, customize a form, or build a view.microsoft/Dataverse-skills160
- Dv OverviewTool routing and cross-cutting rules for Dataverse work — which skill applies to which task, environment-confirmation, and pull-to-repo. Use when the user mentions Dataverse, Dynamics 365, Power Platform, or CRM; this skill picks the specialist (dv-connect / dv-data / dv-metadata / dv-query / dv-solution / dv-admin / dv-security) for the request.microsoft/Dataverse-skills160
- Dv QueryBulk reads, multi-page iteration, and analytics over Dataverse data via the Python SDK and Web API. Use when the user wants to read, list, filter, aggregate, group, join, or analyze records — including pandas DataFrame workflows and notebook exploration.microsoft/Dataverse-skills160
- Dv SecuritySecurity-role assignment, user access, application users, business units, and admin self-elevation in Dataverse environments. Use when the user wants to give someone access, grant a role, become an admin, or add a service principal.microsoft/Dataverse-skills160
- Dv SolutionDataverse solution lifecycle — create, export, import, promote across environments, and validate deployments. Use when the user wants to package customizations, deploy to another environment, or move work between dev / test / prod.microsoft/Dataverse-skills160
- 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-environments130
- Debug Failing TestDebug a failing test using an iterative logging approach, then clean up and document the learning.microsoft/vscode-python-environments130
- 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-environments130
- 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-environments130
- 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-environments130
- 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-environments130
- 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-environments130
- 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-environments130
- 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-environments130
- 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-agent128
- 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-agent128
- Deploying DemoDeploy the SRE Agent demo end-to-end. Use when asked to set up, deploy, or get this demo running.microsoft/sre-agent128
- 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-agent128
- 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-agent128
- Managing Sre AgentManage Azure SRE Agent configuration for this demo: connectors, skills, response plans, and the knowledge base. Use when asked to create, list, update, or delete SRE Agent resources.microsoft/sre-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- 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-agent128
- Analyze PromptRuns Chat Customizations Evaluations analysis for the active customization file and summarizes the findings from the Problems panel.microsoft/vscode-chat-customizations-evaluation126
- 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-evaluation126
- 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-mcp122
- Sharepoint EmbeddedEntry point for all SharePoint Embedded operations - setup, container management, content operations, and billing. Routes to the appropriate sub-skill. Use when working with SPE, SharePoint Embedded containers, container types, file storage containers, or Microsoft Graph storage APIs.microsoft/SharePoint-Embedded-Samples103
- Sharepoint Embedded SetupSets up a complete SharePoint Embedded environment - creates Entra app, container type, registration, container, and uploads a test file. Use when setting up SPE, creating container types, onboarding to SharePoint Embedded, or bootstrapping file storage containers.microsoft/SharePoint-Embedded-Samples103
- Agent CollaborationStandard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communicationmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Agent CollaborationStandard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communicationmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Agent ConductShared hard rules enforced across all squad agentsmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Agent ConductShared hard rules enforced across all squad agentsmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Architectural ProposalsHow to write comprehensive architectural proposals that drive alignment before code is writtenmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Architectural ProposalsHow to write comprehensive architectural proposals that drive alignment before code is writtenmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- AspireOrchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-deploy skill). INVOKES: Aspiremicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Aspire Cli InstallMigrating .NET Aspire repos from workload install to CLI script installmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- Aspire Package UpgradeUpgrading .NET Aspire packages to latest stable/preview versionsmicrosoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74
- 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/PromptKit74
- 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/PromptKit74
- Ci Validation GatesDefensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22microsoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry74