Agent Skills

apm-spec-guardian

✓★ 3,123

by microsoft

Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running

🧰 Not standalone — use together with microsoft/apm

batch-bug-shepherd

✓★ 3,123

by microsoft

Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then open a fix PR (TDD + mutation-break gate) for greenfield bugs. Drive every PR -- community in-flight and own fix alike -- to mergeable by composing the shepherd-driver skill: one dr

🧰 Not standalone — use together with microsoft/apm

cut-release

✓★ 3,123

by microsoft

Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "rele

🧰 Not standalone — use together with microsoft/apm

docs-corpus-audit

✓★ 3,123

by microsoft

Use this skill to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims. Activate when the maintainer wants a WHOLE-CORPUS audit (not per-PR review) -- typical triggers include "audit the docs", "reground the corpus", "check every page against code", "pre-release docs sweep", "the docs have drifted everywhere", or "we just reshaped the TOC, find dead links". Wave-batched and S7-verified

🧰 Not standalone — use together with microsoft/apm

docs-grounding-verifier

✓★ 3,123

by microsoft

Use this skill to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code. Activate when you have specific pages to check for factual accuracy -- not when sweeping a whole corpus (use docs-corpus-audit for that) and not when triaging a PR diff (use docs-sync for that). Trigger nouns: "is this doc accurate", "verify the page against the code", "fact-check this section", "any claims that drifted from source", "fact-checking", "grounding audit", "drift hunt",

🧰 Not standalone — use together with microsoft/apm

docs-impact-architect

✓★ 3,123

by microsoft

Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.

🧰 Not standalone — use together with microsoft/apm

docs-impact-classifier

✓★ 3,123

by microsoft

Use this skill to classify the documentation impact of a pull request diff, returning one of three verdicts -- no-change, in-place edit, or structural change -- with bounded LLM cost. Activate as a sibling skill of docs-sync; the orchestrator calls this first, before any panel spawn, to keep cost floor at 1 LLM call when no docs work is needed. Reads .apm/docs-index.yml as the corpus map; never reads the full corpus.

🧰 Not standalone — use together with microsoft/apm

docs-impact-localizer

✓★ 3,123

by microsoft

Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict in_place; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.

🧰 Not standalone — use together with microsoft/apm

docs-sync

✓★ 3,123

by microsoft

Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-w

🧰 Not standalone — use together with microsoft/apm

example-skill

✓★ 3,123

by microsoft

An example skill from the mock plugin

🧰 Not standalone — use together with microsoft/apm

{{project_name}}

✓★ 3,123

by microsoft

{{description}}

🧰 Not standalone — use together with microsoft/apm

placeholder

✓★ 3,123

by microsoft

🧰 Not standalone — use together with microsoft/apm

shepherd-driver

✓★ 3,123

by microsoft

Use only as the composed drive-to-merge stage of an APM batch orchestrator (batch-bug-shepherd, apm-issue-autopilot) that has already selected ONE open pull request in microsoft/apm. Do NOT use for user-facing requests to triage issues, sweep a queue, or open PRs -- the parent orchestrator owns those. Spawn one shepherd-driver subagent per PR: it classifies copilot-pull-request-reviewer[bot] inline review, runs the apm-review-panel, folds (by default) every recommendation inside the PR's stated

🧰 Not standalone — use together with microsoft/apm

cli-logging-ux

✓★ 3,123

by microsoft

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.

🧰 Not standalone — use together with microsoft/apm

devx-ux

✓★ 3,123

by microsoft

Activate when designing or modifying CLI command surfaces, command help text, install/init/run flows, error wording, or first-run experience in the APM CLI -- even when the user does not say "UX" explicitly.

🧰 Not standalone — use together with microsoft/apm

supply-chain-security

✓★ 3,123

by microsoft

Activate when reviewing or modifying dependency resolution, lockfile schema, package downloaders, signature/integrity checks, file integration cleanup, or anything that could expose APM to dependency confusion, typosquatting, malicious packages, or token leakage.

🧰 Not standalone — use together with microsoft/apm

create-pull-request

✓★ 2,599

by microsoft

Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

summarize-github-issue-pr-notification

✓★ 2,599

by microsoft

Summarizes the content of a GitHub issue, pull request (PR), or notification, providing a concise overview of the main points and key details. ALWAYS use the skill when asked to summarize an issue, PR, or notification.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

suggest-fix-issue

✓★ 2,599

by microsoft

Given the details of an issue, suggests a fix for the issue.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

show-github-search-result

✓★ 2,599

by microsoft

Summarizes the results of a GitHub search query in a human friendly markdown table that is easy to read and understand. ALWAYS use this skill when displaying the results of a GitHub search query.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

write-changelog

✓★ 2,599

by microsoft

Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

form-github-search-query

✓★ 2,599

by microsoft

Forms a GitHub search query based on a natural language query and the type of search (issue or PR). This skill helps users create effective search queries to find relevant issues or pull requests on GitHub.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

address-pr-comments

✓★ 2,599

by microsoft

Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

pytest

✓★ 2,433

by microsoft

Best practices for writing and organizing tests with pytest including fixtures, parametrize, and plugins.

🧰 Not standalone — use together with microsoft/debugpy

requests

✓★ 2,433

by microsoft

Best practices for HTTP client usage with Requests including sessions, error handling, and timeouts.

🧰 Not standalone — use together with microsoft/debugpy

numpy

✓★ 2,433

by microsoft

Best practices for numerical computing with NumPy including arrays, broadcasting, and vectorization.

🧰 Not standalone — use together with microsoft/debugpy

click

✓★ 2,433

by microsoft

Best practices for building CLI applications with Click including commands, groups, options, and testing.

🧰 Not standalone — use together with microsoft/debugpy

flask

✓★ 2,433

by microsoft

Best practices for Flask web development including routing, blueprints, and testing.

🧰 Not standalone — use together with microsoft/debugpy

django

✓★ 2,433

by microsoft

Best practices for Django web development including models, views, templates, and testing.

🧰 Not standalone — use together with microsoft/debugpy

jinja2

✓★ 2,433

by microsoft

Best practices for template rendering with Jinja2 including environments, filters, autoescaping, and security.

🧰 Not standalone — use together with microsoft/debugpy