AI-assisted development

AI assistants write better Genkit code when they understand Genkit’s core concepts (flows, actions, dotprompt, and so on) and how to run and debug your application. The fastest way to give your assistant that knowledge is with Genkit Agent Skills.

Genkit Agent Skills

Agent Skills are curated knowledge packages that teach AI agents how to build applications with Genkit. They bundle best practices, common error handling, API usage, and development workflows into a format your assistant can load on demand. Skills are maintained in the Genkit Skills GitHub repository.

Currently available skills:

• developing-genkit-js: For developing Genkit applications with Node.js and TypeScript.

Installation

Install skills into your project with skills.sh:

npx skills add genkit-ai/skills

You can also copy the skill folder manually into the location your tool expects. See your tool’s documentation for where agent skills live.

Usage

Genkit skills follow the Agent Skills Specification. Point your agent environment (such as Antigravity in Gemini Enterprise, Cursor, or Claude Code) at the relevant skill directory to enable Genkit-specific capabilities. Once installed, your assistant can consult the skill whenever it works on Genkit code, so it produces idiomatic, up-to-date results.

Genkit MCP server

Skills give your assistant knowledge. The Genkit MCP server gives it the ability to interact with your running application. Installing both provides the most complete experience.

The MCP server exposes tools that let an assistant:

• Look up and search Genkit documentation.
• Start, restart, and stop your application runtime.
• List and run the flows in your Genkit app.
• Fetch execution traces for analysis and debugging.

For setup instructions, see the Genkit MCP server documentation.

Google Developer Knowledge MCP server

The Genkit MCP server ships a documentation bundle for Genkit itself. Most Genkit apps also call other Google products, such as Gemini models, Firebase, Google Cloud, or Google Maps Platform, and your assistant needs current docs for those too. The Developer Knowledge MCP server is a remote MCP server that searches live, official Google developer documentation, including this site (genkit.dev), so your assistant grounds its answers in published docs rather than relying only on its training data.

The server exposes three tools: search_documents, get_documents, and answer_query, and it complements the Genkit skills and the Genkit MCP server. To add it alongside the Genkit MCP server, follow Configure your IDE or coding agent and select your client. To teach your assistant when to reach for these tools, also install the retrieving-developer-knowledge agent skill.

With the Genkit skill, the Genkit MCP server, and the Developer Knowledge MCP server installed, you can ask for work that spans Genkit and the rest of the Google stack in one prompt, for example:

Look up the current Firebase App Hosting deployment docs, then update my
Genkit flow in src/index.ts to read its API key from the environment and
add the apphosting.yaml config needed to deploy it.

Retrieve docs as markdown

Skills and the MCP server both need an install step. When you just want an agent to read a page, every URL on this site also answers with plain markdown, which costs far fewer tokens than the rendered HTML. Replace <lang> with js, go, dart, or python, and <page> with the docs slug:

URL	What you get
https://genkit.dev/docs/<lang>/<page>.md	one page, rendered for one SDK
https://genkit.dev/docs/<page>.<lang>.md	the same content, addressed from the neutral slug
https://genkit.dev/docs/<page>.md	the unfiltered page, every SDK in one file

Larger bundles are indexed at llms.txt, which lists a whole-SDK bundle at https://genkit.dev/llms-<lang>.txt, per-topic bundles under https://genkit.dev/_llms-txt/, and condensed rules files at https://genkit.dev/GENKIT.js.md and https://genkit.dev/GENKIT.go.md that are sized to paste into a system prompt. llms.txt lists exactly what exists, so check it rather than guessing a URL.

Rules files

Most assistants read a file checked into your repository: AGENTS.md, CLAUDE.md, .cursor/rules/, or .github/copilot-instructions.md. Whichever one your team uses, point it at the rules file and the markdown endpoints so the assistant can pull the page it needs.