Adk Style

google/adk-style

ADK development style guide for routine nits — Python idioms, codebase conventions, imports, typing, Pydantic patterns, formatting, logging, async/concurrency, and file organization. Use this skill whenever writing code, tests, or reviewing PRs for the ADK project to ensure compliance with styling and coding conventions. Triggers on "code style", "how should I format", "naming convention", "lint", "nit", "imports", "typing", "Pydantic patterns", "testing rules", "async", "io".

6k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

20998

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/google/adk-python --skill adk-style

What comes with it

20 720 bytes besides the instruction

references/async.md

references/documentation.md

references/file-organization.md

references/formatting.md

references/imports.md

references/logging.md

references/pydantic.md

references/testing.md

references/typing.md

references/visibility.md

The instruction itself

3 sections, as written by the author

ADK Style Guide

Style Guide (references/)

Visibility — naming conventions for module-private, internal, and package-private visibility.
Imports — relative vs absolute imports, TYPE_CHECKING patterns.
Typing — strong typing, avoiding Any, bare type names, keyword-only arguments, Optional vs | None, abstract parameter types, mutable default avoidance, runtime type discrimination.
Pydantic Patterns — Pydantic v2 usage, Field() constraints, field_validator, model_validator, private attributes, deprecation migration, post-init setup.
Formatting — indentation, line limits, and running pre-commit hooks.
Documentation — comments and docstrings.
Logging — lazy evaluation and log levels.
Async and Concurrency — async I/O requirements, avoiding blocking the event loop.
File Organization — file headers and class organization.

Testing

references/testing.md — core principles, 9 rules for writing ADK tests, test structure template

How to use it

Copy the folder

Take google/adk-style from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.