「structured output」の検索結果

INVOKE THIS SKILL when you need human-in-the-loop approval, custom middleware, or structured output. Covers HumanInTheLoopMiddleware for human approval of dangerous tool calls, creating custom middleware with hooks, Command resume patterns, and structured output with Pydantic/Zod.

日本語の概要は準備中です。原文の説明を表示しています。

Extract structured data matching a JSON schema from websites. Handles complex nested schemas, arrays, pagination, and validation. Always outputs via formatOutput.

日本語の概要は準備中です。原文の説明を表示しています。

Research a US employment law topic across federal, state, and city jurisdictions and produce structured research notes with proper source attribution. Use this skill any time the user asks about US employment laws, regulations, or pending legislation - from a single jurisdiction question to a 50-state survey. Triggers include phrases like "research [employment law topic]", "what are the laws on [employment topic]", "state-by-state [employment topic]", "help me understand [topic] across the US", or any prompt that asks for a legal landscape overview before another deliverable. Always run this BEFORE the employment-law-dashboard skill if a dashboard is the eventual output. Output is a structured research note that distinguishes primary sources (statutes, regs, agency guidance) from secondary sources (law firm alerts, tracker orgs).

日本語の概要は準備中です。原文の説明を表示しています。

Design a structured protocol for auditing AI-generated text against Ennis's six CT standards. Use when students need to critically evaluate AI output in any subject.

日本語の概要は準備中です。原文の説明を表示しています。

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

日本語の概要は準備中です。原文の説明を表示しています。

LLM application architecture expert for RAG, prompting, agents, and production AI systemsUse when "rag system, prompt engineering, llm application, ai agent, structured output, chain of thought, multi-agent, context window, hallucination, token optimization, llm, rag, prompting, agents, structured-output, anthropic, openai, langchain, ai-architecture" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive patterns for building AI-powered code generation tools, code assistants, automated refactoring, code review, and structured output generation using LLMs with function calling and tool use. Use when "code generation, AI code assistant, function calling, structured output, code review AI, automated refactoring, tool use, code completion, agent code, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Invokes Google Gemini models for structured outputs, image generation, text-to-speech narration, multi-modal tasks, and Google-specific features. Use when users request Gemini, image generation, Gemini TTS or a synthesized voice, structured JSON output, Google API integration, or cost-effective parallel processing.

日本語の概要は準備中です。原文の説明を表示しています。

Generates a fully structured SEO content brief for a target keyword and optionally pushes it to a Notion database. Use this skill whenever the user says 'create a content brief', 'brief this keyword', 'run a content brief for', 'generate a brief', 'write a brief for [keyword]', 'content brief on [topic]', or any variation where someone needs a keyword researched and turned into a structured writing assignment with H1, H2 outline, FAQ, internal links, word count target, and writer notes. Also triggers when the user provides a keyword and asks for an SEO brief, editorial brief, or writing spec. Outputs a mandatory structured format that the text parser maps directly to Notion properties. Supports single-keyword and batch (CSV) modes.

日本語の概要は準備中です。原文の説明を表示しています。

Build production-ready AI agents with PydanticAI — type-safe tool use, structured outputs, dependency injection, and multi-model support.

日本語の概要は準備中です。原文の説明を表示しています。

Use Neo4j GenAI Plugin ai.text.* functions and procedures for in-Cypher embedding generation, text completion, structured output, chat, tokenization, and batch ingestion. Covers ai.text.embed(), ai.text.embedBatch(), ai.text.completion(), ai.text.structuredCompletion(), ai.text.aggregateCompletion(), ai.text.chat(), ai.text.tokenCount(), ai.text.chunkByTokenLimit(), and provider configuration for OpenAI, Azure OpenAI, VertexAI, and Amazon Bedrock. Requires CYPHER 25. Replaces deprecated genai.vector.encode(). Use when writing pure-Cypher GraphRAG, embedding nodes in-graph, generating structured maps from prompts, or calling LLMs inside Cypher queries. Does NOT handle neo4j-graphrag Python library pipelines — use neo4j-graphrag-skill. Does NOT handle vector index creation/search — use neo4j-vector-index-skill.

日本語の概要は準備中です。原文の説明を表示しています。

Design a structured protocol for auditing AI-generated text against Ennis's six CT standards. Use when students need to critically evaluate AI output in any subject.

日本語の概要は準備中です。原文の説明を表示しています。

Use when needing 100% type-safe, schema-valid data extraction from LLMs. Keywords: structured output, JSON schema, Pydantic, Zod, type-safe, constrained decoding, validation, tool use.

日本語の概要は準備中です。原文の説明を表示しています。

Data structures and serialization formats for agent-to-agent communication. Covers message envelopes, structured output schemas, capability declarations, task handoff payloads, error/retry signaling, and context windows as data structures. Deep comparison of A2A protocol, MCP, OpenAI function calling, and LangChain message types. Teaches when to use rigid schemas vs free-form with validation, typed vs untyped, streaming vs batch. Activate on: "agent message format", "agent communication schema", "agent-to-agent protocol", "A2A protocol", "MCP message format", "structured output for agents", "agent interop", "interchange format", "agent serialization", "task handoff format", "capability declaration". NOT for: what agents say to each other (use agent-conversation-protocols), orchestration topology (use multi-agent-coordination), building agent infrastructure (use agentic-infrastructure-2026).

日本語の概要は準備中です。原文の説明を表示しています。

Construa agentes de IA prontos para produção com PydanticAI — type-safe tool use, structured outputs, dependency injection, e suporte multi-modelo.

日本語の概要は準備中です。原文の説明を表示しています。

给定 PMID/PMCID 取结构化全文（NLM BioC XML/JSON）。封装 BioC PubMed（标题+摘要）和 BioC PMC OA（开放获取全文）端点，输出按章节切分的段落、表格上下文、RAG 友好 chunk，适合大批量入向量库。Fetches structured fulltext from NLM BioC API for PMID/PMCID, outputs section-segmented paragraphs and RAG-ready chunks. 触发词：全文抽取 / BioC / RAG 入库 / 文献全文 / PMC 开放获取 / structured fulltext / 段落抽取 / 表格抽取 / chunking / fulltext to vector store / paragraph extraction.

日本語の概要は準備中です。原文の説明を表示しています。

Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework

日本語の概要は準備中です。原文の説明を表示しています。

Fast structured generation and serving for LLMs with RadixAttention prefix caching. Use for JSON/regex outputs, constrained decoding, agentic workflows with tool calls, or when you need 5× faster inference than vLLM with prefix sharing. Powers 300,000+ GPUs at xAI, AMD, NVIDIA, and LinkedIn.

日本語の概要は準備中です。原文の説明を表示しています。

OpenAI API (developers.openai.com) の Responses API リファレンス。 text generation, embeddings, structured outputs, streaming, function calling, programmatic tool calling, conversation state, prompt caching, reasoning models, background mode, compaction, multi-agent。 webhooks, error codes, rate limits, Realtime API server controls。 公式 SDK (Python / JavaScript(JS) / .NET / Java / Go / Ruby), openai CLI。 Chat Completions / Assistants からの移行, deprecations。

Claude Agent SDK (code.claude.com/docs/en/agent-sdk) の TypeScript / Python リファレンス。 query(), ClaudeAgentOptions / Options, custom tools (in-process MCP), createSdkMcpServer, hooks, permissions (canUseTool), subagents, sessions (resume / fork), streaming, structured outputs, slash commands, tool search, hosting / observability。

Claude API (platform.claude.com) の Messages API リファレンス。 streaming (SSE), thinking (adaptive) / effort, prompt caching, context editing, compaction, structured outputs, Message Batches, token counting, vision / PDF, Files API, citations, embeddings (Voyage AI)。 errors, rate limits, beta headers, Amazon Bedrock / Vertex AI / Foundry 経由アクセスを含む。

Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework

日本語の概要は準備中です。原文の説明を表示しています。

Build autonomous AI agents with Claude Agent SDK. Structured outputs guarantee JSON schema validation, with plugins system and hooks for event-driven workflows. Prevents 14 documented errors. Use when: building coding agents, SRE systems, security auditors, or troubleshooting CLI not found, structured output validation, session forking errors, MCP config issues, subagent cleanup.

日本語の概要は準備中です。原文の説明を表示しています。

Data structures and serialization formats for agent-to-agent communication. Covers message envelopes, structured output schemas, capability declarations, task handoff payloads, error/retry signaling, and context windows as data structures. Compares the version-pinned A2A, MCP, and JSON-RPC role boundaries covered by this bundle; OpenAI and LangChain-specific APIs require their own current sources. Teaches when to use rigid schemas versus free-form content with validation, typed versus untyped boundaries, and streaming versus batch. Activate on: "agent message format", "agent communication schema", "agent-to-agent protocol", "A2A protocol", "MCP message format", "structured output for agents", "agent interop", "interchange format", "agent serialization", "task handoff format", "capability declaration". NOT for: what agents say to each other (use agent-conversation-protocols), orchestration topology (use multi-agent-coordination), building agent infrastructure (use agentic-infrastructure-2026).

日本語の概要は準備中です。原文の説明を表示しています。