GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills，按职业与使用场景整理，复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoft
openclaw
@openclaw
OpenAI
@openai
The Apache Software Foundation
@apache
GitHub
@github
Anthropic
@anthropics
AutoGPT
@Significant-Gravitas
Garry Tan
@garrytan全部 Skills 196628
goquery-parsing
Builds robust, maintainable Go HTML parsers with goquery — stable CSS selectors, typed structs, and parsers that survive minor markup changes. TRIGGER — load BEFORE writing the parser, not after: raw HTML or a .html file is in context and structured data is wanted out of it; goquery is imported or `Find(`/`Attr(`/`Each(` is being written; the prompt names goquery, scraper, parser, extract, scrape, crawl, or selector alongside HTML or a page. Trigger on plain requests — "pull the prices off this page", "get these fields out of this markup", "turn this listing into structs" — the user will not name goquery; the HTML plus a Go repo is the trigger. SKIP when the extraction target is JSON or an API response rather than markup, or when the project is not Go.
go-testing
How Go tests are written in these repos: assertions, tables, test doubles, helpers, async waits, golden files, fuzzing, benchmarks, and integration tests against a real Postgres via the bundled pgtest helper (one shared testcontainer, a fresh database per test). TRIGGER — load BEFORE writing, editing or reviewing any *_test.go file, testdata/ golden file, fuzz target or benchmark, or when the task says go test, test helper, fake, mock, stub, table test, testcontainers, TestMain, test database, flaky test or coverage in a Go repo. Plain requests count: "write the tests", "add a test for this", "fix the failing test", or a feature task whose last step is testing it. Load alongside go-idiomatic and tdd, not instead of them. SKIP when no Go test code is written or judged.
go-idiomatic
Go engineering standards for this repo — package layout, error handling, logging, testing, concurrency and design patterns. TRIGGER — load BEFORE writing or editing Go, not after: any .go, go.mod, go.sum or go.work file is touched, Go or Golang is named, or the working directory contains go.mod and the task is implementation, refactor, review or test-writing. Plain feature requests in a Go repo ("add an endpoint", "extract a helper", "write a test for this") count; the user will not say "idiomatic". Load it even when another skill (tdd, simplify) is active. SKIP only when no Go file is involved and Go is not named.
frontend-best-practices
Frontend engineering standards — component architecture, state, async, forms, accessibility, performance and TypeScript discipline. Detects the project's framework and loads only the matching guidance. TRIGGER — load BEFORE writing or editing frontend code, not after: any .tsx, .jsx, .vue, .svelte, or component/hook file is being created or edited; the prompt names a component, hook, prop, state, form, modal, route, page, React, Next, Solid, SolidStart, solid-js, signal, useState, useEffect, createSignal, createStore, createResource, createAsync, <For>, <Show>, store, context, a11y, or web vitals. Trigger on plain feature requests in a frontend repo — "add a button", "wire up this form", "make this load faster", "fix this rerender" — the user will not say "best practices"; the component file is the trigger. Load it even when another skill (tdd, impeccable, simplify) is already active. SKIP only for backend-only work with no UI file touched.
compare-tools
Use whenever the user needs to *choose* a technology, library or tool for this project: "which library should I use", "help me pick a tool", "what's the best X for this", "compare these technologies", "should I use X or Y", "what are my options for Z". Trigger even when it isn't phrased as a comparison. Explores the codebase, aligns on priorities (community support, maintenance, lock-in, extensibility), researches the market, and writes a report to ./ideas/ with every viable option, doc links, a comparison table, and a ranked list scored out of 100 against the user's own priorities.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
code-review
Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". Reviews changes since a fixed point (commit, branch, tag, or merge-base) along two parallel axes — Standards (does this follow the repo's documented coding standards?) and Contract (does this match the ticket and the feature's frozen contract?) — reported side by side. Also defines the Journey axis, which /fleet reconcile applies to a completed slice. For whole-system design assessment rather than a diff, use architecture-review.
clean-comments
Remove comments that fail ~/.claude/rules/comments.md from source files. Use when user wants to clean comments, remove redundant comments, strip obvious comments, or run /clean-comments on staged files before committing.
architecture-review
Use when the user wants an architecture review, a design health check, a staff-level read on architectural risk, or an assessment of coupling and cohesion: "review my architecture", "is this codebase well-architected", "architecture health check", "where's the design risk", "design review before we scale". Maps the system, detects the stack, fans out seven parallel reviewers (one per quality dimension — boundaries, coupling, data flow, failure modes, information hiding), and synthesises a verdict plus a prioritised roadmap. Diagnoses only — does not refactor. For a diff or PR, use code-review; to actually apply refactors, use improve-codebase-architecture.
app-performance-testing
Investigate why this app's HTTP API endpoints are slow and how to make them faster. Discovers the endpoints, measures their response times, works out which layer the time goes to (network, middleware, handler code, database, external calls, cache, serialization) using Grafana metrics, traces, logs and profiles plus the code, and produces a ranked list of fixes. Use whenever the user asks why the app or an endpoint is slow, wants the API to feel snappier, mentions latency, p95, slow queries, N+1, or wants a performance check or audit of the backend, even if they don't say "performance testing".
code-review
Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". Reviews changes since a fixed point (commit, branch, tag, or merge-base) along two parallel axes — Standards (does this follow the repo's documented coding standards?) and Contract (does this match the ticket and the feature's frozen contract?) — reported side by side. Also defines the Journey axis, which /fleet reconcile applies to a completed slice. For whole-system design assessment rather than a diff, use architecture-review.
diagram-design
畫結構圖（架構、流程、時序、狀態機、泳道、時間軸、分層、樹、依賴、部署、ER、甘特等 39 型）的完整規範庫：選型、語意 pattern、連線幾何、複雜度預算、每型範例 HTML、動畫變體。html-visualizer 畫圖時的按需深讀來源。
ckm-ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm-design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.
ckm-design-system
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
ckm-banner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
fsdp-style-guide
Mandatory for all UI/UX design, implementation, review, audit, or visual regression tasks. Always use for any work that affects user-facing appearance, behavior, accessibility, branding, layout, navigation, forms, dialogs, alerts, tables, or visual design.
agency-priorities
Provide self-contained USDA strategic goals and Forest Service priorities for agency briefings, proposals, and work-plan alignment. Use when explaining agency direction or evaluating how a project contributes to USDA and Forest Service priorities.