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).
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
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).
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.
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.
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.
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.
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.
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.
Steady2 mentions in 2 weeks
No other project uses it yet
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.
Steady2 mentions in 2 weeks
2 projects use a version of this
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.
Steady2 mentions in 2 weeks
5 projects use a version of this
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.
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.
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…
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.
Steady11 mentions in 2 weeks
6 projects use a version of this
microsoft/agent-framework/dotnet/.github/skills/project-structure/SKILL.md
Explains the project structure of the agent-framework .NET solution
Steady11 mentions in 2 weeks
21 projects use a version of this
microsoft/agent-framework/dotnet/.github/skills/pull-requests/SKILL.md
Guidance for creating pull requests and handling PR review comments in the Agent Framework repository. Use this when writing a PR description (filling out the PR template) or when responding to and resolving review comments on an existing PR.
Steady11 mentions in 2 weeks
15 projects use a version of this
microsoft/agent-framework/dotnet/.github/skills/verify-dotnet-samples/SKILL.md
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.
Steady11 mentions in 2 weeks
No other project uses it yet
microsoft/agent-framework/dotnet/.github/skills/verify-samples-tool/SKILL.md
The verify-samples project (dotnet/eng/verify-samples/) is an automated tool that runs sample projects and verifies their output using deterministic checks and AI-powered verification. Important: By default, samples must be pre-built before running verify-samples. Build the solution first, or pass --build to build samples during the run: Then run verify-samples: The tool itself needs: - AZURE_OPENAI_ENDPOINT — for the AI verification agent - AZURE_OPENAI_DEPLOYMENT_NAME (optional, defaults to gpt-5-mini) Individual samples require their own env vars (for example, FOUNDRY_PROJECT_ENDPOINT). The tool automatically checks…
Steady11 mentions in 2 weeks
No other project uses it yet
microsoft/agent-framework/dotnet/samples/02-agents/AgentSkills/Agent_Step01_FileBasedSkills/skills/unit-converter/SKILL.md
Convert between common units using a multiplication factor. Use when asked to convert miles, kilometers, pounds, or kilograms.
Steady11 mentions in 2 weeks
3 projects use a version of this
microsoft/agent-framework/dotnet/samples/02-agents/AgentSkills/Agent_Step04_MixedSkills/skills/unit-converter/SKILL.md
Convert between common units using a multiplication factor. Use when asked to convert miles, kilometers, pounds, or kilograms.
Steady11 mentions in 2 weeks
3 projects use a version of this
microsoft/agent-framework/dotnet/samples/02-agents/Harness/BuildYourOwnClaw/Claw_Step03_ScalingCapabilities/skills/risk-scoring/SKILL.md
Score how concentrated and risky a portfolio is on a 0-100 scale from its position weights. Use when the user asks how risky their portfolio is, whether it is too concentrated, or for a diversification check.
Steady11 mentions in 2 weeks
2 projects use a version of this
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.