MCP server "agtgovernance" as configured in microsoft/agent-governance-toolkit. Launched with ${CLAUDE_PLUGIN_ROOT}/bin/agt-node ${CLAUDE_PLUGIN_ROOT}/server/agt-mcp.mjs.
Instructions for microsoft/VFSForGit, covering agent instructions for vfs for git, repository layout, recommended (matches readme.md and ci), build paths and path a — unit-test inner loop (10–15 s incremental).
Turn your coding agent into a SOTA browser agent. Drives a local Playwright workspace via one bash command at a time, saving screenshots and an action log into finalruns/run /, and visually self-verifies the result.
Solve a user-specified web task code-as-action style by driving a local Playwright browser through one bash command at a time, saving screenshots and an action log into finalruns/run /, and visually verifying the result. Use when the user asks to automate a web task (search, filter, form-fill, multi-step flow, data…
Instructions for microsoft/FLAML, covering github copilot instructions for flaml, project overview, build and test commands, installation and basic installation.
Use when: adding a new chart type to flint-chart, implementing chart templates across Vega-Lite, ECharts, Chart.js, gallery examples, test cases, or VLM rendering verification.
Model Context Protocol server for Flint — compile, validate, and render semantic chart specs across supported backends. Runs locally from the flint-chart-mcp npm package.
Use when: the user asks to make or render charts with flint-chart, visualize tabular data, generate a ChartAssemblyInput, validate/render through MCP, or add Flint to a JS/TS project. Author the semantic spec, transform data before Flint when needed, install/import Flint only when executable code is needed, and…
Use when: creating, translating, refining, reviewing, or validating a custom Flint ThemeSpec from brand guidelines, websites, slide decks, publication references, design tokens, or an existing visual identity. Produce a reusable ThemeSpec JSON object for Flint Theme Lab without inventing fields or changing chart…
Instructions for microsoft/skill-recorder, covering repository instructions for coding agents and pull requests target the active release branch, not main.
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
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…
Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.