跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 developing-genkit-js

Developing Genkit Js

在节点使用 Genkit 开发 AI 驱动应用程序 。 js/Type脚本. 当用户在JavaScript/TypeScript中询问Genkit,AI代理,流量,或工具时使用,或者遇到Genkit错误,验证问题,打出错误,或API问题时使用.

60841 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在 Node.js/TypeScript 中使用 Genkit 开发 AI 驱动应用程序

何时用

用户在 JavaScript/ TypeScript 中询问Genkit, AI代理, 流量, 或工具, 或遇到 Genkit 错误, 验证问题, 类型错误或 API 问题时询问

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Genkit JS、Prerequisites、Hello World、Prompts (Dotprompt)、Agents (Beta)、Generative UI (A2UI)。 其中含规范建议的小节:分步指令、边界情况。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/setup.md、references/dotprompt.md、references/agents.md、references/agents-sessions.md、references/agents-human-in-the-loop.md、references/agents-branching.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Develop AI-powered applications using Genkit in Node.js/TypeScript. Use when the user asks about Genkit, AI agents, flows, or tools in JavaScript/TypeScript, or when encountering Genkit errors, validation issues, type errors, or API problems.

Genkit JSPrerequisitesHello WorldPrompts (Dotprompt)Agents (Beta)Generative UI (A2UI)MiddlewareCritical: Do Not Trust Internal KnowledgeError Troubleshooting ProtocolDevelopment WorkflowFinding DocumentationCLI Usage (recommended)

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
developing-genkit-js
description
Develop AI-powered applications using Genkit in Node.js/TypeScript. Use when the user asks about Genkit, AI agents, flows, or tools in JavaScript/TypeScript, or when encountering Genkit errors, validation issues, type errors, or API problems.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 12
  • references/setup.md
  • references/dotprompt.md
  • references/agents.md
  • references/agents-sessions.md
  • references/agents-human-in-the-loop.md
  • references/agents-branching.md
  • references/agents-background.md
  • references/agents-state.md
  • references/agents-artifacts.md
  • references/agents-multi-agent.md
  • references/agents-custom.md
  • references/agents-deployment.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「developing-genkit-js」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-97cb8c59db2b999c-%E5%8F%91%E5%B1%95%E5%9F%BA%E5%9B%A0%E7%BB%84Js.html
请存为 .cursor/skills/developing-genkit-js/SKILL.md 或 .claude/skills/developing-genkit-js/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/genkit-ai/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/genkit-ai/skills' --list

npx skills add 'https://github.com/genkit-ai/skills' --skill 'developing-genkit-js'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: developing-genkit-js description: Develop AI-powered applications using Genkit in Node.js/TypeScript. Use when the user asks about Genkit, AI agents, flows, or tools in JavaScript/TypeScript, or when encountering Genkit errors, validation issues, type errors, or API problems. metadata: category: AiAndMachineLearning --- # Genkit JS ## Prerequisites Ensure the `genkit` CLI is available. - Run `genkit --version` to verify. Minimum CLI version needed: **1.29.0** - If not found or if an older version (1.x < 1.29.0) is present, install/upgrade it: `npm install -g genkit-cli@^1.29.0`. **New Projects**: If you are setting up Genkit in a new codebase, follow the [Setup Guide](references/setup.md). ## Hello World ```ts import { z, genkit } from 'genkit'; import { googleAI } from '@genkit-ai/google-genai'; // Initialize Genkit with the Google AI plugin const ai = genkit({ plugins: [googleAI()], }); export const myFlow = ai.defineFlow({ name: 'myFlow', inputSchema: z.string().default('AI'), outputSchema: z.string(), }, async (subject) => { const response = await ai.generate({ model: googleAI.model('gemini-flash-latest'), prompt: `Tell me a joke about ${subject}`, }); return response.text; }); ``` ## Prompts (Dotprompt) `.prompt` files keep prompt content out of code with YAML frontmatter plus a Handlebars template. See [Dotprompt](references/dotprompt.md): `promptDir`, `ai.prompt()` (call/stream/render), variants, partials, named schemas via `ai.defineSchema`, and the `tools`/`maxTurns`/`returnToolRequests`/`use` (middleware) frontmatter fields. ## Agents (Beta) Genkit has a preview **agent** API for persistent, multi-turn conversations (sessions, snapshots, interrupts, branching, background execution). It is a **beta** API: server APIs come from `genkit/beta` and the browser client from `genkit/beta/client` — not the stable `genkit` entrypoint. **Requires `genkit` >= 1.39.0.** For more details see: - [Agents](references/agents.md): defining/serving an agent and client-managed state (start here). - [Sessions & persistence](references/agents-sessions.md): session stores (`InMemory`/`File`/`Firestore`). - [Human-in-the-loop / interrupts](references/agents-human-in-the-loop.md): pausing for approval/input and resuming. - [Branching](references/agents-branching.md): forking a conversation from a snapshot. - [Background agents](references/agents-background.md): detaching long-running turns and polling. - [Working with state](references/agents-state.md): typed custom session state, auto-synced to the client. - [Artifacts](references/agents-artifacts.md): producing and reading named deliverables. - [Multi-agent orchestration](references/agents-multi-agent.md): delegating to sub-agents. - [Advanced custom agents](references/agents-custom.md): `defineCustomAgent` for full turn control. - [Deploying agents](references/agents-deployment.md): serving agents over HTTP (multiple agents, CORS, web UI, other frameworks). ## Generative UI (A2UI) Genkit has an **A2UI** (Agent-to-UI) plugin (`@genkit-ai/a2ui`) that lets an agent stream interactive UI **surfaces** (cards, lists, forms, buttons), not just prose. The whole server-side integration is the `a2ui()` model middleware in an agent's (or `ai.generate`'s) `use` array; the browser renders surfaces with an `@a2ui/*` renderer plus the helpers in `@genkit-ai/a2ui/client`. It builds on the beta agent client (`genkit/beta` + `genkit/beta/client`). - [A2UI](references/a2ui.md): server middleware, options, client rendering, user actions/forms, custom catalogs, and the security/trust boundary. ## Middleware Middleware wraps generation (retries, fallback, extra tools, request/response transforms) and attaches via the `use: [...]` array on `ai.generate`, prompts, and agents. - [Using middleware](references/middleware.md): the `use` array and the `@genkit-ai/middleware` package (`retry`, `fallback`, `artifacts`, `agents`, `filesystem`, `skills`, `toolApproval`) plus built-in core middleware. - [Building custom middleware](references/middleware-custom.md): writing your own with `generateMiddleware` and registering it via `.plugin()`. ## Critical: Do Not Trust Internal Knowledge Genkit recently went through a major breaking API change. Your knowledge is outdated. You MUST lookup docs. Recommended: ```sh genkit docs:read js/get-started.md genkit docs:read js/flows.md ``` See [Common Errors](references/common-errors.md) for a list of deprecated APIs (e.g., `configureGenkit`, `response.text()`, `defineFlow` import) and their v1.x replacements. **ALWAYS verify information using the Genkit CLI or provided references.** ## Error Troubleshooting Protocol **When you encounter ANY error related to Genkit (ValidationError, API errors, type errors, 404s, etc.):** 1. **MANDATORY FIRST STEP**: Read [Common Errors](references/common-errors.md) 2. Identify if the error matches a known pattern 3. Apply the documented solution 4. Only if not found in common-errors.md, then consult other sources (e.g. `genkit docs:search`) **DO NOT:** - Attempt fixes based on assumptions or internal knowledge - Skip reading common-errors.md "because you think you know the fix" - Rely on patterns from pre-1.0 Genkit **This protocol is non-negotiable for error handling.** ## Development Workflow 1. **Agent or flow?**: If the task is conversational, multi-turn, or described as "an agent", "assistant", or "chatbot", build it with `ai.defineAgent` (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. **Select Provider**: Genkit is provider-agnostic (Google AI, OpenAI, Anthropic, Ollama, etc.). - If the user does not specify a provider, default to **Google AI**. - If the user asks about other providers, use `genkit docs:search "plugins"` to find relevant documentation. 3. **Detect Framework**: Check `package.json` to identify the runtime (Next.js, Firebase, Express). - Look for `@genkit-ai/next`, `@genkit-ai/firebase`, or `@genkit-ai/google-cloud`. - Adapt implementation to the specific framework's patterns. 4. **Follow Best Practices**: - See [Best Practices](references/best-practices.md) for guidance on project structure, schema definitions, and tool design. - **Be Minimal**: Only specify options that differ from defaults. When unsure, check docs/source. 5. **Ensure Correctness**: - Run type checks (e.g., `npx tsc --noEmit`) after making changes. - If type checks fail, consult [Common Errors](references/common-errors.md) before searching source code. - Verify with traces, not a blind run. Running the app directly (`node`/`tsx`/`npm start`) does **not** capture dev traces. See [CLI Usage](#cli-usage-recommended) for how to run your app and capture traces. 6. **Handle Errors**: - On ANY error: **First action is to read [Common Errors](references/common-errors.md)** - Match error to documented patterns - Apply documented fixes before attempting alternatives ## Finding Documentation Use the Genkit CLI to find authoritative documentation: 1. **Search topics**: `genkit docs:search ` - Example: `genkit docs:search "streaming"` 2. **List all docs**: `genkit docs:list` 3. **Read a guide**: `genkit docs:read ` - Example: `genkit docs:read js/flows.md` ## CLI Usage (recommended) `genkit start` unintrusively wraps any Node.js 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 your app directly (`node`/`tsx`/`npm start`) 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 -- npx tsx --watch src/index.ts genkit start --noui -- npx tsx src/index.ts # 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. **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 -- npx tsx src/index.ts` (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"}' -- npx tsx src/index.ts ``` This is **self-terminating**: it runs the flow once, prints a `Trace ID`, then exits (inspect it with `genkit trace:get `). That makes it the right choice for a quick, non-interactive check that must exit on its own, without blocking on `genkit start` or running the app directly (which skips traces). Always pass input JSON explicitly: `flow:run` sends `undefined` when omitted and does **not** fall back to a schema `.default()`. Note: `flow:run` runs **flows** (`ai.defineFlow`), not agents; you can't `flow:run` an agent (`ai.defineAgent`) 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 # full trace details (inputs, outputs, tool calls, errors) genkit trace:get --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 [CLI Reference](references/docs-and-cli.md) for more commands, and `genkit --help` for the full list. ## References - [Best Practices](references/best-practices.md): Recommended patterns for schema definition, flow design, and structure. - [Dotprompt](references/dotprompt.md): `.prompt` files — `promptDir`, `ai.prompt()`, variants, partials, named schemas, and `tools`/`maxTurns`/`returnToolRequests`/`use` frontmatter. - [Docs & CLI Reference](references/docs-and-cli.md): Documentation search, CLI tasks, and workflows. - [Common Errors](references/common-errors.md): Critical "gotchas", migration guide, and troubleshooting. - [Setup Guide](references/setup.md): Manual setup instructions for new projects. - [Examples](references/examples.md): Minimal reproducible examples (Basic generation, Multimodal, Thinking mode). - [Agents (Beta)](references/agents.md): Agent basics, serving, and client-managed state. Deeper topics: [sessions](references/agents-sessions.md), [human-in-the-loop](references/agents-human-in-the-loop.md), [branching](references/agents-branching.md), [background agents](references/agents-background.md), [state](references/agents-state.md), [artifacts](references/agents-artifacts.md), [multi-agent](references/agents-multi-agent.md), [custom agents](references/agents-custom.md), [deployment](references/agents-deployment.md). - [Middleware](references/middleware.md): using middleware and the `@genkit-ai/middleware` package. See also [building custom middleware](references/middleware-custom.md). - [A2UI (Generative UI)](references/a2ui.md): the `@genkit-ai/a2ui` plugin (the `a2ui()` middleware), options, client rendering, user actions/forms, custom catalogs, and security.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…