MicrosoftSkilltest-management
microsoft/aspire/.agents/skills/test-management/SKILL.md
Quarantines or disables flaky/problematic tests using the QuarantineTools utility
Find the best CLAUDE.md, AGENTS.md and Claude skills
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Most stars first · from page 30Worked for most · soon
MicrosoftSkillMicrosoftSkillupdate-container-images
microsoft/aspire/.agents/skills/update-container-images/SKILL.md
Updates Docker container image tags used by Aspire hosting integrations. Queries registries for newer tags, uses LLM to determine version-compatible updates, and applies changes. Use this when asked to update container image versions.
MicrosoftSkillvscode-extension
microsoft/aspire/.agents/skills/vscode-extension/SKILL.md
Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension/, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features.
MicrosoftAGENTS.mdVFSForGit
microsoft/VFSForGit/AGENTS.md
This file is for AI coding assistants (GitHub Copilot, Claude Code, Cursor, OpenAI Codex, Gemini CLI, Aider, etc.). It captures project-specific knowledge that isn't obvious from a fresh git clone and which routinely trips up agents. See CONTRIBUTING.md for coding standards (StyleCop rules, error handling, exception logging) — do not duplicate those here. The build scripts (scripts\Build.bat and friends) put build outputs one level up from the git working tree. The Readme documents the recommended clone-into-src\ convention, which matches the…
MicrosoftAGENTS.mdtypespec
microsoft/typespec/AGENTS.md
Alloy is a code generation framework using JSX components. Before working with Alloy code, read the relevant docs from installed packages. Your training data may be outdated — these docs match your installed version.
MicrosoftCopilot instructionstypespec
microsoft/typespec/.github/copilot-instructions.md
ALWAYS follow these instructions first and only fall back to additional search and context gathering if the information here is incomplete or found to be in error. TypeSpec is a language for defining cloud service APIs and shapes. This monorepo contains the TypeSpec compiler, standard library packages, tools, documentation, and various language client emitters. [!IMPORTANT] These instructions do NOT apply to the language emitter packages (http-client-csharp, http-client-java, http-client-python). Those packages are excluded from the pnpm workspace and do not require…
MicrosoftSkillcode-review
microsoft/typespec/.github/skills/code-review/SKILL.md
Review TypeSpec pull requests against the project's own rules: the Tier 0-3 breaking change policy, `.chronus` changelog requirements, compiler API usage, test framework conventions, and emitter output stability. Use when reviewing a diff or pull request in this repository.
MicrosoftSkillemitter-prep-for-pr
microsoft/typespec/.github/skills/emitter-prep-for-pr/SKILL.md
Prepare language emitter changes for PR: validate (build, format, lint), add a changeset, and push. This skill is specifically for the language emitter packages (http-client-python, http-client-csharp, http-client-java) - NOT for core TypeSpec packages like compiler, http, openapi3, etc. Use when the user wants to finalize emitter changes, says things like "prep for pr", "prepare for PR", "validate and push", "add changeset", or "finalize changes".
MicrosoftSkillhttp-client-python-bump-and-release
microsoft/typespec/.github/skills/http-client-python-bump-and-release/SKILL.md
Create a PR to bump TypeSpec/Azure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.
MicrosoftSkillpnpm-format
microsoft/typespec/.github/skills/pnpm-format/SKILL.md
Format the codebase with pnpm and recover from common formatting failures.
MicrosoftSkillwriting-python-sdk-spector-mock-api-tests
microsoft/typespec/.github/skills/python-sdk-spector-mock-api-tests/SKILL.md
Writes TypeSpec http-client-python generator mock API tests (azure/unbranded/shared) from a Spector case. Use when given a Spector case link or a PR link that modifies Spector cases under http-specs/azure-http-specs.
MicrosoftCopilot instructionstypespec / http-client-java
microsoft/typespec/packages/http-client-java/.github/copilot-instructions.md
See http-client-java-development for instructions on how to develop the TypeSpec library for Java client.
MicrosoftCopilot instructionstypespec / http-client-js
microsoft/typespec/packages/http-client-js/.github/copilot-instructions.md
Scope: These instructions apply only to the packages/http-client-js sub-project in this monorepo. Use them whenever Copilot generates code, tests, commit messages, or pull request descriptions for the emitter. If Copilot is used in other sub-projects, these rules do not apply unless stated otherwise. - Project Purpose We are building a TypeSpec Emitter that generates JavaScript (TypeScript) HTTP clients.
MicrosoftSkillgenerate-from-typespec
microsoft/typespec/packages/http-client-python/.github/skills/generate-from-typespec/SKILL.md
Generate Python SDK code from a TypeSpec specification using the local emitter. Use this skill when the user wants to generate/regenerate a Python client from a TypeSpec spec, provides a GitHub URL or local path to a TypeSpec project, or says things like "generate from this spec", "emit Python from this tsp", "regenerate the SDK", or "compile this TypeSpec for Python".
MicrosoftSkilltest-unbranded-emitter
microsoft/typespec/packages/http-client-python/.github/skills/test-unbranded-emitter/SKILL.md
Build and test the @typespec/http-client-python emitter. Use this skill whenever the user wants to test their local changes to the emitter, run the generator test suite, check if their http-client-python changes are passing, or validate a fix. Triggers on phrases like "test the emitter", "run tests", "check if my changes pass", "run test:generator", "run CI", or any mention of testing/validating changes in the emitter package.
MicrosoftSkillazldev-add-component
microsoft/azurelinux/.agents/skills/azldev-add-component/SKILL.md
Read 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, diff-sources, and build. Triggers include add component, new package, import package, create comp.toml, new component.
MicrosoftSkillazldev-build-component
microsoft/azurelinux/.agents/skills/azldev-build-component/SKILL.md
Read 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 inner loop, diff-sources, and disabling a failing %check via check.skip. Triggers include build component, build failed, build error, inner loop, preserve buildenv, local repo, disable check.
MicrosoftSkillazldev-comp-toml
microsoft/azurelinux/.agents/skills/azldev-comp-toml/SKILL.md
Read 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, file organization, overlay hygiene, stale files, disabled tests, and testing verification. Triggers include comp.toml, component config, review component, component hygiene, spec source, upstream-distro, build defines, release calculation, includes.
MicrosoftSkillazldev-image
microsoft/azurelinux/.agents/skills/azldev-image/SKILL.md
Read 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 KIWI NG. Triggers include image build, image boot, kiwi, container image, VM image, images.toml.
MicrosoftSkillazldev-mock
microsoft/azurelinux/.agents/skills/azldev-mock/SKILL.md
Read 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 -p/--add-package flag, and resetting stale chroot state. Triggers include test package, mock shell, inspect rpm, smoke test, chroot, verify build output.
Agent instruction files
What are agent instruction files?
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.