[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698YB2JTZ5DX3DDCQNTZJWW":3,"skill-same:01M698YB2JTZ5DX3DDCQNTZJWW":74},{"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},"01M698YB2JTZ5DX3DDCQNTZJWW","adk-git",null,"Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a pull request, drafting a PR description, or checking that a change is shaped to land. Don't use for generic git mechanics such as rebasing, resolving conflicts, cherry-picking, or branch surgery; those need no skill. Don't use to judge the content of a change (use adk-review) or for code style and naming (use adk-style).","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-git\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"adk git","adk","git","messages","drafting","when","types","mechanics","message","conflicts","conventional commits","branch","template","plan","testing","code","commit","change","python","review","writing","2026-11-10 10:12:30",false,"---\nname: adk-git\ndescription: >-\n  Writes commit messages and pull request descriptions for the adk-python\n  repository: Conventional Commits types and scopes, subject lines that say why\n  a change was made, and the linked-issue and testing-plan sections the PR\n  template requires. Use when writing or rewording a commit message, squashing\n  commits before a pull request, drafting a PR description, or checking that a\n  change is shaped to land. Don't use for generic git mechanics such as\n  rebasing, resolving conflicts, cherry-picking, or branch surgery; those need\n  no skill. Don't use to judge the content of a change (use adk-review) or for\n  code style and naming (use adk-style).\n---\n\n# Commit and Pull Request Conventions\n\n## Commit message format\n\nConventional Commits:\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n```\n\nThe type decides where the commit lands in `CHANGELOG.md`. `release-please`\ngenerates the changelog from merged commit subjects, so the wrong type either\nfiles the change under the wrong heading or drops it from the release notes\nentirely.\n\n| Type                                               | Changelog section        |\n| -------------------------------------------------- | ------------------------ |\n| `feat`                                             | Features                 |\n| `fix`                                              | Bug Fixes                |\n| `perf`                                             | Performance Improvements |\n| `docs`                                             | Documentation            |\n| `refactor`, `test`, `build`, `ci`, `style`, `chore` | hidden, no entry         |\n\nThe mapping lives in `.github\u002Frelease-please-config.json`. A type that is not\nlisted there produces no changelog entry at all.\n\nScope is optional. Use a short module name with no underscores\n(`fix(cli):`, `feat(a2a):`, `fix(sessions):`) or leave it off.\n\n## Subject line\n\nSay why the change exists, not which lines moved. A reviewer who reads only the\nsubject should understand the motivation.\n\n| Write                                                        | Not                                                            |\n| ------------------------------------------------------------ | -------------------------------------------------------------- |\n| `fix(sessions): prevent duplicate events when resuming HITL` | `fix(sessions): check interrupt_id before appending`           |\n| `feat(workflow): support parallel tool execution`            | `feat(workflow): add asyncio.gather call in execute_tools_node` |\n| `refactor: make graph public for dev UI serialization`       | `refactor: make graph a public field on Workflow`              |\n\nRules:\n\n1. Imperative mood: `add`, not `added`.\n2. Lowercase the first word after the colon. `release-please` copies the\n   subject into `CHANGELOG.md` verbatim, and the great majority of merged\n   commits are lowercase, so capitalizing makes one line stand out.\n3. No trailing period.\n4. Keep the subject under about 72 characters. Nothing enforces this, but each\n   commit renders as one changelog line.\n5. Reference the issue in the body, not the subject: `Fixes #1234` or\n   `Closes #1234`, or the full issue URL when the issue lives in another\n   repository.\n\nSelf-check: read the subject back and ask whether it says *why* someone made\nthe change. If it only names the edit, rewrite it.\n\n## Commit body\n\nAdd a blank line, then a short concrete explanation. For a feature, show the\nnew capability or a usage line. For a fix, say what caused the failure and how\nthe change addresses it.\n\n```text\nfeat(workflow): support JSON string parsing in schema validation\n\nParse JSON strings into dicts or Pydantic models when input_schema or\noutput_schema is defined on a node.\n```\n\n```text\nfix(sessions): prevent duplicate events when resuming HITL\n\ninterrupt_id was not checked before appending, so resuming twice appended the\nsame event twice. Ignore interrupts that were already processed.\n\nFixes #1234\n```\n\n## Before committing\n\n`pre-commit` reformats and checks staged files, and the same hooks run again in\nCI on every pull request, so a commit made with hooks skipped fails there.\n\n```bash\npre-commit install                  # once per clone\npre-commit run --files {paths}      # check only what changed\n```\n\nThe hooks include `isort`, `pyink`, `addlicense`, `mdformat`, `ruff`,\n`codespell`, and repository-local compliance checks; see\n`.pre-commit-config.yaml`. If `pre-commit` is not installed, point the user at\nthe `adk-setup` skill rather than committing unformatted code.\n\n## Pull requests\n\n- Every PR except a small documentation or typo fix needs a linked issue.\n  Put `Closes: #{issue_number}` in the PR description, or describe the problem\n  and solution inline following the issue templates.\n- Fill in the Testing Plan section of `.github\u002Fpull_request_template.md`,\n  including a summary of passing `pytest` results.\n- Do not merge on GitHub. The `Do Not Merge on GitHub` check fails on every PR\n  to `main` by design; a maintainer lands the change and it is synced back to\n  the repository. GitHub then shows the PR as closed with a `merged` label\n  rather than merged, and the landed commit carries the original authorship.\n  That red check is expected and is not something to fix.\n","# Commit and Pull Request Conventions\n\n## Commit message format\n\nConventional Commits:\n\n```text\n\u003Ctype>(\u003Cscope>): \u003Cdescription>\n```\n\nThe type decides where the commit lands in `CHANGELOG.md`. `release-please`\ngenerates the changelog from merged commit subjects, so the wrong type either\nfiles the change under the wrong heading or drops it from the release notes\nentirely.\n\n| Type                                               | Changelog section        |\n| -------------------------------------------------- | ------------------------ |\n| `feat`                                             | Features                 |\n| `fix`                                              | Bug Fixes                |\n| `perf`                                             | Performance Improvements |\n| `docs`                                             | Documentation            |\n| `refactor`, `test`, `build`, `ci`, `style`, `chore` | hidden, no entry         |\n\nThe mapping lives in `.github\u002Frelease-please-config.json`. A type that is not\nlisted there produces no changelog entry at all.\n\nScope is optional. Use a short module name with no underscores\n(`fix(cli):`, `feat(a2a):`, `fix(sessions):`) or leave it off.\n\n## Subject line\n\nSay why the change exists, not which lines moved. A reviewer who reads only the\nsubject should understand the motivation.\n\n| Write                                                        | Not                                                            |\n| ------------------------------------------------------------ | -------------------------------------------------------------- |\n| `fix(sessions): prevent duplicate events when resuming HITL` | `fix(sessions): check interrupt_id before appending`           |\n| `feat(workflow): support parallel tool execution`            | `feat(workflow): add asyncio.gather call in execute_tools_node` |\n| `refactor: make graph public for dev UI serialization`       | `refactor: make graph a public field on Workflow`              |\n\nRules:\n\n1. Imperative mood: `add`, not `added`.\n2. Lowercase the first word after the colon. `release-please` copies the\n   subject into `CHANGELOG.md` verbatim, and the great majority of merged\n   commits are lowercase, so capitalizing makes one line stand out.\n3. No trailing period.\n4. Keep the subject under about 72 characters. Nothing enforces this, but each\n   commit renders as one changelog line.\n5. Reference the issue in the body, not the subject: `Fixes #1234` or\n   `Closes #1234`, or the full issue URL when the issue lives in another\n   repository.\n\nSelf-check: read the subject back and ask whether it says *why* someone made\nthe change. If it only names the edit, rewrite it.\n\n## Commit body\n\nAdd a blank line, then a short concrete explanation. For a feature, show the\nnew capability or a usage line. For a fix, say what caused the failure and how\nthe change addresses it.\n\n```text\nfeat(workflow): support JSON string parsing in schema validation\n\nParse JSON strings into dicts or Pydantic models when input_schema or\noutput_schema is defined on a node.\n```\n\n```text\nfix(sessions): prevent duplicate events when resuming HITL\n\ninterrupt_id was not checked before appending, so resuming twice appended the\nsame event twice. Ignore interrupts that were already processed.\n\nFixes #1234\n```\n\n## Before committing\n\n`pre-commit` reformats and checks staged files, and the same hooks run again in\nCI on every pull request, so a commit made with hooks skipped fails there.\n\n```bash\npre-commit install                  # once per clone\npre-commit run --files {paths}      # check only what changed\n```\n\nThe hooks include `isort`, `pyink`, `addlicense`, `mdformat`, `ruff`,\n`codespell`, and repository-local compliance checks; see\n`.pre-commit-config.yaml`. If `pre-commit` is not installed, point the user at\nthe `adk-setup` skill rather than committing unformatted code.\n\n## Pull requests\n\n- Every PR except a small documentation or typo fix needs a linked issue.\n  Put `Closes: #{issue_number}` in the PR description, or describe the problem\n  and solution inline following the issue templates.\n- Fill in the Testing Plan section of `.github\u002Fpull_request_template.md`,\n  including a summary of passing `pytest` results.\n- Do not merge on GitHub. The `Do Not Merge on GitHub` check fails on every PR\n  to `main` by design; a maintainer lands the change and it is synced back to\n  the repository. GitHub then shows the PR as closed with a `merged` label\n  rather than merged, and the landed commit carries the original authorship.\n  That red check is expected and is not something to fix.\n",{"name":5,"description":7},"main","8cd3b12c8a5d658c5e0d3ea0731d8be34a092a4a",".agents\u002Fskills\u002Fadk-git",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add google\u002Fadk-python --skill adk-git",{"tool":66,"command":67},"bunx","bunx skills add google\u002Fadk-python --skill adk-git",{"tool":69,"command":70},"pnpm","pnpm dlx skills add google\u002Fadk-python --skill adk-git","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fadk-git\u002FSKILL.md",true,[],[75,108,135,161,177,185],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":89,"publishedAt":45},"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",[81,86],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[90,91,92,9,93,25,94,95,96,97,98,99,100,101,102,103,104,105,106,107],"graph","bigquery","bigquery graph","for","sql","edge","graph query","hop","node","queries","language","query","connectivity","gql","semantic","multi","connection","path",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":45},"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",[114],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},[116,91,117,118,119,29,120,121,122,123,124,125,126,127,128,9,129,130,25,131,132,133,134],"ai ml","ml","bigquery ai ml","vector","generative","you","advanced","dataset","leverage","structural","time","effect","search","summarize","genai","generative ai","translate","components","capabilities",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":148,"publishedAt":45},"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",[141,144,145],{"categoryNo":142,"categoryName":143,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[149,39,150,43,151,152,153,154,155,156,157,158,159,160],"review skill","code review skill","code review","session","state","developer","feedback","profile","with","session state","reviews","true",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":45},"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",[167],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[169,170,171,172,173,174,175,176],"weather skill","weather","data","reference","speed","get","wind","information",{"skillNo":178,"name":163,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":45},"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",[182],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[170,169,176,175,184,174,173,172,171],"scripts",{"skillNo":186,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":190,"publishedAt":45},"01M698Z6P1NZFW6A6V342AWZPR","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fadk-python\u002Fblob\u002Fmain\u002Fcontributing\u002Fsamples\u002Fenvironment_and_skills\u002Flocal_environment_skill\u002Fskills\u002Fweather-skill\u002FSKILL.md",[189],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[169,170,172,176,171]]