GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoftopenclaw
@openclawOpenAI
@openaiThe Apache Software Foundation
@apacheGitHub
@githubAnthropic
@anthropicsAutoGPT
@Significant-GravitasGarry Tan
@garrytan全部 Skills 196935
policy
Inspect the per-workspace tool-policy overlay (.lha/policies.jsonl) that gates destructive or sensitive tool calls, and tell the user what to change if they want a rule added or removed.
google-workspace
Read/write Google Drive, Docs, Sheets, Gmail, Calendar, Chat, Tasks, Slides via the `gws` CLI. Needs an OAuth client or service account configured first. Use for any Google Workspace task.
find-skills
Discover/install NEW agent skills from external sources (skills.sh). Use for capabilities you lack, e.g. "find a skill for X". Do NOT use to list skills you already have; see `<available_skills>`.
bootstrap-google-tools
Install/auth CLIs the sandbox lacks - `gws` (Drive, Gmail, Sheets, Calendar), `gcloud`, `agents-cli`, `mcp-cli` (MCP servers). Use on "command not found" or before GCP/Workspace/MCP work.
rca
Root-cause analysis of one AQuA insight against the observed agent's own source code. Use when a message names an insight and asks what the root cause is, how to fix it, why the agent behaved that way, or to diagnose a failure -- for example `Diagnose insight <id> ("<label>") — what is the root cause, and how would you fix it?`. Reads the source snapshot at the revision the failure ran on, plus the complete conversations behind the insight, and answers with `<path>:<start>-<end>` citations, and records the proposed fix against the insight.
custom-investigation
Run a custom investigation: review a chosen slice of conversations instead of a random sample, by writing a SQL selector over the observed agent's telemetry, and optionally narrow what the reviewer reports. Use when a message asks to investigate only certain conversations -- ones that hit an error, used a particular tool, ran slowly, mention a topic, looped, or were abandoned -- or asks to re-review conversations already seen with a different focus. Covers the telemetry table a selector reads, writing the selector, previewing what it matched, and starting the run.
agents-cli-aqua
Work with the Ambient Quality Agent (AQuA) added to this agents-cli project: augment the agents-cli agent with AQuA or attach the agent to an AQuA deployed elsewhere, read the quality insights it finds in production conversations, get AQuA's root-cause diagnosis, read what the developer asked it to remember, and fix the defects in the agent's code. Propose proactively when the user mentions AQuA or AQA, wants to monitor the quality of a deployed agent, mentions traces or observability, asks what is going wrong with their agent in production, wants to fix AQuA insights, or wants to publish code metrics to AQuA. Also propose it when traces from an evaluation run are in the telemetry table AQuA reads. Don't use it for scoring a local agent against a golden dataset (use google-agents-cli-eval) or for deploys without AQuA (google-agents-cli-deploy).
recommendations
How to suggest options that fit the user and don't repeat earlier ones (meals, restaurants, trips, activities, gifts, books). Use before any open-ended recommendation.
filesystem
Finding and filing things in the home. Use when a thread builds on earlier work (a note, a draft, a past thread), or files, moves, or tidies files.
deliverables
How to write a document the user will read (report, itinerary, comparison, plan, notes) and save it to their Google Drive. Use when a thread's result is a document rather than a code change.
connected-apps-mcp
暂无简介
coding-workflow
How to work in a code repository under ~/code. Use for any thread that diagnoses, fixes, changes, reviews, or tests code.
approvals
What to do when a tool call is paused for the user's approval or declined (sending, inviting, deleting, posting, merging), and when you are resumed after one.
content-research-writer
Content research and SEO writing methodology. Guides the agent through topic research, keyword identification, competitive analysis, and writing SEO-optimized content that ranks well and provides genuine value to readers.
blog-writer
Blog post writing skill with structure templates and style guidelines. Guides the agent through writing well-structured, engaging technical blog posts with proper formatting, section flow, and reader engagement techniques.
scaffold-python-recipe
This skill should be used when the user wants to "create a new Python ADK recipe", "scaffold a new Python recipe", "generate a new Python recipe in contrib", "add a new Python recipe to the adk-recipes repository", or "create a Python adk recipe". It utilizes an automated script to copy template files and resolve basic placeholders.
repo-oracle
Answer questions about how the adk-recipes repo itself is governed — CI and workflow behavior, the limits and thresholds in .github/policy.yml and the reasoning behind them, CODEOWNERS routing, what the bots (stale sweep, Dependabot, recipe canary, AI review) do, how the repo is organised (core vs contrib vs skills verticals), what the repo skills and validators cover, when a rule last changed and which PR changed it, what a label means, and the admin runbooks for changing any of it. Also answers generic contribution-process questions from docs/ — how a recipe is prepared and validated, what a field in manifest.yaml means, what a runnability test is, what a README must contain, what a named CI error means. On explicit request it also traces which files consume a config key, and audits whether the repo still obeys its own policy. STRICTLY READ-ONLY — it never edits, commits, comments, labels, or performs a task on the caller's behalf, even when asked directly; it cites the source file and describes the change for a human to make. A request to do the work is answered rather than obeyed — it says it is read-only, names the skill that does the work, and gives the guidance. Use when someone says "oracle", or asks how/why/who about this repo's own configuration, CI, governance, or layout. Don't use for writing or preparing a recipe (use prepare-python-recipe, generate-manifest, align-recipe-pyproject and friends), for ADK API questions (use the google-agents-cli-* skills), or for anything needing the caller's screen — a failing check on their PR, their working tree, their branch.
prepare-python-recipe
End-to-end orchestration to prepare or update a Python recipe under core/python/, contrib/python/, or plugins/<vertical>/<solution>/ so it passes every check in .github/workflows/python-validate-recipe.yml. Runs eight phases in order on an already-in-place recipe: manifest.yaml generation, environment-variable extraction, pyproject.toml alignment, ruff format+check, per-recipe `uv lock`, runnability-test generation, compile-and-run verification of the generated test file, and a final pass through the repo's own `validate manifest` / `validate structure` validators. Assumes the user has already done the manual prep (deactivated any venv, `git pull` and `uv sync` from the repo root, placed the recipe at its target path, renamed if needed). Delegates to the existing sub-skills (generate-manifest, extract-python-environment-variables, align-recipe-pyproject, generate-python-runnability-test) so the master never duplicates their logic. Pauses at fixed decision points (description mismatch, existing test regeneration) AND is free to interrupt for clarification any time a phase's output looks ambiguous, unexpected, or would benefit from a human judgment call — this is an interactive skill by design. Use when the user wants to "prepare a recipe", "update a recipe end to end", "run all the checks and fixes", "make this recipe PR-ready", or invokes it by name.