GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoftopenclaw
@openclawAnthropic
@anthropicsOpenAI
@openaiThe Apache Software Foundation
@apacheGitHub
@githubAutoGPT
@Significant-GravitasGarry Tan
@garrytan全部 Skills 482556
documentation-writer
Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use /skill-writer instead.
adhd-mode
Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says "stop adhd mode". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.
wait-what
That last message didn't land: re-explain it with the missing context.
to-questionnaire
Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.
research
Investigates a question against primary sources (official docs, source code, specs, first-party APIs) and writes the findings, with a citation for every claim, to a Markdown file. Use when the user wants a topic researched or facts gathered from documentation, when a decision waits on facts from outside the repo, and when reading legwork should run while other work continues.
grilling
Interviews the user relentlessly about a plan, design, decision, or idea until every branch of the decision tree is resolved and nothing is silently assumed. Use when the user says "grill me" or wants to stress-test their thinking, before building something whose requirements are still fuzzy, and when another skill needs a structured interview.
grill-with-docs
A relentless interview to sharpen a plan or design that also keeps the project's glossary and decision records up to date as answers land.
grill-me
A relentless interview to sharpen a plan or design.
domain-modeling
Builds and sharpens a project's domain language as decisions are made: challenges fuzzy or conflicting terms, stress-tests concepts with edge-case scenarios, and records resolved terms in GLOSSARY.md and hard-to-reverse decisions as ADRs. Use when discussing what the project's terms mean, when writing or editing a glossary or an ADR, and during design interviews.
wayfinder
Plan work too big for one session as a map of decision tickets, resolved one at a time.
triage
Move incoming issues (and optionally external PRs) through triage states to agent-ready briefs.
to-tickets
Split a spec into tracer-bullet sub-issues with blocking links.
to-spec
Turn the current conversation into a spec issue, without re-interviewing.
standup
Daily standup from git history and GitHub activity: what changed since yesterday, what's in flight, what's blocked.
shortcut-ledger
Collects every `shortcut:` comment in the codebase into a ledger of deliberate simplifications, each with its ceiling and the trigger for revisiting it, and flags the ones with no trigger. Use when grooming the backlog, when the user asks what shortcuts or deferred work the code carries, and before planning work in an area with marked shortcuts.
session-retro
Capture a work session as a structured retro doc in docs/sessions/
issue-update
Updates an existing GitHub issue: edits the body, posts a comment, retags, or reopens, acknowledging stale framing instead of silently rewriting it, and previews before applying. Use when the user asks to update, comment on, relabel, or reopen an issue, or when a workflow needs to post a progress checkpoint to a tracking issue.