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

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.

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…

No other project uses it yet

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-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. You need Python 3.10+, git, Node.js and npm. When DRIVER_VERSION changes, for example after a pull, run python scripts/upstream.py checkout and…

No other project uses it yet

MicrosoftSkill

playwright-release

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

Prepare a Playwright Python 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.

No other project uses it yet

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.

MicrosoftSkill

playwright-triage

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

Triage and fix one microsoft/playwright-python issue, or do a maintainer's task, unattended inside the Issue triage GitHub Actions workflow (.github/workflows/triage.yml), which a needs-triage, needs-triage-mac or needs-triage-win label starts, or a maintainer starts by hand with an issue, a task or both. Reproduces the issue on the runner, then leaves a verified fix proposal for the workflow to open as a draft PR, an investigation note for it to post on the issue, or an upstream bug report for a maintainer to file in microsoft/playwright. Only for that workflow.

MicrosoftReads credentialsAGENTS.md

playwright-python / _impl

microsoft/playwright-python/playwright/_impl/AGENTS.md

These rules say how to write playwright/_impl from packages/playwright-core/src/client in microsoft/playwright. Use them at each roll, for every new or changed line of the client. The upstream code is in .upstream/, the checkout at the commit in DRIVER_VERSION. The steps of a roll are in the playwright-roll skill. The port is line by line. The structure of the Python follows the JavaScript. The timing of the Python follows asyncio. A reviewer reads the .ts file and the .py file side…

No other project uses it yet

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

MicrosoftCLAUDE.md

playwright-cli

microsoft/playwright-cli/CLAUDE.md

The CLI source lives in microsoft/playwright, in packages/playwright-core/src/tools/. This repo ships @playwright/cli: playwright-cli.js runs the CLI of the playwright-core alpha that package.json pins, and adds the update check, with skillCheck.js. skills/playwright-cli/ is a copy of the skill that playwright-cli install --skills writes, and node scripts/update.js refreshes it. There is no build step and no lint. Tests are in tests/integration.spec.ts. They run playwright-cli.js with runCli() in the output directory of the test, and the npmRegistry fixture serves a fake registry for…

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-triage

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

Triage and fix one microsoft/playwright-cli issue, or do a maintainer's task, unattended inside the Issue triage GitHub Actions workflow (.github/workflows/triage.yml), which a needs-triage, needs-triage-mac or needs-triage-win label starts, or a maintainer starts by hand with an issue, a task or both. Reproduces the issue on the runner, then leaves a verified fix proposal for the workflow to open as a draft PR, in this repo or in microsoft/playwright where the source of the CLI is, or an investigation note for it to post on the issue. Only for that workflow.

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.

MicrosoftSkill

core

microsoft/RD-Agent/rdagent/scenarios/rl/autorl_bench/core/skill.md

你负责维护实验的累积运行总结文件 reports/summary.md。 每轮实验结束后，你需要用 file_editor 在 reports/summary.md *末尾追加*一个新 section。 如果 reports/summary.md 不存在，先创建文件，首行写 # 运行总结。 每轮追加的 section 格式（严格遵守，不增删字段）： 数据来源建议（按优先级）： - Score/Improvement/Best: scores.json 或服务器返回 - 状态/耗时/exit_code: run.log - 训练类型/关键配置/关键代码: code/train.py - 失败根因: agent.log + run.log 规则： 1. 追加，不要覆盖已有内容 2. 必须按 Iteration 递增写入：读取 reports/summary.md 中最后一个迭代号，当前必须是 N+1；若不满足先修正再写 3. 分析 code下面的 源码，提取训练类型和超参数；若无法确定写 unknown，不留空 4. 如果训练失败，必须给出可定位的根因（日志片段或错误类型），并标注 failure_type（如：code_error_runtime / rollout_logic_wrong / timeout_no_submission / copy_model_fallback / training_diverged / unknown） 5. “做了什么”“为什么”是最重要字段，必须可复现、可检验，且“为什么”必须引用上轮证据（scores.json/run.log/agent.log） 6. 问题/进步 必须包含过程指标或失败类型（如：valid_submission_rate / first_valid_idx / time_to_first_improvement / time_used_ratio / failure_type） 7. 长代码片段每轮最多 1 段，最多 40 行；优先贴本轮新增或改动处；若与上轮相同写“与 Iteration…

MicrosoftAGENTS.md

agent-framework / dotnet

microsoft/agent-framework/dotnet/AGENTS.md

Instructions for AI coding agents working in the .NET codebase. See ./.github/skills/build-and-test/SKILL.md for detailed instructions on building, testing, and linting projects. See ./.github/skills/project-structure/SKILL.md for an overview of the project structure. See ./.github/skills/pull-requests/SKILL.md for guidance on writing PR descriptions and handling/resolving PR review comments. The framework integrates with Microsoft.Extensions.AI and Microsoft.Extensions.AI.Abstractions (external NuGet packages) using types like IChatClient, FunctionInvokingChatClient, AITool, AIFunction, ChatMessage, and AIContent. When developing or reviewing code, verify adherence to these key design principles: Samples (in ./samples/ folder) should…

No other project uses it yet

MicrosoftSkill

build-and-test

microsoft/agent-framework/dotnet/.github/skills/build-and-test/SKILL.md

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.