adk-sample-creator

Scaffold ADK Python sample directories with agent.py and README.md files.

21.1k|3.8k|Updated Apr 1, 2025
One-click install
npx skills add https://github.com/google/adk-python --skill adk-sample-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adk-sample-creator
Source: https://github.com/google/adk-python/tree/main/.agents/skills/adk-sample-creator
Command: npx skills add https://github.com/google/adk-python --skill adk-sample-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces the friction of adding new, consistent, repository-ready ADK Python samples by guiding you through choosing the correct contributing folder and creating the required file structure.

Core Features & Use Cases

  • Creates new sample scaffolding: Builds a directory-per-sample structure with an agent.py and a README.md.
  • Guides correct placement: Prompts you to select the appropriate contributing subdirectory to extend (e.g., workflow_samples, task_samples, new_workflow_samples).
  • Enforces sample conventions: Uses consistent snake_case naming and provides pattern-specific guidance for workflows vs standalone agents, including README sections and Mermaid graph requirements.
  • Supports common ADK patterns: Facilitates examples that demonstrate agent patterns like dynamic nodes, standalone agents, and fan-out/fan-in.

Quick Start

Use this skill when you want to add a new ADK Python example, then choose the contributing folder you want to add it under and describe the feature/pattern your sample should demonstrate.

Frequently Asked Questions about adk-sample-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new ADK Python sample directory?

To scaffold an ADK Python sample, generate a new directory containing an agent.py and README.md, ensuring the folder uses snake_case naming and follows repository conventions for the contributing subfolder.

What is the correct folder structure for contributing ADK workflow samples?

ADK workflow samples require a directory-per-sample structure placed under the appropriate contributing subfolder, such as workflow_samples or task_samples, containing both an agent.py file and a README.md.

How do I add agent patterns like fan-out/fan-in to ADK contributing examples?

You can add agent patterns like fan-out/fan-in by creating a new sample directory under the contributing folder and generating template-aligned content in the agent.py file that demonstrates the specific dynamic node or standalone agent workflow.

Does the ADK sample generator enforce repository conventions for README files?

Yes, the ADK sample generator enforces repository conventions by providing pattern-specific guidance for README.md files, including required sections and Mermaid graph visualizations for workflow or standalone agent patterns.

Can I create standalone agent examples without setting up a full workflow?

Yes, you can create standalone agent examples by selecting the appropriate contributing subfolder and generating the required agent.py and README.md files using the standalone agent pattern template.

What are the limitations when scaffolding ADK samples with dynamic nodes?

When scaffolding ADK samples with dynamic nodes, you must manually ensure the logic falls under the correct contributing subfolder and validate that the sample folder naming strictly follows snake_case conventions before generation.