Index of every page on this site: llms.txt
All skills
google avatar

/scaffold-python-recipe

@ead8d7f
by googlegoogle/adk-recipes11k stars
2,961
Run it yourself

This skill should be used when the user wants to "create a new Python ADK recipe", "scaffold a new Python recipe", "generate a new Python recipe in contrib", "add a new Python recipe to the adk-recipes repository", or "create a Python adk recipe". It utilizes an automated script to copy template files and resolve basic placeholders.

Use this Skill: https://skilld.dev/gh/google/adk-recipes/scaffold-python-recipe

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈90 tokens for metadata: the name and description. ≈820 when used: this file. ≈1.6k more on demand in 6 files.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈359 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Scaffolding a New Python ADK Recipe

Use this skill to scaffold a new Python ADK recipe inside this repository using the automated script at scripts/scaffold.py.


Rules

  1. No Manual Boilerplate Writing: Always use scripts/scaffold.py to create the recipe. Never write the boilerplate files manually.
  2. Do Not Modify After Scaffolding: Once the script runs successfully, do not make any further changes to the recipe in this turn.
  3. Use the Correct Terminology (Recipe): Always refer to what is being created as a recipe, never as a "project". Ensure all output messages, instructions, and explanations to the user use "recipe" exclusively.

Inputs

You must have both pieces of information below before running the script. If either is missing or was not explicitly provided by the user, ask for it — do not assume or use a default.

1. Output Directory (Required — must ask if not provided)

The user must choose one of these valid locations:

  • contrib/python/ — community recipes; preferred for new Python recipes
  • core/python/ — curated recipes
  • contrib/ — legacy flat layout, still accepted; prefer contrib/python/

If the user has not specified which directory, ask them to choose. Do not proceed until a valid choice is confirmed.

This skill cannot scaffold a vertical plugin (plugins/<vertical>/<solution>/). Those have a different shape — SKILL.md, EVAL.yaml, scripts/, assets/, references/, tests/unit/ — and no template ships for them yet. If the user asks for one, tell them so rather than scaffolding into the wrong place.

2. Recipe Name (Required — must ask if not provided)

The recipe name must satisfy all of the following rules:

  • Contains only lowercase letters and hyphens (a-z, -)
  • Is 30 characters or less
  • Does not start or end with a hyphen

If the user provided a name, validate it against these rules before proceeding. If it is invalid, explain which rule it violates and ask for a corrected name. Do not proceed until a valid name is confirmed.


Run

Execute the scaffold script:

python3 .agents/skills/scaffold-python-recipe/scripts/scaffold.py --name <RECIPE_NAME> --output-dir <OUTPUT_DIRECTORY>

The script accepts exactly two flags: --name (required) and --output-dir (required). Do not pass any other flags.


Respond

Once the script succeeds, inform the user the recipe is ready and highlight the following required next steps:

  1. Update manifest.yaml: Fill in the description, ownership.team, and ownership.poc fields (placeholders are marked with TODO:). This file is validated by CI and must not contain placeholder values. Use the generate-manifest skill if you want it populated automatically from the source code.
  2. Update README.md: Replace the generic title and description with details specific to this recipe (ownership/POC live in manifest.yaml, above — not in the README).

Then, provide these quick-start commands:

cd <OUTPUT_DIRECTORY>/<RECIPE_NAME>
uv sync                  # install dependencies
uv run pytest            # run the test suite
uv run adk run app       # run the agent interactively

Do not make any further changes. End your turn.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill provides a utility for scaffolding new Python recipes using the ADK framework. It includes security considerations such as input validation and path traversal guards within its scaffolding script to ensure safe project creation. The generated templates adhere to standard development practices, including dependency management through established tools and integration with vendor-provided telemetry services.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at ead8d7f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 2 months ago
metadata
{
  "author": "Google",
  "license": "Apache-2.0",
  "version": "1.0.0"
}

README badge

README badge for google/adk-recipes/scaffold-python-recipe