Agent skill · writing content · google
integration-create
Creates a new ADK integration documentation page (a Markdown file under docs/integrations/) 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".
Why this skill is useful
Provides a structured template and specific conventions for creating integration documentation that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 1,462 stars on the source repository.
What this skill does
ADK Integration Page Creator (integration-create) This skill creates a new integration page for the adk-docs repository. Integration pages live under docs/integrations/ and are auto-discovered into a card catalog. The output of this skill is a strong starting point, not a finished page: when done, run the integration-review skill on it and test with mkdocs serve. The real template is the set of existing shipping pages. Before drafting, open the exemplar(s) for the chosen category and match their structure and conventions: 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 To find more similar pages, scan catalogtags in one pass (grep catalogtags docs/integrations/.md) and read the ones sharing the category's tag (e.g. mcp, observability) or product domain in full. Match live pages and repo conventions rather than inferring everything from the templates below. See CONTRIBUTING.md (the "Integrations" section) for the human-facing contract. For the full rulebook applied during review, see the integration-review skill. Step 1: Gather inputs Ask the user for whatever is not already provided: Product / integration name (drives catalogtitle and the H1). Category, which selects the template: MCP tool (an MCP server the agent connects to) Observability (tracing / metrics / evaluation exporter) Plugin (an installable package exposing tools or callbacks) Language support: Python only, or Python + TypeScript. Package name (PyPI / npm) and install command. Connection style for MCP: local (stdio) and/or remote (HTTP). Tools or methods the integration exposes (for the table). Links: product docs, GitHub repo, PyPI/npm, where to get an API key. Icon: confirm an asset will be added at docs/integrations/assets/<slug>.png. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/integration-create