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
golang-continuous-integration
Provides CI/CD pipeline configuration using GitHub Actions for Golang projects. Covers testing, linting, SAST, security scanning, code coverage, Dependabot, Renovate, GoReleaser, code review automation, and release pipelines. Use this whenever setting up CI for a Go project, configuring workflows, adding linters or security scanners, setting up Dependabot or Renovate, automating releases, or improving an existing CI pipeline. Also use when the user wants to add quality gates to their Go project.
golang-context
Idiomatic context.Context usage in Golang — creation, propagation, cancellation, timeouts, deadlines, context values, and cross-service tracing. Apply when working with context.Context in any Go code.
golang-concurrency
Golang concurrency patterns. Use when writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Also triggers when you detect goroutine leaks, race conditions, channel ownership issues, or need to choose between channels and mutexes.
golang-code-style
Golang code style, formatting and conventions. Use when writing code, reviewing style, configuring linters, writing comments, or establishing project standards.
golang-cli
Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses cobra, viper, or urfave/cli.
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while golang-performance provides the optimization patterns.
go-trait-fit
Match a Go role's `dev::go-*` traits to what the module actually requires, read from `go.mod`. Use when picking or customizing a role in a repository whose root carries a `go.mod`.
drift-detection
Compare implementation diff against task acceptance criteria and ADRs to surface drift. Use when a task is in review state before transitioning to done, when integrating a worktree spanning two or more sessions, during a pre-merge audit when the diff exceeds the task description, or after a sub-agent reports completion.
domain-reviewer
Coordinate deep-dive reviews via specialized sub-agents as critics. Use for deep review of a specific module or domain (not general code review), when multiple specialized perspectives are needed (e.g. security plus performance plus correctness), or for pre-release review of critical system components.
distributed-systems-checklist
Audit distributed services against the 8 fallacies and the CAP trade-off. Use during design review for any service that crosses a network boundary, during incident triage when root cause is unclear and a network or IPC layer is involved, or when drafting an architectural ADR for new distributed components.
design-system
File an accepted visual direction into the project's one system file, and let a page override only itself. Use when a direction has been accepted, when the project already has a system file, or when the next screen would otherwise invent a second palette.
design-direction
Show a numbered prototype and hold it until the supervisor picks. Use when starting or redesigning a screen, and when a first pass would look the same on any similar brief.
composition-verification
Prove a role/trait/rule/skill edit reached the composed prompt. Use after editing any library component, before reporting a composition change landed, and when a rule or skill looks absent from a role that should carry it.
comment-length-lint
PostToolUse hook — flags oversized comment blocks and docstrings on every `.py` you Edit/Write and forwards them non-blockingly; fail-open, no manual invocation.
clean-architecture-guide
Audit a codebase for DDD/Hexagonal/Ports-and-Adapters compliance. Use when reviewing a module that owns business logic, in a pre-merge audit when a PR touches domain types, repositories, or transport layers, when drafting an ADR for a new bounded context, or triaging a codebase drifting toward a Big Ball of Mud.
claim-evidence-check
Claims table for a text — every checkable statement gets a source you saw or an honest mark, and every link is checked by script. Use when a draft states facts, numbers, dates, names, versions, tool behaviour or quotes; before a text is handed back or published; or when asked whether a text is accurate.
bash-mastery
Shell scripting, Makefile conventions, and modern CLI tooling. Use when writing or reviewing shell scripts, creating or modifying Makefiles, or choosing CLI tools for automation tasks.
backup-recovery
3-2-1 backup strategy with verified restore procedures. Use when setting up or reviewing backup infrastructure, before risky data migrations or destructive operations, or after adding new persistent storage such as a database or volume.