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
character-passport
Cast an AI video before anything moves: for every character and hero prop, a passport (one paragraph, every visible detail, pasted word for word into every prompt), a turnaround sheet in the moodboard's look, six expressions written as cause + physical tells, a measured voice line (pace in words per minute, accent, one verbal habit), and for props the materials, wear and how they move and sound. Includes anti-slop design rules, a prompt builder that refuses paraphrased passports, code routes (three.js, VRM, SVG face rig) and tested reference sites. Use for "make a character", "consistent character", "character sheet", "turnaround", "character bible", "expression sheet", "voice for my character", "prop sheet", "same person in every shot", or characters that look generic, plastic or different from shot to shot. Not for category looks (varg-character-design), real actor photos in multi-scene ads (varg-consistent-characters) or the film's look (video-moodboard).
river-review
River Review のメインエントリポイント。 レビュー依頼の intent classification → 専門 skill 選択 → 実行 → finding verification → feedback classification → fixture / reference / suppression への還元までを束ねる improvement-loop orchestrator。
wrap-up-branch
Use when the user asks to finish a feature branch: missing regression tests, review fixes, docs, and the merge into dev or the given target.
using-development-skills
Use when the development loop is missing from your context, or when a skill names a Claude tool that Codex lacks.
update-deps
Use when the user asks to update Python dependencies or pre-commit hooks, keeping the project's pin and configuration style.
staff-review
Use when the user asks for a review of a branch, diff, repository, directory, or file, or when the development loop requires an independent review of finished work.
simplify-stuff
Use when the user asks to remove unnecessary content or simplify files while keeping useful behavior and project knowledge.
roast-my-code
Use when the user asks to roast code: a factual staff review told with aggressive humor; --fix applies selected CRITICAL and HIGH fixes.
rethink
Use when choosing or changing a design, yours or the user's; when the user asks to rethink an approach; or when the user dislikes your proposal.
resolve-merge
Use when a merge or rebase has conflicts, including plans and chronicles with colliding names.
refactor-loop
Autonomous /goal loop that refactors a project on every axis without changing its behavior. Start it only when the user names refactor-loop.
plugin-feedback
Use when the user asks to write development-skills feedback from observed work, or to assess a feedback report for useful simplifications.
phone-a-friend
Use when the user wants a second opinion on a plan or code change from the other CLI, Claude Code or Codex.
handoff
Use when the user asks to move the session to a new chat or runs /handoff.
explain-diff
Use when the user asks to explain, understand, or describe a code change: a branch, pull request, commit, diff, or patch, such as 'explain what branch X does' or 'what does this PR change', even when bro is also active or the diff is pasted inline. Also use it when the user did not understand a reply or a concept, or asks to explain it better or to give a real example; at the end of planned work, after its checks and review; and to write or update a pull request description.
evolve-loop
Autonomous /goal loop that rethinks a project's design and adds features and improvements that can change its behavior, each change recorded and proven. Start it only when the user names evolve-loop.
create-test
Use when you must define what done means for a task, design or write acceptance checks, build a regression gate for a refactor or behavior change, or check performance.
commit
Use when the user asks to commit the staged changes as a Conventional Commit.