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
chat-to-approach
Converts a pasted AI conversation summary or transcript into a canonical alignment document at ./docs/approach.md — the single source of truth for what we are building and why. Grills only on ambiguities, conflicts and deltas, never on settled decisions. The doc is portfolio-level: it holds many features at once, which /to-roadmap prioritises into a Now/Next/Later board before each feature runs the per-feature spine on its own. For a single already-chosen feature, use /to-prd instead.
capture-idea
Capture an idea you just had — shape it into one concrete line, then append it to ## Accepted ideas in ./ideas/CONTEXT.md. Use for "capture this idea", "add that to the roadmap", "note this down before I forget".
artifact-scan
Use whenever the user asks "which skill should I use?", "where are we in the workflow?", "what should I run next?", "what product docs already exist?", "do we have a roadmap/PRD/plan yet?", or "what's left before I start coding?". Front door to the product workflow suite: detects the ideate report, approach doc, roadmap, PRDs, plans and tickets, then names the one skill to run next based on what exists rather than a fixed order. Routes between *skills* — for "what feature should I build next?" use ideate. Also usable as a preflight routine from other product skills.
to-vault
File what the user learnt or decided into their Obsidian vault as atomic Notes, one idea each, linked into MOCs and logged. Use when the user types /to-vault, or says "save this to my vault", "put this in obsidian", "add this to my notes", "file this decision", "record this decision in the vault", "keep this", "keep that answer", "save that answer", or asks to keep takeaways from the session in their second brain. Also offer it right after record-decision writes an ADR. Also takes a Notion page link as the capture. Works from any repo. Not for writing ADRs (record-decision), Claude's own memory, or ingesting a source into wiki/ (use /ingest).
review-pr
Read PR review comments, monitor CI with gh pr checks --watch, implement fixes, and push updates.
review-pr-2x
Run review-pr twice and monitor PR checks with gh pr checks --watch.
review-fix
全方位進行專案程式碼審查，產生詳細且清楚的審查報告，並根據報告自動建立 OpenSpec change 的所有提案文件，用來規劃並修復所有發現的問題。另支援供 review-pr 等流程呼叫的輕量驗證模式。
teach
Teach the user a new skill or concept, within this workspace.
triage-issue
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
source-synthesis
Deep synthesis of a curated reading list — blog posts, tutorials, docs, articles — tailored to a specific use case or build goal. Use whenever the user provides URLs (public links to educational content) and wants a thorough, opinionated synthesis rather than a raw summary. Trigger on phrases like "synthesise these sources", "give me a lit review of", "I want to read up on X, here are some links", "help me digest these articles", "summarise these tutorials for my use case", "I'm about to build X, here's my reading list", or whenever the user pastes a list of URLs alongside a goal or project description. Also trigger proactively when the user provides multiple URLs and a description of something they're trying to learn or build — even if they don't say "synthesise".
prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
handoff
Compact the current conversation into a handoff document that another agent picks up in a fresh context window — including an agent targeting a different repo. Use when the user says "hand off", "write a handoff", "pass this to another agent", "continue in another repo", or wants to preserve context before switching sessions/repos.
refactor-django
任意 Django 專案的波浪式重構工作流程。當使用者想要讓專案更好維護、程式碼更具可讀性、更容易測試、更 clean、提升測試覆蓋率、從 Fat View 抽取 Service 層、拆解 Fat Model、解耦 Django signals、修復技術債、整備 type hints / mypy、設定 pre-commit 工具鏈、或需要一套安全且可追蹤的重構計畫時使用。觸發詞：refactor、重構、service 層抽取、測試覆蓋率提升、fat view、fat model、技術債清理、clean code、service layer、安全網測試、Django 重構、type hints。
grilling
Interrogates a plan, design or decision one question at a time until nothing is silently assumed. Use when the user wants their thinking stress-tested rather than executed: "grill me", "grill me on this", "poke holes in this", "stress-test this plan", "challenge this design", "what am I missing here", "argue against this", "pressure-test this decision", or "interview me about this before we build". Trigger when the user presents a plan and asks for pushback instead of implementation, even without the word "grill". For a session that also checks the plan against CONTEXT.md and existing ADRs, use grill-me-with-docs instead.
grill-me
A relentless interview to sharpen a plan or design.
grill-me-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
flow-friction-audit
Drives a live web flow through a real browser, turns the run into evidence-backed friction findings, then routes them into the impeccable skill for critique and redesign. Use whenever the user wants to know where a real user gets stuck, confused or slowed down in a running flow — "audit the signup flow", "where's the friction in checkout", "walk through onboarding and tell me what's clunky", "usability audit of the live app", "why do people drop off here". Trigger on "usability", "UX audit", "friction", "drop-off" or "walk the flow" without this skill being named, and when the user only supplies a URL and asks what's wrong with the experience. Trigger before any URL or credentials exist — settling the goal, flow and environment is this skill's own first step, so ask for what's missing from inside the skill. Also use to run the design half alone from an agreed problems doc.
feedback
Turns the user's unstructured feedback about how a product or system behaves into verified, agent-ready GitHub issues. Splits a complaint into points, checks each against the code and recorded intent (ADRs, CONTEXT.md, git history), plays back what it found until the user agrees, then files one ticket per agreed finding under a shared label for /implement or /fleet dispatch. Use when the user says "/feedback", "I don't like how X works", "this isn't usable because…", "X feels wrong", "this behaviour is annoying", "push back on how Y behaves", or otherwise complains about the repo's behaviour or UX without a concrete bug report or spec. Also takes a jam.dev screen recording with the points as bullets. Not for feedback on a skill (use skill-feedback-collector), a single well-understood bug (triage-issue) or a ready-to-file follow-up (file-issue).