メニュー
Call workflows explicitly bound to the current Agent as structured process tools.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Extract structured contract fields from existing contract text or already parsed contract content according to a configured field list. Use when the user asks for 合同字段抽取, 合同信息抽取, 合同关键信息提取, 合同台账, contract field extraction, contract metadata extraction, contract ledger data, or extracting parties, amount, dates, term, payment terms, renewal terms, breach clauses, or other configured contract fields. This skill does not parse uploaded files directly; it works only after contract text is available from another system or parser.
Design structured user clarification flows with the existing request_user_input capability so the assistant asks stable, focused questions with usable quick options instead of plain natural-language follow-up. Use when the user or another skill needs 问答交互, 表单交互, 结构化质询, 弹出输入框, 选项框, 单选, 多选, 补充信息, 确认参数, 文件上传提示, 表单填写, questionnaire, form interaction, structured clarification, user input, quick replies, or parameter confirmation.
Plan precise slide-by-slide PPT structures from a topic, text content, requirements, or uploaded-material summaries, and prepare a file-generator-ready PPTX payload for downstream generation. Use when the user asks for PPT planning, PowerPoint outline, slide planning, page-by-page PPT requirements, presentation storyboard, report deck structure, pitch deck outline, training deck plan, proposal slides, project report slides, business review slides, or when the user asks to first create a precise outline before generating a PPT file. This skill is the planning and layout layer, not the PPTX file generator.
Rewrite existing assistant replies, service replies, workplace messages, or explanatory answers to sound more natural, human, warm, polite, concise, professional, empathetic, and easy to understand while preserving the original facts and boundaries. Use when the user asks for 回复口吻优化, 语气优化, 改得自然一点, 去 AI 味, 减少机械感, 像正常人说话, 温和一点, 亲切一点, 礼貌一点, 客服话术优化, 办公回复优化, 心理关怀回复, 面向普通用户, polish response, rewrite tone, make it natural, make it warmer, make it less robotic, or humanize this reply.
Generate downloadable SVG and HTML technical diagrams from natural language or structured data, including system architecture, AI Agent architecture, data flow, flowchart, comparison matrix, sequence, state, and ER diagrams.
Generate downloadable SVG charts from structured data, including radar, bar, line, pie, doughnut, scatter, and score distribution charts.
| name | agent-workflow |
| description | Call workflows explicitly bound to the current Agent as structured process tools. |
| when_to_use | Use when the current Agent needs to run a configured workflow for approval-driven or process-driven handling. |
| provider_type | builtin |
| provider_id | workflow |
| runtime_type | tool |
| max_calls_per_turn | 10 |
| timeout_seconds | 600 |
| supported_callers | ["agent"] |
| required_config | ["agent_workflow"] |
| tools | ["list_agent_workflows","run_agent_workflow","get_workflow_run_status"] |
| display | {"icon":"workflow","category":"system","label":{"en_US":"Agent Workflow","zh_Hans":"Agent 工作流"},"description":{"en_US":"Call workflows bound to this Agent.","zh_Hans":"调用绑定到当前 Agent 的工作流。"},"when_to_use":{"en_US":"Use for configured approval or process workflows.","zh_Hans":"用于已配置的审批或流程工作流。"}} |
Use this skill only for workflows that are already bound to the current Agent.
Workflow calls are tool-mode calls. They do not take over the conversation stream. Return the tool result to the skill loop and continue from the structured status:
succeeded: use primary_output first, then outputs, to answer or continue. Do not claim that the workflow produced content that is not present in primary_output or outputs. If the workflow succeeded but returned no displayable output, tell the user the workflow ran but returned no displayable output and include workflow_run_id.pending_approval: tell the user approval is waiting and include the safe approval entry details from the tool result when useful.failed: summarize the error and decide whether to retry or ask for corrected input.Do not invent workflow IDs. The Agent runtime injects an available_workflows JSON list when workflows are bound. Use that injected list first to choose a binding. Call list_agent_workflows only if the injected list is missing, ambiguous, or stale.
Call run_agent_workflow only with a binding_id from available_workflows or the fallback list result. Pass the user's current request as inputs.query unless the binding's input_schema, required_inputs, or default_input_key explicitly says otherwise. After approval resumes, use get_workflow_run_status with the returned workflow_run_id to query the result.