documentation-styleFormatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure…quality-gateQuality gate for SDD artifacts (specs, ADRs, tasks, code). Use when generating or updating specs, ADRs, task decomposition, or code implementation to validate quality before delivering to the user. Do not use for linting, code formatting, human code review,…work-item-creationRules and checklist for creating work items on GitHub Issues or Azure DevOps. Use when you need to create issues, user stories, tasks, epics, or features on the board. Do not use for platform configuration (use board-config), managing workflow of existing…test-disciplineTesting practices for behavior-focused, refactor-resistant tests. Use when implementing features, fixing bugs, refactoring, or adding or reviewing tests to ensure they verify intent through public interfaces and avoid tautological assertions. Also use when…lsp-setupSet up Language Server Protocol (LSP) servers for Copilot CLI by detecting the repository language stack, selecting trusted servers, and merging user or project configuration. Use when the user asks to install or configure a language server, enable code…work-item-workflowWork item workflow for implementation. Use when starting work on a GitHub issue or Azure DevOps work item to verify assignee, dependencies, priority, and capacity. Do not use for creating new work items (use work-item-creation), for suggesting the next task…debugging-recoverySystematic debugging with structured triage. Use when tests fail, builds break, runtime behavior does not match expectations, or any unexpected error occurs during implementation. Do not use for planned refactoring (use code review), for test strategy (use…harness-learningsCapture and consult codebase-specific learnings across the lifecycle. Use when an agent encounters a correction loop, review finding, test prerequisite, or recurring pattern that future sessions should know about. Also use at the start of implement, verify,…
مستكشف المستودعات
microsoft · المستودعات و skills الممثلة - الصفحة ٣
عرض على مستوى المستودعات لـ ٣٬٥٥٦ skills مجمعة عبر ٤٠٤ مستودعات GitHub.
proactive-health-checkAssess ticket reservation availability, failures, latency, dependencies, and Azure resource health using read-only evidence.ticketing-pr-validationValidate ticket reservation pull requests using repository evidence and optional read-only production baselines.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.azure-monitor-rcaInvestigate Azure Monitor incidents using application, database, and network evidence without changing workload resources.email-incident-followupDraft an opted-in incident email and request approval before sending, with best-effort duplicate checks.github-issue-followupDraft an opted-in GitHub incident follow-up and request approval before publishing, with best-effort duplicate checks.deploying-demoDeploy the SRE Agent demo end-to-end. Use when asked to set up, deploy, or get this demo running.running-demoRun break/fix demo scenarios with browser verification. Use when asked to demo, break the app, or show the SRE Agent working.
reactor-appCreate WinUI 3 desktop applications using the Reactor framework — a React-inspired declarative C# projection over WinUI 3. No XAML, no data binding, no templates. This file is the legacy single-file skill — prefer the `reactor` plugin under `plugins/reactor/`…reactor-build-and-checkBuilding Reactor apps and reading diagnostics — `mur check <path>` is the build (same exit code as `dotnet build`, never re-run to confirm) with one-line diagnostics, skill pointers, and `→ try:` did-you-mean suggestions to use verbatim. Covers iteration vs…reactor-dslPointer to the full Reactor API signatures index (`references/reactor.api.txt`). The 90% of DSL content — hooks, components, common factories, modifiers, theme tokens, gotchas, React-to-Reactor mapping — already lives in `reactor-getting-started`. Load this…reactor-windowingReactor top-level windowing cookbook: WindowSpec, OpenWindow, draggable windows, borderless/tool windows, placement persistence, taskbar visibility, z-order, aspect ratio, SizeToContent, displays, taskbar integration, and picker HWND wiring.pr-lifecycleTake a microsoft/microsoft-ui-reactor PR from "pushed" to "ready for review" without hand-holding. Activate for "get this PR ready", "take this PR through readiness", "run the PR lifecycle", "babysit this PR", "loop Copilot reviews until it's clean", or…analyzer-dymAuthor or remove Reactor "did-you-mean" / diagnostic analyzers and the matching `mur check` rules in the microsoft/microsoft-ui-reactor repo. Activate when a contributor asks to "add a REACTOR_ diagnostic", "add a did-you-mean for <mistake>", "add/remove a…pr-reviewMulti-dimensional review of a PR or feature branch in the microsoft/microsoft-ui-reactor repo. Activate when a contributor asks to "review my PR", "review my changes", "vet my branch before pushing", "do a full review", "PR review", "review this feature", or…reactor-devtoolsDriving a running Reactor app via `mur devtools` — screenshot, inspect visual tree, click/type/scroll, read hook state. Use when diagnosing visible bugs (layout, contrast) or verifying a UI change landed.
systems-design-methodologyUse when the /systems-design mode is active. 9-phase structured design methodology -- problem framing, system classification, constraints, candidate architectures, tradeoff analysis, risk review, refinement, migration planning, and documentation. Governs…systems-design-review-methodologyUse when the /systems-design-review mode is active. 7-step design review methodology -- understand the design, classify the system, evaluate against codebase, adversarial analysis, tradeoff validation, synthesis, and action items. Governs conversation flow,…adversarial-reviewAdversarial review of a system design from 6 critical perspectives -- SRE, security, staff engineer, finance, operator, and developer advocate. Produces a unified risk assessment. Use for INTERACTIVE on-demand reviews during a design conversation…system-type-azureDomain patterns for Azure cloud architecture — compute selection, managed services, identity (Entra ID), networking, data platform, messaging, deployment, cost management, and operational patterns. Use when designing or evaluating a system deployed on…system-type-peer-to-peerDomain patterns for peer-to-peer system architecture — network topologies, NAT traversal, peer discovery, data distribution, consistency without central authority, identity and trust, and incentive mechanisms. Use when designing or evaluating a decentralized,…system-type-spaDomain patterns for single-page application architecture — client-side routing, state management, rendering strategies, authentication, performance, and offline support. Use when designing or evaluating a browser-based SPA, progressive web app, or rich…design-philosophy-domain-drivenDomain-Driven Design as a lens for system architecture — bounded contexts, aggregates, ubiquitous language, context mapping, domain events, and strategic vs tactical patterns. Use when modeling complex business domains, defining service boundaries, or…design-philosophy-linuxThe Unix/Linux design philosophy as a lens for system design — mechanism vs policy, composability, small tools, text streams, convention over configuration, and the principle of least surprise. Use when evaluating designs for composability, simplicity, or…
coordinator-init-modeThe complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for…skill-name{what this skill teaches agents}skill-name{what this skill teaches agents}evidence-judgeRead a supplied report and summarize its recorded status and numeric items.agent-collaborationStandard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communicationcoordinator-response-modeSelecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the…coordinator-source-of-truthThe complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand…reviewer-protocolReviewer rejection workflow and strict lockout semantics
stateStore and query a Microsoft Managed App's built-in state and file attachments with `ms project state` CLI schema commands and generated TypeScript clients. First, with the user signed in to the CLI, run `ms feature status --name state --json`; if…create-appCreates managed apps using React and Vite. Use when scaffolding a new app with `ms app create` and ending on local dev with `ms app dev`.add-office365-usersAdds Office 365 Users by delegating to `/add-data-source` with `api-id=shared_office365users` and action mode. Use for user profiles, managers, direct reports, people search, and profile photos.list-appsDiscovers managed apps in the active environment via `ms app list --json` and optional `ms app show --json`. Use when listing or locating apps.add-data-sourceCanonical add flow for Microsoft Managed Apps. Use when adding any data source through `ms app add data-source` (with `--as table` or `--as action`), or when the user wants help discovering which connector / api-id to use.deployShips a Microsoft App to the cloud. Use when the user asks to deploy via `ms app deploy` (with optional build-status traceability flow).list-connectorsLists connectors available in the active environment — including whether each is allowed or blocked by your organization's policy — plus the connection-bound data sources already wired into a Microsoft App. Use when discovering connectors and their operations…add-dataverseAdds Dataverse by delegating to `/add-data-source` with `api-id=dataverse` and table mode. Use when binding Dataverse tables.
demo-caldova-evidence-agentGuide or rehearse the Caldova Evidence Agent demo one beat at a time. Use when: demo the Caldova evidence agent, rehearse the SQL MCP demo, walk through the evidence agent, start the evidence demo, next beat, show Foundry Log stream, or practice the causal…run-caldova-evidence-agentStart, open, verify, or stop the Caldova Evidence Agent application. Use when: run the Caldova evidence app, start the evidence agent, open the research app, check the app, verify the live app, or stop the local app.biomedical-evidence-review-v2Use for broad, comparative, or follow-up biomedical evidence questions that require focused parallel retrieval, cross-source synthesis, limitations, concise citations, and a next research question.build-caldova-evidence-agentBuild, provision, repair, or verify the Caldova Evidence Agent stack. Use when: build the Caldova evidence agent, deploy the evidence demo, provision SQL MCP, create the hosted agent, publish the evidence skill, deploy the app, rebuild the demo, or verify the…run-handsfree-indexingPrepare, deploy, validate, rehearse, monitor, or clean up the SQLCon EU 2026 Caldova Hands-Free Indexing demo. Use for Azure SQL automatic indexing, Automatic Index Compaction, the Hyperscale dashboard workload, index bloat, compaction progress, or the demo's…run-keynote-demo-1Prepare, validate, rehearse, or troubleshoot SQLCon EU 2026 Keynote Demo 1, Caldova Regional Care on Azure Local. Use when running the Demo 1 setup, checking SQL Server 2025 and Foundry Local, validating the Azure Local gateway, starting the transfer-center…analyze-readiness-at-scaleAnalyze migration assessment readiness at scale or show an estate-wide migration assessment dashboard for Azure Arc SQL Server instances.evaluate-azure-migration-assessmentRun or refresh migration assessment for an Azure SQL Server instance and retrieve readiness and SKU results.
functional-analysis-group-writerAuthor phase-K group AFU (functional-analysis) markdown for ONE group declared in `config/grouping.yaml`. LLM-driven. SCAFFOLD. Two scopes: Per-section — writes one per-language draft into…requirements-group-writerAuthor phase-J group ATE (technical-requirements) markdown for ONE group declared in `config/grouping.yaml`. LLM-driven. SCAFFOLD. Two scopes: Per-section — writes one per-language draft into…chunk-text-extractionDeterministically slice a mainframe or IBM i (AS400) source file (COBOL, CBLLE, SQLCBLLE, CL, CLP, CLLE, JCL, PROC, copybook, BMS) into one raw-text file per chunk. USE FOR: extract CL or COBOL chunks as txt and prepare source text for section-doc-writer. DO…cobol-chunkingDeterministically chunk mainframe or IBM i (AS400) sources (COBOL, CBLLE, SQLCBLLE, CL, CLP, CLLE, JCL, PROC, copybook, BMS) into `chunk-manifest.json`. USE FOR: chunk COBOL, ILE COBOL, IBM i Control Language, CLLE program, JCL job, copybook, phase A…cobol-facts-extractionDeterministically extract `facts.json` from mainframe or IBM i (AS400) COBOL, CBLLE, SQLCBLLE, CL, CLP, CLLE, JCL, PROC, copybook, or BMS. USE FOR: IBM i CL command facts, CALL/CALLPRC/SBMJOB, OVRDBF/MONMSG, COBOL facts, call graphs, and incoming xref. DO NOT…diagram-rendererAuthor FILE-LEVEL Mermaid overviews for ONE mainframe or IBM i (AS400) source from `facts.json`. Emits call graph, COBOL control flow, IBM i CL command flow, JCL steps, CICS calls, SQL cursor lifecycle, and ER fragments when facts exist. USE FOR: IBM i…facts-slicingDeterministically fan a per-file `facts.json` into per-chunk slice files (`docs/_shared/<file>/facts-slices/<chunk_id>.json`) so phase-C per-section subagents (section-doc-writer, qa-reviewer) read only the ~10% of facts they need. USE FOR: slice facts.json,…functional-analysis-finalizerAuthor phase-G per-file `functional-analysis.md` for ONE mainframe or IBM i (AS400) source from its prepared section drafts. LLM-driven. USE FOR: assemble IBM i or mainframe functional analysis, stitch FA sections, and phase-G finalization. DO NOT USE FOR:…
azldev-add-componentRead this before adding or importing a component; follow the workflow instead of guessing. Explains how to add a new component to an azldev distro, covering inspecting the upstream spec, the inline-versus-dedicated-file decision, and validating with render,…azldev-build-componentRead this before building a component or diagnosing a build failure; do not guess build flags or the inner loop. Explains how to build, iterate on, and debug an azldev component, covering comp build flags (local-repo, preserve-buildenv), the render/build/test…azldev-comp-tomlRead this before authoring, editing, or reviewing a *.comp.toml file; do not work from memory. Explains the azldev component definition format and review workflow, covering component structure, spec sources, build config, release calculation, render options,…azldev-imageRead this before building, booting, or configuring an azldev image. Explains the azldev image commands (list, build, boot, test, customize) and the [images.<name>] config (kiwi definition, capabilities, tests, publish); the kiwi XML format itself is upstream…azldev-mockRead this before testing or inspecting a built RPM; do not drive mock by hand from memory. Explains how to test and inspect built packages in a mock chroot with 'azldev adv mock shell', covering non-interactive (heredoc) and interactive chroot workflows, the…azldev-overlay-metadataRead this before adding or reviewing an overlay `metadata` table; do not guess the category or upstream status from memory. Explains the overlay metadata schema that documents why an overlay exists and when it can be dropped, covering the required category…azldev-overlaysRead this before adding, changing, or diagnosing any overlay; never edit a spec or rendered file from memory. Explains how to modify a component's RPM spec or loose source files with azldev overlays (semantic patches applied at render time) instead of forking…azldev-remove-componentRead this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state. Explains the manual removal workflow for deleting component metadata, cleaning references, and validating any related…
agents-sdk-typescript-otelUse when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in JavaScript or TypeScript. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire…agents-sdk-to-prodUse when a user wants to assess, create, harden, deploy, or review the production readiness of JavaScript or TypeScript code built with the Microsoft 365 Agents SDK. Do not use for unrelated applications, services, or code that does not run or support an…agents-sdk-to-prodAssess, create, harden, deploy, or review production readiness of C#/.NET Microsoft 365 Agents SDK agents and their direct hosting/operations files. Use only for Agents SDK scenarios, not unrelated application hardening.agents-sdk-to-prodAssess, create, harden, deploy, or review production readiness of Python Microsoft 365 Agents SDK agents and their direct hosting/operations files. Use only for Agents SDK scenarios, not unrelated application hardening.teams-sdk-to-agents-sdk-dotnet-migrationUse when migrating a customer's Teams SDK (teams.net) bot to the Microsoft 365 Agents SDK in .NET. Triggered by projects that depend on Microsoft.Teams.Plugins.AspNetCore, Microsoft.Teams.Apps, or Microsoft.Teams.Api and call builder.AddTeams() /…teams-app-manifestCreate or audit a Microsoft Teams app manifest for an existing Microsoft 365 Agents SDK application by mapping declared intent and source-code evidence to released manifest capabilities. Use when manifest.json is missing, incomplete, or must be checked…sync-teams-dotnet-samples-to-agents-sdkCI instructions for a bounded Teams SDK .NET to Agents SDK sample synchronization.agents-sdk-python-otelUse when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in Python. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard,…
azuresql-db-containerRuns the Azure SQL Database container locally (Private Preview): the real PaaS engine where SERVERPROPERTY('EngineEdition') returns 5. This is NOT the SQL Server image mcr.microsoft.com/mssql/server. Use when a user wants to "run Azure SQL locally", "add a…azuresql-db-faqAnswers questions about what the Azure SQL Database container (Private Preview) can and cannot do, and WHY it differs from Azure SQL Database in the Microsoft Azure cloud. Use when a user asks "can I take a backup", "why does USE fail", "is X supported", "why…azuresql-db-sidecarAdds the Azure SQL Database container as a sidecar service in an existing Docker Compose stack or Dev Container. Use when wiring the local Azure SQL Database engine into compose or devcontainer.json, when an app needs a SQL backend via a service name (not…azuresql-db-authConnects an app to the Azure SQL Database container securely, with a least-privilege database user instead of the sa login, the right auth method per environment, and safe handling of the connection secret. Use when a user asks "don't use sa in my app",…azuresql-db-ciRuns integration tests against the Azure SQL Database container (Private Preview, local engine) in CI. Use when setting up GitHub Actions, Azure Pipelines, or GitLab CI to test against Azure SQL DB; when adding a database service container to a CI workflow;…azuresql-db-connectionsMakes an app's database connections reliable against the local Azure SQL Database container (Private Preview) and, unchanged, against Azure SQL Database in the cloud: connection pooling plus retry/transient-fault handling. Use when the user mentions…azuresql-db-dabStands up an instant no-code REST + GraphQL API over the local Azure SQL Database container using Microsoft Data API Builder (DAB). Use when a user wants to "expose my table as an API", "add a REST API over the database", "generate a GraphQL API", "put an API…azuresql-db-from-sql-serverMigrates a local SQL Server setup to the Azure SQL Database container for Azure-faithful local development. Use when a project already uses mcr.microsoft.com/mssql/server, mssql/server, an sqlcmd plus SA password docker setup, a "SQL Server in docker" or…
workiq-previewWorkIQ tools for Microsoft 365 workplace data and actions. Use for email, meetings, calendar, files, SharePoint, OneDrive, Teams, people, Planner, and connected work context. Triggers include gather requirements, summarize workplace discussions, manage…workiqWorkIQ tools for Microsoft 365 workplace data and actions. Use for email, calendar events and meetings, files, SharePoint, OneDrive, Teams, people, Planner, and other M365 requests. Triggers include cancel meeting or event, accept or decline meetings, create…declarative-agent-developerEntry point for Microsoft 365 Copilot declarative-agent authoring and lifecycle requests. Use for scaffolding, manifest edits, capabilities, API or MCP actions, authentication, localization, instruction design and review, validation, packaging, provisioning,…setup-sso-ui-widgetAdds Microsoft Entra SSO (single sign-on, no OBO) to a Microsoft 365 Copilot declarative agent whose tools are served by an MCP server — for BOTH widget standards: (1) the MCP Apps standard (from create-mcp-app / the MCP Apps SDK): a plugin manifest such as…planner-status-reportGenerates a Microsoft Planner status report for one plan, using task status, owners, dates, priorities, buckets, risks, wins, progress, upcoming commitments, and milestones.ui-widget-developerBuild MCP servers for Copilot Chat using the OpenAI Apps SDK or MCP Apps SDK widget rendering support (any language). Use this skill when: - Creating MCP servers that integrate with M365 Copilot declarative agents - Building rich interactive widgets (React +…action-item-extractorExtract action items with owners, deadlines, and priorities from meeting contentchannel-auditAudit Teams channels across your teams — identify inactive channels, low‑engagement conversations, channels with no recent posts, and recommend cleanup actions.