「structured output」の検索結果

General workflow for auditing ML CI failures, experiment regressions, training run failures, golden metric failures, and telemetry-backed ML work-product claims from local repositories, logs, metrics, configs, and artifacts. Use when Codex needs to decide whether an ML failure is a model/convergence issue, correctness bug, data/config issue, infrastructure/runtime issue, evaluation/gating policy issue, or unsupported claim, and produce structured evidence-backed outputs.

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

Build agents on OpenAI's platform patterns — assistants-style threads, function calling, structured outputs, and multi-step tool workflows. Use when working with OpenAI models as the agent engine.

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

Communicate data insights to non-technical stakeholders in a structured, persuasive format. Use when the user says "present these findings", "explain this analysis to leadership", "make a data presentation", "tell the story behind the data", "translate this into a business narrative", "make this insight actionable", "stakeholder readout", "executive summary of results", or needs to turn analysis output into a decision-ready document or slide deck.

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

Use @vercel/error to design, implement, migrate, audit, or review structured TypeScript errors. Trigger when a project uses or adopts the package, or when work involves its codes, fields, factories, HTTP APIs, telemetry, or terminal output. Use native Error for local failures that need no stable identity, recovery guidance, observability, or transport.

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

Research what people are actually saying about a topic in the last 30 days across Reddit, X / Twitter, YouTube, Hacker News, dev.to, Medium, and other public discourse platforms. API-free; uses WebSearch with platform-targeted site operators plus recency filters. Produces DISCOURSE.md (a structured brief) and JSON output the writer can consume. Complements blog-researcher (which focuses on authority sources) with a recency-and-engagement lens. Use when user says "blog discourse", "discourse research", "what are people saying about", "research what people are saying", "voice of customer", "social listening", "30-day research", "trend research", "what's the discussion on", "real-time research", "practitioner discourse", "/blog discourse".

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

Guides the usage of Gemini Interactions API on Gemini Enterprise Agent Platform. Use when the user wants to use the stateful, server-managed Interactions API for multi-turn conversations, background execution, streaming, structured output, and function calling on the Agent Platform.

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

Orchestrate AI coding agents (Claude Code, Codex, OpenCode) in isolated sandboxes using the @ai-hero/sandcastle SDK. Use when the user needs to (1) run agents AFK in Docker/Podman containers, (2) build multi-agent pipelines with plan-execute-review patterns, (3) run parallel agents on separate worktrees, (4) create iterative agent loops with maxIterations, (5) extract structured output from agent runs, (6) set up sandcastle in a new or existing project, or (7) write prompt files with template args and shell expressions.

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

Create custom modules for [Harbor Boost](https://github.com/av/harbor/tree/main/boost), an optimizing LLM proxy. Use when building Python modules that intercept/transform LLM chat completions—reasoning chains, prompt injection, structured outputs, artifacts, or custom workflows. Triggers on requests to create Boost modules, extend LLM behavior via proxy, or implement chat completion middleware.

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

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

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

Guides the usage of Gemini Interactions API on Gemini Enterprise Agent Platform. Use when the user wants to use the stateful, server-managed Interactions API for multi-turn conversations, background execution, streaming, structured output, and function calling on the Agent Platform.

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

Code auditor that grades software projects and the agents/developers who built them. Produces structured JSON + Markdown reports with a standardized rubric. Evaluates architecture, correctness, testing, authorship cohesiveness, ghost code, and more. Optionally ingests tmux session logs for process evidence and interrogates agents about specific problems found. Use when asked to "audit", "grade", "evaluate", "review code quality", "rate this project", "score the agents", or "assess the codebase". Especially useful after Marcus multi-agent experiments to grade agent output and track quality over time.

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

Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.

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

Runs a team of 50 LLM personas through a 30-round structured debate to predict market direction. Uses the Canvas Agent Swarm Service — the same shared infrastructure other skills use for smaller agent teams. Output is an influence-weighted consensus direction + trade recommendation with a transparent record of every argument, research query, and cross-examination.

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

Produces structured asset and liability summaries from financial documents for legal proceedings. Extracts valuations, ownership classifications, and encumbrances, then outputs net-worth overview, categorized schedules, disputed items, and documentation gaps. Use when preparing financial summaries for divorce/dissolution, estate planning, bankruptcy, business valuation, or settlement negotiations. Trigger on: net worth summary, marital estate, balance sheet, asset schedule, liability schedule, community/separate property.

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

Structured second-pass reasoning after code review or plan evaluation. Offers named reasoning methods (pre-mortem, inversion, red team, Socratic, etc.) to re-examine findings through a specific lens. Use after /mk:review verdict or any time deeper analysis is needed on an existing output. NOT for initial review (see mk:review); NOT for creating implementation plans (see mk:plan-creator).

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

Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.

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

Design spec with 98 rules for building CLI tools that AI agents can safely use. Covers structured JSON output, error handling, input contracts, safety guardrails, exit codes, and agent self-description.

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

Normalize and screen scattered foreign-trade leads into a conservative, structured lead pool that can flow into customer-intel research. Use when an operator has company names, websites, emails, or contact clues from search results and needs a standardized output with missing-field warnings, review flags, next-step suggestions, and customer-intel-ready JSON.

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

Discover prospect companies from a structured OpenClaw search brief, including public search and user-authorized data sources, then output a conservative candidate list ready for lead screening.

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

Find the first batch of foreign-trade prospect companies from public web, LinkedIn, and user-authorized data sources such as customs exports, trade show lists, association directories, CRM/Excel files, or historical customer data, then output a conservative, structured candidate list ready for lead screening.

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

Garanta estrutura válida de JSON/XML/código durante a geração, use modelos Pydantic para outputs type-safe, suporte modelos locais (Transformers, vLLM) e maximize velocidade de inferência com Outlines - biblioteca de geração estruturada da dottxt.ai

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

Orientação especializada para ajuste fino com GRPO/RL usando TRL para treinamento de modelos com raciocínio e tarefas específicas

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

Controle saída de LLM com regex e gramáticas, garanta geração válida de JSON/XML/código, aplique formatos estruturados e construa fluxos de trabalho multi-etapas com Guidance - framework de geração restrita da Microsoft Research

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

Extraia dados estruturados de respostas de LLM com validação Pydantic, tente novamente automaticamente extrações que falharem, analise JSON complexo com segurança de tipo e transmita resultados parciais com Instructor - biblioteca de saída estruturada testada em batalha

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