Make Python Recipe Deployable
Makes an existing Python recipe deployable: generates the serving files a container...
Install
npx skills add google/adk-recipes --skill make-python-recipe-deployable -g -a claude-code -y- Repository
- google/adk-recipes10.6k
- Category
- Design
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Makes an existing Python recipe deployable: generates the serving files a container needs (Dockerfile, .dockerignore, fast_api_app.py, app_utils/a2a.py, app_utils/services.py, app_utils/reasoning_engine_adapter.py) and configures the recipe to match (required serving dependencies, the App object in agent.py, the hatch wheel package, manifest.deployable). Interactive by design, it asks the recipe owner about runtime data directories and stops for a human decision when a recipe needs an ADK migration or carries a legacy app_utils generation. When docker is available it offers to PROVE the claim: it builds the generated Dockerfile, runs it, probes it, and refuses to flag a recipe deployable if the container does not come up. Does NOT deploy or write terraform. Use when the user wants to "make this recipe deployable", "add a Dockerfile to a recipe", "add the serving files", "containerize a recipe", "verify the container builds", or prepare a recipe for Cloud Build / Artifact Registry.
Make a Python Recipe Deployable
A deployable recipe is one that can be packaged into a container and run as a service. This skill writes the files that requires and configures the recipe to match.
It does not build an image, deploy anything, or provision infrastructure. Image builds happen later via Cloud Build → Artifact Registry; this skill's job ends when the files are correct.
The standard it implements lives in .github/policy.yml under deployability:, the minimum google-adk version, the required dependency list, the required
file list, and the legacy app_utils file list. Change the standard there,
not in the script.
What "deployable" means here, and the one distinction that matters
deployable in .github/schemas/manifest-schema.json means "can be deployed
with one click". Two independent questions decide the outcome:
- Does it need infrastructure a human must provision? If yes it is containerized, not one-click deployable.
- Did we PROVE the container works, or only assume it?
