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
triage
Move incoming issues (and optionally external PRs) through triage states to agent-ready briefs.
to-tickets
Split a spec into tracer-bullet sub-issues with blocking links.
to-spec
Turn the current conversation into a spec issue, without re-interviewing.
to-questionnaire
Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.
teach
Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.
tdd
Test-driven development with a red-green loop, one vertical slice at a time, plus what makes a test worth keeping. Use when building a feature or fixing a bug test-first, when the user mentions TDD or red-green-refactor, when writing integration tests, and when another skill implements a change at an agreed seam.
svg-logo-designer
Generate SVG logos with multiple concepts, layouts, and color variations.
standup
Daily standup from git history and GitHub activity: what changed since yesterday, what's in flight, what's blocked.
skill-writer
Writes and reviews shared agent skills plus Claude Code Markdown and Codex TOML subagents for this plugin and bootstrapped projects. Covers choosing how prescriptive to be, the house writing style, whether a skill is user- or model-invoked and how skills call each other, writing the description field that controls when a skill fires, splitting content across reference files, the allowed-tools vs tools frontmatter distinction, and harness-kit's own conventions (shared scripts, dual plugin registration and host-specific script paths). Use when creating a new skill or agent, editing an existing one, writing a pointer line in AGENTS.md or CLAUDE.md, or deciding whether something should be a skill, an agent, a script, or nothing at all.
shortcut-ledger
Collects every `shortcut:` comment in the codebase into a ledger of deliberate simplifications, each with its ceiling and the trigger for revisiting it, and flags the ones with no trigger. Use when grooming the backlog, when the user asks what shortcuts or deferred work the code carries, and before planning work in an area with marked shortcuts.
session-retro
Capture a work session as a structured retro doc in docs/sessions/
review-pr
Reviews a pull request with two code-reviewer passes, standards and spec (on your own PR, as the gate before merge: fix the findings and record them), or works through unresolved review feedback on an existing PR: fix, commit, push, and reply in thread. Use when the user asks to review a PR or address review comments, and whenever the open-pr skill reaches its agent review or its outside reviews, or finds an open PR already exists.
research
Investigates a question against primary sources (official docs, source code, specs, first-party APIs) and writes the findings, with a citation for every claim, to a Markdown file. Use when the user wants a topic researched or facts gathered from documentation, when a decision waits on facts from outside the repo, and when reading legwork should run while other work continues.
rebase
Rebase the current feature branch onto a target branch (default origin/main) and resolve its conflicts.
prototype
Builds throwaway code that answers one design question: a single-file HTML demo to push a state model or business logic through hard cases, or several structurally different UI variants on one route, switchable in the browser. Use when the user wants to check whether logic or a state model feels right, explore what a screen should look like before committing, or settle a wayfinder prototype ticket with something runnable.
pr-comments
Reply in thread to every unresolved PR review comment, once the fixes are pushed.
pr-body
The shape of a pull request description: the smallest visual that makes the change clear, evidence that it works, and a merge-danger call (one-way or two-way door, plus blast radius). Use when writing or rewriting a PR description, and when opening or updating a pull request.
open-pr
Opens a pull request for the current feature branch and sees it through: validate, self-review, simplify, organize commits, push, create the PR, wait for CI, run an independent agent review and fix its findings, then answer any outside (Copilot or human) review. Use when implementation is complete and ready for review, when the user asks to open, raise, or submit a PR, and when the harness-issue skill hands off in PR mode. Also use when asked to work through or consolidate several dependency PRs.