[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698YDB3NEA5K1ZNJ03MRH60":3,"skill-same:01M698YDB3NEA5K1ZNJ03MRH60":83},{"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":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M698YDB3NEA5K1ZNJ03MRH60","adk-review",null,"Reviews the uncommitted changes in an adk-python working tree and reports correctness, design, public-API stability, test, sample and documentation gaps as a prioritized findings report, fixing them only when asked. Use when the user asks to review local changes, wants a self-review before opening a pull request, asks whether a change breaks the public API or needs tests, samples or docs, or asks what is wrong with the current diff. Required for changes to public APIs, core architecture (Runner, Workflow, BaseNode), new features and major refactors. Don't use for a single style nit (use adk-style), for diagnosing a failing test or a misbehaving agent at runtime (use adk-debug), or for wording a commit message or PR description (use adk-git).","google\u002Fadk-python","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698XZC2HCATT8VD5VAVZDTP",22217,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fadk-review\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"review","adk review","adk","failing","design","when","reviews","public api","local","self","runner","reports","only","review local changes","api","documentation","architecture","commit","change","workflow","python","docs","2026-11-10 10:12:30",false,"---\nname: adk-review\ndescription: >-\n  Reviews the uncommitted changes in an adk-python working tree and reports\n  correctness, design, public-API stability, test, sample and documentation\n  gaps as a prioritized findings report, fixing them only when asked. Use when\n  the user asks to review local changes, wants a self-review before opening a\n  pull request, asks whether a change breaks the public API or needs tests,\n  samples or docs, or asks what is wrong with the current diff. Required for\n  changes to public APIs, core architecture (Runner, Workflow, BaseNode), new\n  features and major refactors. Don't use for a single style nit (use\n  adk-style), for diagnosing a failing test or a misbehaving agent at runtime\n  (use adk-debug), or for wording a commit message or PR description (use\n  adk-git).\n---\n\n# ADK Change Reviewer\n\nReview the working-tree diff against the seven dimensions below, report what is\nwrong, and stop. Fix only what the user then asks you to fix.\n\n## Workflow\n\n1. `git status` and `git diff` (add `--staged` for staged work) to get the exact\n   set of added, modified, and deleted files.\n2. Review the diff file by file against the checklist.\n3. Emit the report in the format below.\n4. Stop. Do not edit any file, and do not offer to. Wait for the user to ask.\n5. If the user asks for fixes, apply them, then re-run the affected tests\n   (`pytest tests\u002Funittests\u002F{path}`) and `pre-commit run --files {paths}`.\n\nStep 4 is the part that is easy to get wrong: an unrequested fix buries the\nfindings the user asked for and mixes review output with new, unreviewed edits.\n\n## Checklist\n\n### 1. Correctness\n\n- **Types**: no new `mypy` errors. CI diffs `mypy` output against the base\n  branch and fails only on *newly introduced* errors, so a pre-existing error in\n  a file you touched is not a blocker but a new one is.\n- **Imports**: no circular imports; absolute imports where the module already\n  uses them.\n- **Exceptions**: no bare `except:`; catch a specific type and log with enough\n  context to identify the caller.\n- **Type discrimination**: check an object's type before reading a\n  type-specific attribute (for example confirm a node is an `LlmAgent` before\n  inspecting `mode`), so an unexpected node type raises nothing.\n- **Boundaries**: `None`, empty collections, zero, and empty strings are\n  handled by validation or a fallback default.\n- **Preconditions**: state invariants are checked before the core logic runs.\n\n### 2. Design\n\n- **Complexity**: functions or classes that would be clearer split up.\n- **Coupling**: high cohesion, low coupling; no anti-patterns introduced.\n- **Performance**: redundant computation, repeated I\u002FO in a loop, or\n  allocations that scale with input where they need not.\n- **Security**: inputs validated, sensitive data not logged, no injection,\n  resource exhaustion, or exposure of internal state.\n\n### 3. Style\n\nCross-reference the diff against the `adk-style` skill rather than restating\nits rules here: visibility and `_` prefixes, typing, Pydantic v2 patterns, lazy\nlogging, imports, async, and file organization.\n\nConfirm the changed files pass `pre-commit run --files {paths}`.\n\n### 4. Architecture and unintended outcomes\n\n- **Public API stability**: does the change modify, remove, or narrow a\n  public interface, class, method, argument list, or CLI surface under\n  `src\u002Fgoogle\u002Fadk\u002F`? A breaking change needs a deprecation cycle first, because\n  the package is released under Semantic Versioning and users pin minor\n  versions.\n- **Session, Artifact, and Memory service changes**: adding any new field to\n  `Session`, `ArtifactVersion`, `MemoryEntry`, or to `BaseSessionService`,\n  `BaseArtifactService`, `BaseMemoryService` and their schemas is a **breaking\n  change** (even if optional or defaulted), because existing downstream storage\n  subclasses and external backends will not persist or deserialize unknown\n  fields, causing silent state loss upon reload.\n- **Execution and resumption**: changes to workflows, nodes, or state must stay\n  compatible with the event execution lifecycle and with session resumption\n  (human-in-the-loop steps and checkpoints). See the `adk-architecture` skill.\n- **Concurrency and lifetime**: no race conditions; plugins, exporters, and\n  connections are closed on every path, including the error path.\n- **Database and runtime DDL safety**: runtime startup paths (e.g.,\n  `DatabaseSessionService.prepare_tables()` and\n  `_ensure_schema_indexes_exist()`) must never execute destructive DDL such as\n  `DROP INDEX` (which takes `ACCESS EXCLUSIVE` locks and breaks rolling\n  deployments\u002Frollbacks). Any additive runtime DDL must account for\n  multi-container startup races (process-local `asyncio.Lock` does not prevent\n  cross-container TOCTOU races on `checkfirst=True`) by wrapping creation in a\n  `SAVEPOINT` (`connection.begin_nested()`) and tolerating concurrent creation.\n- **Scope**: a new public name, parameter or flag the fix did not need; a flag\n  that keeps the buggy behavior as the default; a fix in a shared layer when\n  one caller needed it; an existing test assertion edited to match the new\n  behavior.\n\n### 5. Documentation impact\n\n- User-facing documentation lives in the separate `adk-docs` repository, so a\n  user-visible change needs a PR there as well; note it in the report.\n- Guides under `docs\u002Fguides\u002F` may need an update when a public API or workflow\n  pattern changes.\n- If the change alters a code unit's design contract, the `adk-unit-design`\n  skill owns the design document for that unit.\n\n### 6. Samples\n\n- Do existing samples under `contributing\u002Fsamples\u002F` still run against the\n  change?\n- Does a new capability warrant a new sample? Follow the `adk-sample-creator`\n  conventions if so.\n\n### 7. Tests\n\n- Every new or modified code path has a test under `tests\u002Funittests\u002F`.\n- A new test belongs in the existing `test_{module}*.py` file for its unit, not\n  in a file named after the change, which fragments that unit's coverage.\n- Tests follow the rules in the `adk-style` testing reference: one behavior per\n  test, behavior-named tests, no assertions on private attributes, minimal\n  fixtures, arrange\u002Fact\u002Fassert structure.\n\n## Ground each finding\n\nBefore reporting a finding, resolve the symbol through base classes (`Event`\nextends `LlmResponse`). For a correctness finding, name the input that makes it\nfail; for any other finding, quote the rule or convention it breaks. A finding\nthat is neither is a guess; leave it out.\n\n## Report format\n\nGroup findings by priority and give a file path and line for each. Do not\nreport a dimension with nothing to say.\n\n- ? **Critical**: bugs, type errors, race conditions, resource leaks, security\n  issues.\n- ? **Design**: complexity, readability, performance, architectural\n  misalignment.\n- ? **Style**: lint, formatting, non-lazy logging, typing mismatches.\n- ? **Docs, tests, samples**: missing or stale coverage, guides, samples.\n","# ADK Change Reviewer\n\nReview the working-tree diff against the seven dimensions below, report what is\nwrong, and stop. Fix only what the user then asks you to fix.\n\n## Workflow\n\n1. `git status` and `git diff` (add `--staged` for staged work) to get the exact\n   set of added, modified, and deleted files.\n2. Review the diff file by file against the checklist.\n3. Emit the report in the format below.\n4. Stop. Do not edit any file, and do not offer to. Wait for the user to ask.\n5. If the user asks for fixes, apply them, then re-run the affected tests\n   (`pytest tests\u002Funittests\u002F{path}`) and `pre-commit run --files {paths}`.\n\nStep 4 is the part that is easy to get wrong: an unrequested fix buries the\nfindings the user asked for and mixes review output with new, unreviewed edits.\n\n## Checklist\n\n### 1. Correctness\n\n- **Types**: no new `mypy` errors. CI diffs `mypy` output against the base\n  branch and fails only on *newly introduced* errors, so a pre-existing error in\n  a file you touched is not a blocker but a new one is.\n- **Imports**: no circular imports; absolute imports where the module already\n  uses them.\n- **Exceptions**: no bare `except:`; catch a specific type and log with enough\n  context to identify the caller.\n- **Type discrimination**: check an object's type before reading a\n  type-specific attribute (for example confirm a node is an `LlmAgent` before\n  inspecting `mode`), so an unexpected node type raises nothing.\n- **Boundaries**: `None`, empty collections, zero, and empty strings are\n  handled by validation or a fallback default.\n- **Preconditions**: state invariants are checked before the core logic runs.\n\n### 2. Design\n\n- **Complexity**: functions or classes that would be clearer split up.\n- **Coupling**: high cohesion, low coupling; no anti-patterns introduced.\n- **Performance**: redundant computation, repeated I\u002FO in a loop, or\n  allocations that scale with input where they need not.\n- **Security**: inputs validated, sensitive data not logged, no injection,\n  resource exhaustion, or exposure of internal state.\n\n### 3. Style\n\nCross-reference the diff against the `adk-style` skill rather than restating\nits rules here: visibility and `_` prefixes, typing, Pydantic v2 patterns, lazy\nlogging, imports, async, and file organization.\n\nConfirm the changed files pass `pre-commit run --files {paths}`.\n\n### 4. Architecture and unintended outcomes\n\n- **Public API stability**: does the change modify, remove, or narrow a\n  public interface, class, method, argument list, or CLI surface under\n  `src\u002Fgoogle\u002Fadk\u002F`? A breaking change needs a deprecation cycle first, because\n  the package is released under Semantic Versioning and users pin minor\n  versions.\n- **Session, Artifact, and Memory service changes**: adding any new field to\n  `Session`, `ArtifactVersion`, `MemoryEntry`, or to `BaseSessionService`,\n  `BaseArtifactService`, `BaseMemoryService` and their schemas is a **breaking\n  change** (even if optional or defaulted), because existing downstream storage\n  subclasses and external backends will not persist or deserialize unknown\n  fields, causing silent state loss upon reload.\n- **Execution and resumption**: changes to workflows, nodes, or state must stay\n  compatible with the event execution lifecycle and with session resumption\n  (human-in-the-loop steps and checkpoints). See the `adk-architecture` skill.\n- **Concurrency and lifetime**: no race conditions; plugins, exporters, and\n  connections are closed on every path, including the error path.\n- **Database and runtime DDL safety**: runtime startup paths (e.g.,\n  `DatabaseSessionService.prepare_tables()` and\n  `_ensure_schema_indexes_exist()`) must never execute destructive DDL such as\n  `DROP INDEX` (which takes `ACCESS EXCLUSIVE` locks and breaks rolling\n  deployments\u002Frollbacks). Any additive runtime DDL must account for\n  multi-container startup races (process-local `asyncio.Lock` does not prevent\n  cross-container TOCTOU races on `checkfirst=True`) by wrapping creation in a\n  `SAVEPOINT` (`connection.begin_nested()`) and tolerating concurrent creation.\n- **Scope**: a new public name, parameter or flag the fix did not need; a flag\n  that keeps the buggy behavior as the default; a fix in a shared layer when\n  one caller needed it; an existing test assertion edited to match the new\n  behavior.\n\n### 5. Documentation impact\n\n- User-facing documentation lives in the separate `adk-docs` repository, so a\n  user-visible change needs a PR there as well; note it in the report.\n- Guides under `docs\u002Fguides\u002F` may need an update when a public API or workflow\n  pattern changes.\n- If the change alters a code unit's design contract, the `adk-unit-design`\n  skill owns the design document for that unit.\n\n### 6. Samples\n\n- Do existing samples under `contributing\u002Fsamples\u002F` still run against the\n  change?\n- Does a new capability warrant a new sample? Follow the `adk-sample-creator`\n  conventions if so.\n\n### 7. Tests\n\n- Every new or modified code path has a test under `tests\u002Funittests\u002F`.\n- A new test belongs in the existing `test_{module}*.py` file for its unit, not\n  in a file named after the change, which fragments that unit's coverage.\n- Tests follow the rules in the `adk-style` testing reference: one behavior per\n  test, behavior-named tests, no assertions on private attributes, minimal\n  fixtures, arrange\u002Fact\u002Fassert structure.\n\n## Ground each finding\n\nBefore reporting a finding, resolve the symbol through base classes (`Event`\nextends `LlmResponse`). For a correctness finding, name the input that makes it\nfail; for any other finding, quote the rule or convention it breaks. A finding\nthat is neither is a guess; leave it out.\n\n## Report format\n\nGroup findings by priority and give a file path and line for each. Do not\nreport a dimension with nothing to say.\n\n- ? **Critical**: bugs, type errors, race conditions, resource leaks, security\n  issues.\n- ? **Design**: complexity, readability, performance, architectural\n  misalignment.\n- ? **Style**: lint, formatting, non-lazy logging, typing mismatches.\n- ? **Docs, tests, samples**: missing or stale coverage, guides, samples.\n",{"name":5,"description":7},"main","8cd3b12c8a5d658c5e0d3ea0731d8be34a092a4a",".agents\u002Fskills\u002Fadk-review",4356,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python","https:\u002F\u002Fgoogle.github.io\u002Fadk-docs\u002F","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 14:38:36",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add google\u002Fadk-python --skill adk-review",{"tool":75,"command":76},"bunx","bunx skills add google\u002Fadk-python --skill adk-review",{"tool":78,"command":79},"pnpm","pnpm dlx skills add google\u002Fadk-python --skill adk-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fadk-review\u002FSKILL.md",true,[],[84,113,140,164,180,188],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":94,"publishedAt":54},"01M698ZJNXJCE7T81AK0Y5R01D","bigquery-graph","Skill for Graph Query Language (GQL) or SQL\u002FPGQ queries against a property graph.\nIncludes path finding, multi-hop traversal, topological connection, shortest path,\nnode reachability, edge connectivity, and semantic graph queries.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fsrc\u002Fgoogle\u002Fadk\u002Fintegrations\u002Fbigquery\u002Fskills\u002Fbigquery-graph\u002FSKILL.md",[90,91],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":92,"categoryName":93,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[95,96,97,9,98,34,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"graph","bigquery","bigquery graph","for","sql","edge","graph query","hop","node","queries","language","query","connectivity","gql","semantic","multi","connection","path",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":54},"01M698ZEVMRDDFX2MH3GHQGSNW","bigquery-ai-ml","Leverages BigQuery's built-in machine learning and GenAI capabilities for advanced data analytics. Use when you need to write SQL queries that perform time-series forecasting, predict values, detect outliers or anomalies, find key drivers, perform semantic search or vector search, classify text, calculate similarity, summarize content, translate language, evaluate models, filter by semantic conditions, measure the causal effect of an intervention, compute correlations between columns, detect change points or structural breaks, extract trend or seasonality components, or leverage generative AI capabilities in BigQuery. Do not use for general BigQuery dataset, table, or job management requests.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fsrc\u002Fgoogle\u002Fadk\u002Fintegrations\u002Fbigquery\u002Fskills\u002Fbigquery-ai-ml\u002FSKILL.md",[119],{"categoryNo":92,"categoryName":93,"taxonomyType":29,"taxonomyTypeDesc":30},[121,96,122,123,124,37,125,126,127,128,129,130,131,132,133,9,134,135,34,136,137,138,139],"ai ml","ml","bigquery ai ml","vector","generative","you","advanced","dataset","leverage","structural","time","effect","search","summarize","genai","generative ai","translate","components","capabilities",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":151,"publishedAt":54},"01M698ZCN6SZ9SJ8E9970M47FQ","code-review-skill","Reviews code with feedback tailored to the developer's profile in session state.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fcontributing\u002Fsamples\u002Fenvironment_and_skills\u002Fskills_inject_state\u002Fskills\u002Fcode-review-skill\u002FSKILL.md",[146,149,150],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[152,153,154,32,155,156,157,158,159,160,161,162,38,163],"review skill","code","code review skill","code review","session","state","developer","feedback","profile","with","session state","true",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":54},"01M698ZAMH02NSGXMR533ETWYW","weather-skill","A skill that provides weather information based on reference data.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fcontributing\u002Fsamples\u002Fenvironment_and_skills\u002Fskills_agent\u002Fskills\u002Fweather-skill\u002FSKILL.md",[170],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,174,175,176,177,178,179],"weather skill","weather","data","reference","speed","get","wind","information",{"skillNo":181,"name":166,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":54},"01M698Z8QFDZ713E03589BHEG5","A skill that provides weather information based on reference data and scripts.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fcontributing\u002Fsamples\u002Fenvironment_and_skills\u002Fskills\u002Fskills\u002Fweather-skill\u002FSKILL.md",[185],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[173,172,179,178,187,177,176,175,174],"scripts",{"skillNo":189,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":54},"01M698Z6P1NZFW6A6V342AWZPR","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fcontributing\u002Fsamples\u002Fenvironment_and_skills\u002Flocal_environment_skill\u002Fskills\u002Fweather-skill\u002FSKILL.md",[192],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,175,179,174]]