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
prompt-authoring
Choose the mechanism before the wording, then write prose that holds. Use before wording or rewording any rule, injection or skill body, and when a written instruction has failed to change behaviour.
library-editing
Put a component where this project reads it, and wire it to a role. Use before adding or removing a trait, rule or skill, and when a component you wrote is not reaching the agent.
library-change-hypothesis-protocol
After execute-stage commits land (diff finalized) and BEFORE the task transitions to done, file a companion HYP with an explicit verification_protocol — or record an explicit "no behavior change" note for refactors at plan-stage. NEVER file the HYP at plan-stage (precommitment anti-pattern).
composition-verification
Prove a role/trait/rule/skill edit reached the composed prompt. Use after editing any library component, before reporting a composition change landed, and when a rule or skill looks absent from a role that should carry it.
comment-length-lint
PostToolUse hook — flags oversized comment blocks and docstrings on every `.py` you Edit/Write and forwards them non-blockingly; fail-open, no manual invocation.
bash-mastery
Shell scripting, Makefile conventions, and modern CLI tooling. Use when writing or reviewing shell scripts, creating or modifying Makefiles, or choosing CLI tools for automation tasks.
agent-cli-guidelines
Design a CLI, gate or hook whose reader is another agent. Use when building or changing one, and when a tool of yours was ignored, misread, or worked around.
worktree-isolation
Isolated development using git worktrees so the main branch stays clean. Use when starting any non-trivial task (execute state), doing parallel work on multiple tasks, making risky changes you might want to discard, or delegating to a sub-agent (automatic via ai-hats agent --isolation).
tool-call-hygiene
Choose between Bash and dedicated Claude Code tools (Grep/Glob/Read/Edit) and edit files efficiently. Triggers on intent to grep/find/cat/sed/rg, multiple sequential reads, session-start context restore, codebase discovery, or multiple sequential Edits to one file.
task-summary
Focused post-task summary covering architectural decisions, decision forks, pitfalls, and plan deviations. Use at `document → review`, before handing the card to the reviewer, on a task that failed, or when the supervisor asks what happened with a task.
task-slicing
Wire a work breakdown into the tracker — depends_on edges, frontier, expand–contract for wide refactors. Use when filling plan.md's Steps section (routed from plan-gate), decomposing an epic into child tasks, or carving a mid-execute remainder into successor tasks.
self-retrospective
Turn what went wrong into a systemic fix. Use when the supervisor asks for a retro, after a failed task (mandatory), after a task with backtracks, or when wrapping up a multi-task session. Not the automated audit that runs after a session closes.
scope-guard
Enforce user-defined task boundaries to prevent scope creep and over-implementation. Use after receiving a task with explicit constraints ("only X", "don't do Y", "focus on Z"), before starting each new sub-step during execution, or when tempted to add helpful work not explicitly requested.
requirements-interview
The Requirements stage of the plan-gate — fills plan.md's Requirements section via structured Q&A where the agent proposes a cited best-guess per question and the supervisor reviews. Reached through plan-gate (which owns the brainstorm→plan entry), not as an independent trigger.
request-supervisor
Decision protocol for when to act autonomously vs escalate to supervisor. Use before any communication with the user or parent-agent, or whenever uncertain whether to act autonomously or escalate.
rack-advanced
Advanced rack beyond day-to-day lifecycle: authoring a new custom backlog, and cross-project work. Use when defining a backlog beyond the built-in tasks/HYP/PROP, or registering and searching backlogs across several projects.
predictive-accounting
For shrink/refactor/optimize/cleanup tasks — present baseline + predicted delta + dependency cost BEFORE implementation, not after
positive-control
Distinguish a failed subject from a broken verification path. Use before relying on search or grep output, logs, composed prompts, stored artifacts, or before/after measurements to support a verdict.