developing-genkit-tooling
Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/genkit-ai/genkit /tmp/genkit && ln -s /tmp/genkit/skills/developing-genkit-tooling ~/.claude/skills/developing-genkit-toolingFrom README
Developing Genkit Tooling Naming Conventions Consistency in naming helps users and agents navigate the tooling. CLI Commands Use kebab-case with colon separators for subcommands. Format: noun:verb or category:action Examples: flow:run, eval:run, init Arguments: Use camelCase in code (flowName) but standard format in help text ( ). MCP Tools Use snakecase for tool names to align with MCP standards. Format: verbnoun Examples: listflows, runflow, listgenkitdocs, readgenkitdocs CLI Command Architecture Commands are implemented in cli/src/commands/ using commander. Runtime Interaction Most commands require interacting with the user's project runtime. Use the runWithManager utility to handle the lifecycle of the runtime process. Output Formatting Logging: Use logger from @genkit-ai/tools-common/utils. Machine Readable: Provide options for JSON output or file writing when the command produces data.