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
team-a
Diamond-a. Test fixture; describes itself for parity checks across both runtimes.
database-modeling
Data modeling — ER diagrams, normalization, denormalization trade-offs, relationship patterns, and schema evolution. Use when designing a new schema, critiquing an existing data model, choosing between normalized and denormalized designs, or modeling complex relationships like polymorphism, hierarchy, or temporal data.
team-e
DeepChain-e. Test fixture; describes itself for parity checks across both runtimes.
database-migration
Schema migration workflows — zero-downtime expand/contract, batched backfills, and rollback strategies. Use when planning a schema migration, reviewing migration scripts, troubleshooting a slow or failed migration, or rolling back a deployed change.
team-d
DeepChain-d. Test fixture; describes itself for parity checks across both runtimes.
team-c
DeepChain-c. Test fixture; describes itself for parity checks across both runtimes.
team-b
DeepChain-b. Test fixture; describes itself for parity checks across both runtimes.
concurrency-patterns
Concurrency and parallelism patterns — async/await, threads, actors, channels, deadlock prevention. Use when choosing a concurrency model, designing concurrent or parallel pipelines, debugging deadlocks or race conditions, or reasoning about shared state and backpressure.
team-a
DeepChain-a. Test fixture; describes itself for parity checks across both runtimes.
code-review
Structured code review with a checklist covering correctness, clarity, tests, security, performance, and style. Use when reviewing a PR, diff, or set of code changes before merging — including phrases like "review this", "check my changes", or "is this ready to merge".
team-c
Cycle3-C. Test fixture; describes itself for parity checks across both runtimes.
team-b
Cycle3-B. Test fixture; describes itself for parity checks across both runtimes.
code-generation
Code generation patterns — template engines, AST manipulation, scaffolding, build-step generation. Use when building or extending a code generator, choosing a template engine, deciding whether to generate code or write an abstraction, adding codegen as a build step, or implementing macro/AST transformations.
team-a
Cycle3-A. Test fixture; describes itself for parity checks across both runtimes.
changelog
Generates and maintains CHANGELOG.md files following Keep a Changelog conventions — from git history, commit messages, or a description of changes. Use when asked to write a changelog, update release notes, or document what changed in a version.
team-b
Cycle2-B. Test fixture; describes itself for parity checks across both runtimes.
caching-strategies
Caching patterns — cache-aside, write-through, TTL strategies, invalidation, HTTP caching. Use when adding caching to reduce latency or DB load, choosing between caching patterns, configuring HTTP cache headers, debugging stale data or stampedes, or designing an invalidation strategy.
team-a
Cycle2-A. Test fixture; describes itself for parity checks across both runtimes.