GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills，按职业与使用场景整理，复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoft
openclaw
@openclaw
OpenAI
@openai
The Apache Software Foundation
@apache
GitHub
@github
Anthropic
@anthropics
AutoGPT
@Significant-Gravitas
Garry Tan
@garrytan全部 Skills 192262
verify-real-surface
Verify a requested behavior through its real UI, CLI, or API surface when tests alone are insufficient. Use after user-facing behavior changes or when asked to prove behavior; do not use for structural-only edits or broad exploratory audits.
unslop
Cut AI tells from any writing. Must always apply.
unattended-run
Persist on one explicitly authorized task while the user is away, continuing through verified units and evidence-backed pivots until its finish line is met. Use only for requests such as "keep working", "run until done", or "going to bed"; do not use to expand ordinary work autonomously.
no-sloppy
Deterministic anti-slop pass for Python. After writing or editing Python code, run the bundled checker before declaring the work done; it lints just the changed lines with an opinionated ruff overlay plus custom slop rules. Use for any non-trivial Python change.
no-slop-ts
Deterministic anti-slop pass for TypeScript/JavaScript. After writing or editing TS/JS code, run the bundled checker before declaring the work done; it lints just the changed lines with an oxlint overlay plus the vendored anti-slop rules. Use for any non-trivial TypeScript or JavaScript change.
grilling
Resolve material product and design decisions before planning or implementing an ambiguous large feature. Use when the user asks to be grilled or when several valid interpretations would produce meaningfully different behavior, architecture, cost, or migration work; do not use for questions, small changes, or facts the repository can answer.
experiment-loop
Run a bounded empirical research loop using Pi background terminals - launch experiments, analyze evidence, and refine the stated hypothesis. Use for explicit research or experiment requests; do not use for ordinary implementation work or open-ended exploration.
code-style
Review, write, and edit non-trivial code using the project's conventions and these code style rules. Read the applicable language reference. For read-only reviews, report findings without edits; run change-verification checks after editing.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
swarm
Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
statechart
Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use for /statechart, or to show a bug as a path through states.
show-me-your-work
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.
sharpen
Make a task deeper, not bigger, then rewrite the prompt. Use for /sharpen.