[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69920A47BGEQZEMXWFNY6YM":3,"skill-same:01M69920A47BGEQZEMXWFNY6YM":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M69920A47BGEQZEMXWFNY6YM","adk-bot-review",null,"Reviews adk-bot pull requests by validating technical correctness against source code, checking PR states and formatting, and following Google's developer documentation style and ADK docs conventions. Triggers on \"review bot PR\", \"check bot changes\", or \"verify bot issue\".","google\u002Fadk-docs","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M6991WQ2WMQGACZVXDMMY88Q",1537,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fadk-bot-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,9,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"bot","review","adk","adk bot review","changes","developer documentation","correctness","reviews","states","style","triggers","check","technical","verify","pull","documentation style","code","pr","documentation","pull requests","docs","2026-11-10 10:12:30",false,"---\nname: adk-bot-review\ndescription: Reviews adk-bot pull requests by validating technical correctness against source code, checking PR states and formatting, and following Google's developer documentation style and ADK docs conventions. Triggers on \"review bot PR\", \"check bot changes\", or \"verify bot issue\".\n---\n\n# Review changes proposed by adk-bot (adk-bot-review)\n\nThis skill guides a rigorous review of adk-bot changes. It ensures documentation\nupdates are technically accurate, appropriately sized, and follow ADK docs\nconventions, based on Google's developer documentation style.\n\n## Step 1: Verify and research the proposed adk-bot change\n\n- Check that the PR title briefly describes the topic being updated, not only\n  the issue.\n- Confirm changes are made directly in the `.md` files and no \"do not merge\"\n  status tags were prematurely removed.\n- Check the PR's mergeable state and CI status. Note git conflicts and failing\n  checks as findings to resolve or to fix in the consolidating PR.\n- The input is one adk-bot-authored PR, or occasionally a few. From the PR,\n  trace back to the issue and the specific item it addresses. Identify the item\n  from the PR title (\"Update ADK doc according to issue #\u003CN> - \u003Citem>\") and\n  body. adk-bot often opens more than one PR for the same item. If multiple PRs\n  are provided, confirm they all address the same item and review them together\n  as one consolidation set. If they address different items, ask the user which\n  one to focus on before continuing.\n- Search closed issues and merged\u002Frejected PRs across the repository for similar\n  topics. Ensure the bot is not re-introducing changes, APIs, or stylistic\n  choices that human maintainers have previously debated and rejected.\n- Summarize the item's intended change and stated reasoning, and carry that\n  intent into the technical validation in the next steps.\n\n## Step 2: Assess update criteria and architecture\n\n- Prioritize smaller, surgical updates over comprehensive overhauls unless the\n  existing docs are entirely unclear.\n- Verify that the update provides a useful learning experience and is actionable\n  for a developer.\n- Ensure the content is placed appropriately within the ADK docs information\n  architecture.\n- Confirm the update length and prioritization are appropriate for the specific\n  code change (check if it is already covered by existing docs or API\n  references).\n\n## Step 3: Validate the change against source and intent\n\n- **Never assume an AI agent's code snippet is correct.**\n- Cross-reference all code examples against the\n  `https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python` repository.\n- Verify the information against relevant pull requests and actual ADK code in\n  the `https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python` repo.\n- Confirm the change actually implements what the linked issue and adk-bot PR\n  set out to do, and resolves the issue item it references.\n- Flag any part of the change that drifts from that stated intent, or any part\n  of the intent the change leaves unaddressed.\n\n## Step 4: Check quality and style\n\n### Headings\n\n- Maintain a logical h1, h2, h3 hierarchy without empty headings (stacking\n  headers).\n- Do not number headings (Use `## This heading`, not `## 1. This heading`).\n- Use imperative titles (e.g., \"Build agents\", not \"Building agents\").\n- Do not use command names in headings; call out the task to be done.\n\n### Language\n\n- Follow Google's developer documentation style\n  (https:\u002F\u002Fdevelopers.google.com\u002Fstyle) as the basis for conventions; consult it\n  for anything not covered here.\n- Use active voice phrasing (e.g., \"The system does X\", not \"X is done\").\n- Never use the word \"this\" without a noun object (e.g., \"This function is\n  used...\", not \"This is used...\").\n\n### Code snippets and formatting\n\n- **Enforce an 80-character line length limit** for general Markdown text\n  (excluding long URLs, unbreakable code blocks, or tables).\n- Check for rendering errors caused by spaces before backticks (```).\n- Use the `!!! warning\u002Ftip\u002Fnote` mkdocs-material admonition format for notes and\n  warnings instead of quote formats (`>`).\n- Do not use ALL CAPS except for code syntax; use bold or italics for emphasis.\n\n## Step 5: Report findings and decide the recommendation\n\nFirst, summarize the findings from the verification steps above, ordered\nblockers first, then required edits, then nits. Then choose one outcome below,\njustified by those findings:\n\n- **Close the bot PR(s).** (sometimes) The change is wrong, outdated, targets a\n  deprecated or unreleased API, or is already covered by live docs or a merged\n  PR. Record the reason and link the superseding doc or PR.\n- **Approve as-is** (rare). The bot PR(s) are correct, well-placed, and need no\n  edits.\n- **Edit in place, then approve** (sometimes). The existing branch is usable but\n  needs conflict resolution, corrections, consolidation, copyedits, or\n  relocation.\n- **Open a new consolidating PR** (most common). Rework the change across the\n  1-3 bot PRs into one PR that fixes code errors and hallucinations, edits for\n  quality, and places the content in the correct file. Then close the superseded\n  bot PR(s).\n\nAlso confirm the change targets the correct file (files may have moved or been\nrestructured, or the edit may belong on a different page).\n\n## Step 6: Produce an action plan\n\nOutput the concrete next actions for the chosen recommendation:\n\n- The specific local edits needed: file paths, what to change, code fixes,\n  consolidation of the 1-3 bot PRs, and correct placement.\n- A short list of the verification findings that justify them, ordered blockers\n  first (unverified\u002Fhallucinated code, wrong file, failing CI checks, broken\n  rendering), then required edits, then nits.\n- Which bot PR(s) to close.\n- A PR description following the repo convention:\n    - a short bullet summary of what changed\n    - `Rendered page:` \u003Cpreview link>\n    - `Agent PR:` \u003Clink(s)>\n    - `Original issue:` #\u003CN> - \u003Citem>\n\n## Style rules to bake in\n\n- Model strings should be `gemini-flash-latest`, `gemini-pro-latest`, or other\n  valid `*-latest` aliases in sample code rather than specific versioned model\n  strings, which increase the maintenance burden when new model versions are\n  released.\n- Imports: `from google.adk.agents import Agent`; MCP uses `from\n  google.adk.tools.mcp_tool import McpToolset`. Agent variable is `root_agent`\n  (Python).\n- No em dashes or verbose AI-generated content: Use a colon in `**term**:\n  definition` bullets; split prose into sentences otherwise.\n- When referring to ADK, use \"ADK\", never \"Google ADK\" or \"The ADK\".\n- Do not start a sentence with an inline-code word.\n- Internal ADK-docs links are site-relative (e.g. `\u002Fsessions\u002Fmemory\u002F`); external\n  links must resolve. Do not invent links.\n- Verify all code samples against actual APIs and library code. The canonical\n  source repositories are listed in `docs\u002Fcommunity\u002Fcontributing-guide.md`.\n","# Review changes proposed by adk-bot (adk-bot-review)\n\nThis skill guides a rigorous review of adk-bot changes. It ensures documentation\nupdates are technically accurate, appropriately sized, and follow ADK docs\nconventions, based on Google's developer documentation style.\n\n## Step 1: Verify and research the proposed adk-bot change\n\n- Check that the PR title briefly describes the topic being updated, not only\n  the issue.\n- Confirm changes are made directly in the `.md` files and no \"do not merge\"\n  status tags were prematurely removed.\n- Check the PR's mergeable state and CI status. Note git conflicts and failing\n  checks as findings to resolve or to fix in the consolidating PR.\n- The input is one adk-bot-authored PR, or occasionally a few. From the PR,\n  trace back to the issue and the specific item it addresses. Identify the item\n  from the PR title (\"Update ADK doc according to issue #\u003CN> - \u003Citem>\") and\n  body. adk-bot often opens more than one PR for the same item. If multiple PRs\n  are provided, confirm they all address the same item and review them together\n  as one consolidation set. If they address different items, ask the user which\n  one to focus on before continuing.\n- Search closed issues and merged\u002Frejected PRs across the repository for similar\n  topics. Ensure the bot is not re-introducing changes, APIs, or stylistic\n  choices that human maintainers have previously debated and rejected.\n- Summarize the item's intended change and stated reasoning, and carry that\n  intent into the technical validation in the next steps.\n\n## Step 2: Assess update criteria and architecture\n\n- Prioritize smaller, surgical updates over comprehensive overhauls unless the\n  existing docs are entirely unclear.\n- Verify that the update provides a useful learning experience and is actionable\n  for a developer.\n- Ensure the content is placed appropriately within the ADK docs information\n  architecture.\n- Confirm the update length and prioritization are appropriate for the specific\n  code change (check if it is already covered by existing docs or API\n  references).\n\n## Step 3: Validate the change against source and intent\n\n- **Never assume an AI agent's code snippet is correct.**\n- Cross-reference all code examples against the\n  `https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python` repository.\n- Verify the information against relevant pull requests and actual ADK code in\n  the `https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python` repo.\n- Confirm the change actually implements what the linked issue and adk-bot PR\n  set out to do, and resolves the issue item it references.\n- Flag any part of the change that drifts from that stated intent, or any part\n  of the intent the change leaves unaddressed.\n\n## Step 4: Check quality and style\n\n### Headings\n\n- Maintain a logical h1, h2, h3 hierarchy without empty headings (stacking\n  headers).\n- Do not number headings (Use `## This heading`, not `## 1. This heading`).\n- Use imperative titles (e.g., \"Build agents\", not \"Building agents\").\n- Do not use command names in headings; call out the task to be done.\n\n### Language\n\n- Follow Google's developer documentation style\n  (https:\u002F\u002Fdevelopers.google.com\u002Fstyle) as the basis for conventions; consult it\n  for anything not covered here.\n- Use active voice phrasing (e.g., \"The system does X\", not \"X is done\").\n- Never use the word \"this\" without a noun object (e.g., \"This function is\n  used...\", not \"This is used...\").\n\n### Code snippets and formatting\n\n- **Enforce an 80-character line length limit** for general Markdown text\n  (excluding long URLs, unbreakable code blocks, or tables).\n- Check for rendering errors caused by spaces before backticks (```).\n- Use the `!!! warning\u002Ftip\u002Fnote` mkdocs-material admonition format for notes and\n  warnings instead of quote formats (`>`).\n- Do not use ALL CAPS except for code syntax; use bold or italics for emphasis.\n\n## Step 5: Report findings and decide the recommendation\n\nFirst, summarize the findings from the verification steps above, ordered\nblockers first, then required edits, then nits. Then choose one outcome below,\njustified by those findings:\n\n- **Close the bot PR(s).** (sometimes) The change is wrong, outdated, targets a\n  deprecated or unreleased API, or is already covered by live docs or a merged\n  PR. Record the reason and link the superseding doc or PR.\n- **Approve as-is** (rare). The bot PR(s) are correct, well-placed, and need no\n  edits.\n- **Edit in place, then approve** (sometimes). The existing branch is usable but\n  needs conflict resolution, corrections, consolidation, copyedits, or\n  relocation.\n- **Open a new consolidating PR** (most common). Rework the change across the\n  1-3 bot PRs into one PR that fixes code errors and hallucinations, edits for\n  quality, and places the content in the correct file. Then close the superseded\n  bot PR(s).\n\nAlso confirm the change targets the correct file (files may have moved or been\nrestructured, or the edit may belong on a different page).\n\n## Step 6: Produce an action plan\n\nOutput the concrete next actions for the chosen recommendation:\n\n- The specific local edits needed: file paths, what to change, code fixes,\n  consolidation of the 1-3 bot PRs, and correct placement.\n- A short list of the verification findings that justify them, ordered blockers\n  first (unverified\u002Fhallucinated code, wrong file, failing CI checks, broken\n  rendering), then required edits, then nits.\n- Which bot PR(s) to close.\n- A PR description following the repo convention:\n    - a short bullet summary of what changed\n    - `Rendered page:` \u003Cpreview link>\n    - `Agent PR:` \u003Clink(s)>\n    - `Original issue:` #\u003CN> - \u003Citem>\n\n## Style rules to bake in\n\n- Model strings should be `gemini-flash-latest`, `gemini-pro-latest`, or other\n  valid `*-latest` aliases in sample code rather than specific versioned model\n  strings, which increase the maintenance burden when new model versions are\n  released.\n- Imports: `from google.adk.agents import Agent`; MCP uses `from\n  google.adk.tools.mcp_tool import McpToolset`. Agent variable is `root_agent`\n  (Python).\n- No em dashes or verbose AI-generated content: Use a colon in `**term**:\n  definition` bullets; split prose into sentences otherwise.\n- When referring to ADK, use \"ADK\", never \"Google ADK\" or \"The ADK\".\n- Do not start a sentence with an inline-code word.\n- Internal ADK-docs links are site-relative (e.g. `\u002Fsessions\u002Fmemory\u002F`); external\n  links must resolve. Do not invent links.\n- Verify all code samples against actual APIs and library code. The canonical\n  source repositories are listed in `docs\u002Fcommunity\u002Fcontributing-guide.md`.\n",{"name":5,"description":7},"main","97b313e91243af5abaeaa97636689e8d0a7a18dd",".agents\u002Fskills\u002Fadk-bot-review",1486,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs","https:\u002F\u002Fadk.dev","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 08:55:10",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add google\u002Fadk-docs --skill adk-bot-review",{"tool":66,"command":67},"bunx","bunx skills add google\u002Fadk-docs --skill adk-bot-review",{"tool":69,"command":70},"pnpm","pnpm dlx skills add google\u002Fadk-docs --skill adk-bot-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fadk-bot-review\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"README.md","REFERENCE","参考文档",711,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fadk-bot-review\u002FREADME.md",[81,97,124,147],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":45},"01M69926JN8069KTYEM5F2X2BQ","weather_skill","A skill to get the weather information.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002Fexamples\u002Ftypescript\u002Fsnippets\u002Fskills\u002Fskills\u002Fweather_skill\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[93,94,95,96],"weather skill","weather","information","get",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":108,"publishedAt":45},"01M69924YWY5KH934DE8X6EQ34","integration-review","Reviews an ADK integration documentation page (a Markdown file under docs\u002Fintegrations\u002F) or an integration pull request for correctness, structure, style, working code, valid links, and catalog conventions. Produces a scored risk report (Critical, High, Medium, Low), a recommended decision (approve, request changes, or close PR), a top-level review response, and draft line-anchored comments; only fixes issues when explicitly asked. Triggers on \"integration-review\", \"review integration page\", \"review integration PR\", \"review this integration\", \"check integration docs\".","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fintegration-review\u002FSKILL.md",[103,104,105],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[109,110,25,111,31,26,112,113,114,115,116,117,118,119,40,42,120,121,122,123],"integration","integration review","review response","only","technical-writing","decision","issues","MCP","writing","critical","when","valid","structure","top","markdown",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":45},"01M69923EH0GYNDPZHHKW2MZ1S","integration-create","Creates a new ADK integration documentation page (a Markdown file under docs\u002Fintegrations\u002F) for a third-party tool, plugin, observability platform, data store, MCP server, or connector. Gathers details, picks the right category template, and drafts a page that follows adk-docs conventions. Triggers on \"integration-create\", \"create integration page\", \"new integration\", \"add an integration\", \"write an integration page\".","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fintegration-create\u002FSKILL.md",[130],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[132,133,109,42,134,135,136,137,138,139,26,116,44,140,141,142,143,144,34,145,146],"integration create","create","server","store","Connector","file","tool","mcp server","observability","integrations","platform","for","page","new","observability platform",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":157,"publishedAt":45},"01M69921WR7MSBCBPTYCGY2R6Z","api-reference-audit","Audits whether ADK API reference docs and version-pinned strings are up to date across all language SDKs. Compares in-repo versions against upstream releases and package registries, then reports what needs bumping and which process to follow, and emits an executable plan only when asked. Triggers on \"audit API reference\", \"check API ref docs\", \"are API docs up to date\", \"bump API doc versions\", \"check SDK doc versions\".","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-docs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fapi-reference-audit\u002FSKILL.md",[153,156],{"categoryNo":154,"categoryName":155,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[158,159,160,161,162,26,44,163,164,165,166,167,168,112,119,169,170,171,172,173,174,175],"api","audit","reference","api reference audit","releases","sdk","api doc","which","bump","strings","up","across","sdks","reports","plan","doc","repo","upstream"]