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
brainstorm
Runs a brainstorming session on any topic: a problem to solve, an opportunity, names, an event, a strategy. Generates far more and better ideas than the user would alone by rotating creative techniques, then optionally narrows them. Use when the user says "brainstorm", "ideas for", "ways to solve", "help me think of", "I'm stuck on", "what are my options for", or "let's ideate", even without the word brainstorm. Not for stress-testing one existing plan (use grilling), deciding what to build next in the current repo (use ideate), or turning a chosen idea into a spec.
unslop
Strip AI tells from prose and put voice back in. TRIGGER: load BEFORE writing user-facing prose, not after. Covers a PR title or body, README, docs page, commit message, issue or ticket text, Slack or email message, article, or release note. Trigger on plain requests like "raise a PR", "write this up", "document this", "draft a message". The user will not say "unslop", the prose itself is the trigger. SKIP for code, config, tests, and log output.
adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /adhd; stays on until "stop adhd mode".
triage-reflections
Routes pending REFLECT-marker learnings from the reflect ledger to GitHub issues. Use when the user says "triage reflections", "/triage-reflections", "process my REFLECT markers", "what have I learned", or when the statusline shows reflect:N. Infers missing skill and scope, splits notes into explicit and unclear, plays unclear ones back for correction, merges duplicates into one item with every example, drops lessons already covered by a rule or lint config, routes by a three-way test the user can correct, files one issue per skill, and writes every decision back to the ledger with `reflect marker mark`.
subagent-creator
Designs a lean Claude Code subagent, or widens one on request. Use when the user wants to create, scope or audit a subagent or custom agent, or asks to give an existing one more tools, turns or access. Grills on whether it earns its place before writing anything. Not for writing skills.
skill-updater
Update an existing skill with new context, patterns, or improvements. Edits the skill at its source repo (not the installed copy) and opens a draft PR for the change. Use when user wants to update a skill, modify a skill, add a pattern to a skill, improve an existing skill, edit a SKILL.md, tweak skill instructions, change skill behaviour, or mentions "update skill", "edit skill", "change skill", "add to skill". Also use when invoked programmatically with a skill name, path, and improvement_suggestions[] payload from skill-feedback-collector, with a GitHub issue number, or when /implement hands over an issue whose changes are all under `skills/`. Do NOT use for creating new skills from scratch — use skill-creator for that.
skill-feedback-collector
Collect structured feedback on a skill session and convert it into improvement proposals, then file them as reflect-format issues or hand them to skill-updater. Use when a skill finishes and asks whether you want to log feedback, or when the user says "log feedback on the X skill", "record feedback on skill Y", "capture feedback for skill Z", "give feedback on the X skill", or "I want to leave feedback on skill X". Make sure to use this skill whenever feedback or impressions on a skill are mentioned — even if the user doesn't explicitly say "feedback".
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
skill-brief
Turns a rough idea for a new skill into a skill-creator-ready brief — the prep work a careful person does by hand before building: source prior art, decide what's worth lifting vs. what only half-fits, check the idea doesn't duplicate a skill you already have, and package the decisions. It does NOT write the final skill; it produces the brief skill-creator builds from. Use when the user says "skill-brief", "brief for a skill", "source and synthesise skills for X", "what's out there before I build a skill for X", "I have an idea for a skill, help me scope it", "capture this into a skill brief", or "turn this into a skill-creator prompt". Trigger proactively whenever someone is about to start a skill-creator session from a raw idea and hasn't sourced prior art yet — the sourcing pass is exactly what prevents building a duplicate.
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
review-skills
Audit all skills available in the current project context for conflicts, quality issues, and replicable patterns. Use when user wants to review skills, audit skills, check skill quality, find conflicting or overlapping skills, improve skill descriptions, check what skills are installed, or mentions "review-skills". Always use this skill when the user wants to understand the health or completeness of their skill setup.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
repo-skill-candidates
Audits one codebase for the recurring, multi-step patterns worth turning into repo-level Claude Code skills, and writes a short evidence-backed report to skill-candidates-report.md. Evidence comes only from the code (source, layout, tests, CI, scripts, docs, existing .claude setup), so it works on a new or inherited repo with no history. Triages every pattern to skill, CLAUDE.md line, linter config or script, and drops what existing skills already cover. Use when the user says "find skill candidates", "what in this repo should be a skill", "audit this repo for skill opportunities", "which patterns here are worth capturing as skills", or "repo-skill-candidates". Report only. Not for writing or drafting a skill (use skill-creator), reviewing code quality (use code-review or architecture-review), or suggesting skills from session history or the user's own habits (use reflect).
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.