跳转到主要内容

intent-recognition

星标199,700
分支23,565
更新时间2026年8月7日 15:42

Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embeds_other (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an agent tool). Must be used whenever the current turn requires choosing or reconsidering the intent of an automation request, including compound requests, independent automations introduced mid-build, one-off questions or reports that need external systems you cannot query directly, and requests that need clarification before an anchor can be chosen. Do not load for routine edits or extensions when the conversation already targets a workflow or Agent.

· 实时索引

安装

用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。

想先保存到本地?可下载 RuleHub 当前索引到的 GitHub 仓库压缩包。

下载 Zip
文件资源管理器2 个文件
SKILL.mdreadonly
nameintent-recognition
descriptionClassifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-a...

intent-recognition

Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embeds_other (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an agent tool). Must be used whenever the current turn requires choosing or reconsidering the intent of an automation request, including compound requests, independent automations introduced mid-build, one-off questions or reports that need external systems you cannot query directly, and requests that need clarification before an anchor can be chosen. Do not load for routine edits or extensions when the conversation already targets a workflow or Agent.

When to use

Use this skill when the user needs help with tasks related to intent recognition.

Guidelines

  • Follow repository conventions in n8n-io/n8n
  • Prefer minimal, focused changes
  • Validate outputs before finishing