Genkit skills: install framework development skills for an agent by language

Who it's for

This guide is for people who will write Genkit apps with an agent and accept picking a skill directory by language. The Genkit framework is at

https://genkit.dev/

The repository is at

https://github.com/genkit-ai/skills

These skills follow the Agent Skills specification, described at

https://agentskills.io/specification

The existing materials expand developing-genkit-js: develop Genkit apps with Node.js and TypeScript. The skill file is at

https://github.com/genkit-ai/skills/blob/main/skills/developing-genkit-js/SKILL.md

There is also a Go install command that points at developing-genkit-go. The materials say to point the agent environment at the matching skill directory so Genkit-related capabilities turn on.

It fits people whose repo language is already decided and who are ready to run npx skills add. It does not fit people who want every language at once without naming --skill. Do not infer from the language names in the title that skills without an install command are already installable.

First try in 3 minutes

Follow only the official recommended JavaScript/TypeScript path.

Preconditions: this machine can run npx, and you intend to write Genkit with Node.js and TypeScript. Before running, confirm the current project is where the skill should be written.

Install location: written by npx skills add; the materials also say to point the agent at the matching skill directory. The materials do not name npx’s default landing place; do not invent a path that does not appear. If the agent does not find the skill, point the environment at that skill directory as the official text says.

Copy and run:

npx skills add genkit-ai/skills --skill developing-genkit-js

Success signal: the command finishes normally and the agent can cite developing-genkit-js. Do a read-only check first: ask it which files it would change to add a minimal Genkit capability in this repo, but not to write disk yet. If it can point at the skill and name proposed files, it is loaded.

Writing app code changes the repo. Do not authorize a real write until file paths and overwrite risk are confirmed.

Use cases

Case 1: Develop a Genkit app in TypeScript. Maps to developing-genkit-js. Fits an existing Node.js project, or a new TS project you are about to create. Ask for a plan first, then allow writes. On success, the edits follow the framework usage given by that skill. The materials do not expand specific APIs or directory templates.

Case 2: Install the matching skill for a Go project. Maps to the official command npx skills add genkit-ai/skills --skill developing-genkit-go. Fits when the main language is Go. Install first, then ask the agent only how it would change Go code, without writing files yet. The success signal is that it loads developing-genkit-go instead of the JS skill by mistake. Besides this install command, the materials do not expand Go-side steps.

Usage limits

Do not mix the two --skill values and treat that as one install. Do not invent skill names that do not appear. The page title also mentions Dart, but the existing materials have no Dart install command; do not reuse the JS or Go command for it.

The materials do not name required clients. Do not assume capabilities are on until the agent is pointed at the skill directory. Preview before writing code. More detail is on the official repository:

https://github.com/genkit-ai/skills