Developing Genkit Python
Develop AI-powered applications using Genkit in Python. Use when the user asks about Genkit, AI agents, flows, or tools in Python, or when encountering Genkit errors, import issues, or API problems.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Developing Genkit Python when an AI agent needs a reusable SKILL.md workflow for this job: Develop AI-powered applications using Genkit in Python. Use when the user asks about Genkit, AI agents, flows, or tools in Python, or when encountering Genkit errors, import issues, or API problems.
When not to use it
Skip Developing Genkit Python when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/developing-genkit-python # Save SKILL.md to ~/.claude/skills/developing-genkit-python/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/developing-genkit-python/SKILL.md. For a shared project, commit the folder at .claude/skills/developing-genkit-python/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Developing Genkit Python skill for this task: Agent or flow? If the task is conversational, multi-turn, or described as. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiinferred
The skill text mentions Gemini or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Genkit Python
Build AI features in Python — generate, stream, tools, flows, and multi-turn agents — with one SDK.
## Prerequisites
- Python **3.10+** and **`uv`** ([install](https://docs.astral.sh/uv/getting-started/installation/)) - Genkit CLI: `npm install -g genkit-cli` if `genkit --version` is missing
New app? [Setup](references/setup.md). Patterns? [Examples](references/examples.md).
## Hello World
```python from genkit import Genkit from genkit_google_genai import GoogleAI
ai = Genkit( plugins=[GoogleAI()], model='googleai/gemini-flash-latest', )
async def main(): response = await ai.generate(prompt='Tell me a joke about Python.') print(response.text)
if __name__ == '__main__': ai.run_main(main()) ```
## Agents (Beta)
Multi-turn chats with history, typed state, human approval, branching, and background work. Start here: [Agents](references/agents.md).
```python chat = agent.chat() res = await chat.send('Hello') # AgentResponse turn = chat.send_stream('Hello') # AgentTurn — .stream / .response ```
More: [sessions](references/agents-sessions.md) · [HITL](references/agents-human-in-the-loop.md) · [branching](references/agents-branching.md) · [background](references/agents-background.md) · [state](references/agents-state.md) · [artifacts](references/agents-artifacts.md) · [custom](references/agents-custom.md) · [HTTP](references/agents-http.md)
## Imports
- Google AI: `from genkit_google_genai import GoogleAI` - Agents: `from genkit.agent import InMemorySessionStore, ...` - Middleware: `from genkit_middleware import Middleware, ToolApproval, ...` - FastAPI: `from genkit_fastapi import serve_agent, serve_flow` - Evals: `from genkit_evaluators import register_genkit_evaluators`
## Workflow
1. **Agent or flow?** If the task is conversational, multi-turn, or described as "an agent", "assistant", or "chatbot", build it with `ai.define_agent` (see [Agents](references/agents.md)) rather than hand-rolling a `generate` + tools loop inside a flow. Reach for a plain flow only for single-shot, stateless generation. 2. Set **`GEMINI_API_KEY`**. Use prefixed model ids (`googleai/gemini-flash-latest`). 3. Enter via **`ai.run_main(main())`** for Genkit apps (especially under `genkit start`). See [Common Errors](references/common-errors.md). 4. Run with [Dev Workflow](references/dev-workflow.md) (`genkit start` + Dev UI). 5. Verify with traces, not a blind run. Running the app directly (`uv run`) does **not** capture dev traces. See [Genkit CLI](#genkit-cli-recommended) for how to run your app and capture traces. 6. Stuck? [Common Errors](references/common-errors.md) first.
## Genkit CLI (recommended)
`genkit start` unintrusively wraps any Python program that uses the Genkit library, running it unchanged while capturing traces from every Genkit action so you can prove tools were actually called and inspect model I/O from the terminal, even for headless checks. It forwards stdio, so interactive CLI tools that rely on stdin/stdout work without issues. Running the app directly (`uv run`) skips trace capture, so you're debugging blind.
**Primary pattern (default):** prefix `genkit start --` to your normal run command. This collects telemetry from any Genkit code your program runs, whether triggered from the dev UI, your own web server/web UI, or a plain script: ```bash genkit start -- uv run src/main.py genkit start --noui -- uv run src/main.py # same, without the Dev UI (still a persistent server) ``` `genkit start` runs until you stop it with Ctrl+C. That is expected and correct for the common cases: a server your web/mobile app calls, or an interactive CLI you exit yourself. `--noui` only drops the Dev UI; it is **not** a one-shot command and will not exit on its own. Do **not** use `genkit start` as a blocking step in automated/non-interactive contexts; use `flow:run` (below) for that.
**Non-interactive use (agents/CI):** add the global `--non-interactive` flag before `--` so the CLI uses defaults and never blocks on a prompt (e.g. the first-run analytics notice): `genkit start --non-interactive -- uv run src/main.py` (works with `flow:run` too).
**Run a flow (`flow:run`):** invoke a specific flow by name from the CLI. Append your run command after `--` to spin up the runtime just for this run (the command runs as-is to register your flows): ```bash genkit flow:run myFlow '{"data": "input"}' -- uv run src/main.py ``` This is **self-terminating**: it runs the flow once, prints a `Trace ID`, then exits, so it's the right choice for a quick, non-interactive check (unlike `genkit start`). Note: `flow:run` runs **flows** (`@ai.flow()`), not agents; you can't `flow:run` an agent (`ai.define_agent`) directly. To exercise an agent from the CLI, wrap one turn in a throwaway flow and run that (see [Agents](references/agents.md)).
**Debugging with traces:** the fastest way to see prompts, model inputs/outputs, tool calls, latencies, and errors. Inspect from the terminal after any run under `genkit start`: ```bash genkit trace:list # find recent trace IDs genkit trace:get <traceId> # full trace details (inputs, outputs, tool calls, errors) genkit trace:get <traceId> --format json # machine-readable JSON, safe to pipe into jq or other parsers ```
For machine-readable output, pass `--format json` to get clean JSON you can pipe into `jq` or other parsers. The **default** output is human-oriented (banner/log lines, possible truncation on large traces), so don't pipe that form directly; use `--format json`, grep, or the Dev UI trace viewer.
See [Dev Workflow](references/dev-workflow.md) for the full checklist and Dev UI walkthrough.
## References
- [Examples](references/examples.md): Structured output, streaming, flows, tools, embeddings. - [Setup](references/setup.md): New project bootstrap and plugins. - [Common Errors](references/common-errors.md): Read first when something breaks. - [FastAPI](references/fastapi.md): HTTP, `genkit_fastapi_handler`, parallel flows. - [Dotprompt](references/dotprompt.md): `.prompt` files and helpers. - [Evals](references/evals.md): Evaluators and datasets. - [Dev Workflow](references/dev-workflow.md): `genkit start`, Dev UI, checklist. - [Agents (Beta)](references/agents.md): Multi-turn API.
Intended uses
- Agent or flow? If the task is conversational, multi-turn, or described as
- Set GEMINIAPIKEY. Use prefixed model ids (googleai/gemini-flash-latest).
- Enter via ai.runmain(main()) for Genkit apps (especially under
- Run with Dev Workflow (genkit start + Dev UI).
- Verify with traces, not a blind run. Running the app directly (uv run)
- Stuck? Common Errors first.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.