Find the best CLAUDE.md, AGENTS.md and Claude skills

MicrosoftSkill

language-injection

microsoft/data-formulator/.cursor/skills/language-injection/SKILL.md

LLM Agent 多语言注入规范。在修改 Agent 提示词、添加新的 Agent 端点、处理用户可见的后端消息（message_code）时使用。

MicrosoftSkill

path-safety

microsoft/data-formulator/.cursor/skills/path-safety/SKILL.md

服务端路径安全与文件访问编码规范。在编写文件下载路由、Agent 工具（文件读取/目录列出）、数据连接器/Loader、Workspace 路径操作、沙箱配置时使用。

MicrosoftCopilot instructions

data-formulator

microsoft/data-formulator/.github/copilot-instructions.md

No summary in the file. Open it to read it.

No other project uses it yet

MicrosoftSkill

core

microsoft/data-formulator/py-src/data_formulator/analyst/skills/core/SKILL.md

The analyst's built-in capabilities: data-inspection tools and the always-available actions (visualize and ask_user).

MicrosoftSkill

data-loading

microsoft/data-formulator/py-src/data_formulator/analyst/skills/data-loading/SKILL.md

Discover connected data sources, add new data connectors through a user-confirmed form, inspect table metadata, and run bounded read-only probes when the current workspace data is insufficient.

MicrosoftSkill

report

microsoft/data-formulator/py-src/data_formulator/analyst/skills/report/SKILL.md

Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

MicrosoftAGENTS.md

pyright

microsoft/pyright/AGENTS.md

Pyright is a Python static type checker written in TypeScript. Before changing code, read the repository Copilot instructions and the applicable contributor and test-policy guidance. For a reported issue, use…

MicrosoftCopilot instructions

pyright

microsoft/pyright/.github/copilot-instructions.md

Pyright is a static type checker for Python, written in TypeScript. It ships as an npm CLI (pyright), an LSP language server (pyright-langserver), and a VS Code extension (vscode-pyright). Use…

MicrosoftSkill

evaluation-tracing

microsoft/pyright/.github/skills/evaluation-tracing/SKILL.md

Investigate Pyright type-inference or cache regressions, unexpected or lost diagnostics, speculative or reentrant evaluation, evaluator state changes, and repeated evaluator work using local evaluation traces.

MicrosoftSkill

pyright-issue-analysis

microsoft/pyright/.github/skills/pyright-issue-analysis/SKILL.md

Investigate Pyright issues using minimal repros, CPython semantics, the typing specification, and mypy comparisons. Use for issue triage, maintainer response drafts, or evidence-backed issue fixes and PRs.

MicrosoftSkill

pyright-pr-typespec-review

microsoft/pyright/.github/skills/pyright-pr-typespec-review/SKILL.md

Investigate whether a Pyright PR changes typing behavior safely by tracing its diff, designing adversarial cases, comparing exact revisions, and checking relevant CPython behavior. Use for requests to find regressions, assess merge safety, or test effects beyond a PR's own examples.

MicrosoftAGENTS.md

playwright-cli

microsoft/playwright-cli/AGENTS.md

This repo ships the npm package @playwright/cli. The CLI itself is in microsoft/playwright, in packages/playwright-core/src/tools/: cli-client/ has the commands and their options, cli-daemon/ has the daemon that keeps the browser open between commands, and backend/ has the tools that the commands run. - What this repo owns: playwright-cli.js, which runs the CLI of the pinned playwright-core and adds the update check, skillCheck.js, the README, and the tests of the packaged CLI. - What is a copy: skills/playwright-cli/ is a copy…

MicrosoftSkill

dev

microsoft/playwright-cli/.claude/skills/dev/SKILL.md

Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.

MicrosoftSkill

playwright-cli

microsoft/playwright-cli/skills/playwright-cli/SKILL.md

Automate browser interactions, test web pages and work with Playwright tests.

Often used withfabric-sdk·ecosystem-reference·fractal-delegation

MicrosoftAGENTS.md

playwright-python

microsoft/playwright-python/AGENTS.md

Python bindings for Playwright. The client in playwright/_impl/ talks to the Node.js driver in playwright/driver/ over a pipe. Everything comes from microsoft/playwright at the commit in DRIVER_VERSION: the driver, the generated API and the code that we port. .upstream/ is a full clone of it (gitignored). Read upstream code there. Do not edit, commit or switch branches in it. The client talks to the Node.js driver that is built from .upstream/. When the same calls fail in a Node.js test…

MicrosoftSkill

playwright-patch-release

microsoft/playwright-python/.claude/skills/playwright-patch-release/SKILL.md

Prepare a patch release of Playwright Python (v1.xx.1 and later) from a release branch. Picks the next version, writes the release notes as the list of fixes in microsoft/playwright between the driver of the previous release of the branch and the driver of its tip, and saves them as a draft GitHub release, in place of an old draft. Never publishes the release.

MicrosoftSkill

playwright-release

microsoft/playwright-python/.claude/skills/playwright-release/SKILL.md

Prepare a new Playwright Python release, v1.xx.0, with the full release notes. For a patch release of a release branch, use playwright-patch-release. Checks open bugs, adds Python-specific changes to the Python release notes in microsoft/playwright, opens the release PR, cuts the release branch, and saves a draft GitHub release. Never publishes the release.

MicrosoftSkill

playwright-roll

microsoft/playwright-python/.claude/skills/playwright-roll/SKILL.md

Roll Playwright Python to a new microsoft/playwright commit. Pins the commit, generates the API and builds the driver from it, and ports the upstream diff of the client and the tests.

MicrosoftAGENTS.md

playwright-python / tests

microsoft/playwright-python/tests/AGENTS.md

These rules say how to write tests/async/{page,library} and tests/sync/{page,library} from tests/page and tests/library in microsoft/playwright, at the commit in DRIVER_VERSION. Use them at each roll, for every new or changed upstream test. The upstream tests are in .upstream/, the checkout at that commit. The steps of a roll are in the playwright-roll skill. The port is line by line, with zero deviations. A reviewer reads the .spec.ts file and the two .py files side by side. Each upstream statement maps…

No other project uses it yet

MicrosoftAGENTS.md

RD-Agent / claude

microsoft/RD-Agent/rdagent/scenarios/rl/autorl_bench/agents/claude/AGENTS.md

You MUST maintain a file called summary.md in the workspace root. Update it after every training attempt and every submission, not just at the end.