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
java-patterns
Modern Java 17+ — records, sealed types, pattern matching, streams, Spring Boot. Use when writing or reviewing Java 17+ code, modernizing legacy Java, or working in Spring Boot services.
prompt-fix-d
Fixture skill D — depends on prompt-fix-c, sits fourth in topological order; trivial body for parity tests.
prompt-fix-c
Fixture skill C — depends on prompt-fix-b, sits third in topological order; trivial body for parity tests.
integration-testing
Integration and E2E testing patterns — testcontainers, fixtures, API mocking, snapshots, and CI isolation. Use when writing integration tests against databases, APIs, or queues; setting up testcontainers or fixture infrastructure; mocking external APIs; or debugging flaky tests.
prompt-fix-b
Fixture skill B — depends on prompt-fix-a, sits second in topological order; trivial body for parity tests.
grpc-protobuf
Protobuf schema design and gRPC service patterns — streaming, error handling, backward compatibility. Use when designing .proto files, implementing gRPC services or clients, choosing a streaming pattern, handling gRPC errors, or evolving a schema without breaking consumers.
prompt-fix-a
Leaf fixture skill A — no dependencies, sits at the bottom of the topological order for prompt-emitter parity tests; trivial body.
graphql-patterns
GraphQL schema design, resolver patterns, DataLoader, pagination, federation, and schema evolution. Use when designing a GraphQL schema, implementing resolvers, diagnosing N+1 problems, adding pagination, setting up federation, or evolving a schema without breaking clients.
app-parsed-optional
Parser fixture exercising every optional frontmatter field (license, compatibility, metadata, allowed-tools, dependencies) so the canonical-JSON snapshot pins their representation across runtimes.
go-conventions
Go idioms — error wrapping, small interfaces, goroutine lifecycle, table-driven tests. Use when writing or reviewing Go code, designing package layouts, or working through concurrency, error handling, and testing decisions.
org-parsed-minimal
Minimal parsed fixture exercising only the three required frontmatter fields, used to freeze parser-output snapshots for cross-runtime drift detection.
git-workflow
Git workflow conventions — branch naming, conventional commits, PR descriptions, and merge strategy. Use when deciding on a branch name, writing a commit message or PR description, or choosing a merge strategy.
low-score-vague
A useful tool that helps with stuff related to skills and is generally helpful for many things.
passing-clean
Naming fixture that satisfies every E-rule in the naming table (name matches dir, single-hyphen-separated lowercase, valid tier, description in-bounds). Used as the "no issues" snapshot.
org-mismatched-name
Naming fixture whose frontmatter name does not match its parent directory (dir is `dir-name-mismatch`, name is `org-mismatched-name`). Drives E005_NAME_DIRECTORY_MISMATCH.
flutter-development
Flutter and Dart development — widget architecture, state management, navigation, and cross-platform layout. Use when building Flutter apps, choosing a state-management approach, designing responsive layouts, or reviewing widget code.
org-fixture-missing-name
A fixture deliberately missing the `name:` field so the validator must emit E000_NAME_MISSING.
team-c
Linear-C. Test fixture; describes itself for parity checks across both runtimes.