Agent skill · writing content · google

integration-review

Reviews an ADK integration documentation page (a Markdown file under docs/integrations/) or an integration pull request for correctness, structure, style, working code, valid links, and catalog conventions. Produces a prioritized review report, 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".

Why this skill is useful

Provides a structured review process for integration documentation that includes specific criteria and examples, which the AI wouldn't reliably generate on its own.

What it needs

About 12k tokens when loaded. Last updated 2026-08-07. 1,462 stars on the source repository.

What this skill does

ADK Integration Page Reviewer (integration-review) This skill guides a rigorous review of integration documentation pages in the adk-docs repository. Integration pages live under docs/integrations/ and document third-party tools, plugins, observability platforms, data stores, MCP servers, connectors, and other extensions to ADK agents. The authoritative sources of truth for this review are: 1. The repository's CONTRIBUTING.md (see the "Integrations" section and its acceptance criteria). 2. The existing shipping integration pages, which are the real template. Always open and compare against peers of the same category: MCP tools: docs/integrations/github.md, docs/integrations/notion.md Observability: docs/integrations/phoenix.md, docs/integrations/arize-ax.md Plugins: docs/integrations/daytona.md, docs/integrations/goodmem.md 3. The catalog rendering logic in scripts/integrations.py. [!NOTE] Read this skill and follow its steps whenever asked to review an integration page or an integration PR. Review workflow Step 1: Gather the change If reviewing a PR, use gh to pull it and read the full cumulative diff, not a single commit: gh pr view <n> --repo google/adk-docs and gh pr diff <n> --repo google/adk-docs. A stale mkdocs.yml entry or asset can hide in files that only show in the full diff. Check whether "Allow edits from maintainers" is enabled (maintainerCanModify) so fixes can be pushed directly if requested later. Confirm the CLA is signed (the google-cla bot). An unsigned CLA is a 🔴 Critical finding and blocks merge until signed. If reviewing a local file, run git status and git diff to see the change. Step 2: Find and read similar pages Find 5 or more similar pages and read them in full. Identify candidates in one pass by scanning catalogtags (grep catalogtags docs/integrations/.md) and matching the tag under review (e.g. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/integration-review

View the source on GitHub

Browse the @skills marketplace