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
show-me-your-work
Record decisions in an append-only TSV file while running long or unattended work, audit it against your own transcript before replying, and have a second reviewer flag what the user should check. Use on /show-me-your-work, for autonomous or multi-phase runs, or whenever a skill needs an audit trail.
sharpen
Rewrite a draft prompt so it asks for an expert-depth version of the same task (expert moves, raw sources, named methods, an outside check) without widening scope. Returns the rewritten prompt and does not do the task. Use for "/sharpen <prompt>" or "make this prompt better before I send it".
setup-endostack
Configure EndoStack. Detect which models this agent's subagents can use, pick a reasoning budget, map each EndoStack role to a tier or model, and write models.toml. Use for "set up EndoStack", first-time setup, changing models or budget, or cutting EndoStack's cost.
security-review
Review a diff, branch, or PR for exploitable security defects. Fans out read-only subagents per defect class (injection, authz, secrets, SSRF, supply chain, CI permissions, agent tool and MCP config, and more) and reports only findings backed by file:line, an exploit path, and evidence. Ends with block, fix-before-merge, or ok.
reflect
Mine this session's transcript for lessons that will still hold in six months and turn each into an edit to a skill the session used, applied only after the user approves. Use at the end of a session, or on "reflect", "what should we learn from this", "capture lessons".
recall
Rebuild where recent work stands from the agent's past chat transcripts and the team's shared record (PRs, tickets, chat, errors), and return a short status brief ending in the next step. Use for "what was I doing on X", "catch me up on my work", "where did I leave off".
principle-type-system-discipline
Use when designing types, reviewing signatures, or writing statically typed code. Have the compiler refuse impossible states, confused primitives, and unhandled variants, and parse outside data where it enters.
principle-treat-input-as-untrusted
暂无简介
principle-test-behavior-not-implementation
Use when writing or changing a test, or deciding whether one should stay. Check what callers can see through the interface they call, so the test breaks when behavior breaks and survives changes to internals alone.
principle-subtract-before-you-add
Use when planning the order of an addition, refactor, or rewrite. Clear out dead code and redundancy before building, so the system ends up simpler and no less capable, with a surface the same size or smaller.
principle-sequence-verifiable-units
Apply to bulk sweeps, migrations, repeated near-identical edits, and stacks of commits or PRs. Break the job into slices, each closed by a check that passes, and order commits so that reading the history shows a reviewer the change is correct.
principle-separate-before-serializing-shared-state
Apply when parallel agents, workers, or processes might write the same key, file, state object, or branch. Start by giving each writer its own target, and add locking only where the design truly requires one shared target.
principle-redesign-from-first-principles
Use when a new requirement has to fit into an existing design. Rework the design as though the requirement had been there from the beginning, and carry it into every type, doc, and example, instead of attaching it at the side.
principle-prove-it-works
Use at the end of every task, before you say it succeeded. Check the actual output yourself, for example by exercising the feature, reading back what got stored, or opening the diff. A proxy signal, a subagent's self-report, or a successful compile does not count.
principle-outcome-oriented-execution
Use during a planned rewrite or migration with declared phases. Aim for a correct, fully checked final state rather than spending effort keeping each intermediate step working with compatibility code you will discard.
principle-never-block-on-the-human
Use when you are about to ask the user whether to do something that can be undone. Decide, continue, and show the result so it can be corrected later; pause for confirmation only on irreversible actions or product direction.
principle-model-the-domain
Use when writing stateful logic, branch-heavy code, or the same shape assumption repeated across files. Capture domain rules with a state machine, typed model, or lookup table so invalid states cannot be built.
principle-minimize-reader-load
Use when shaping or reviewing code that is hard to follow, deciding whether new indirection or state is worth it, or writing output for people. Reduce the indirections and hidden mutable state a reader has to track.