菜单
Use when using, reviewing, or implementing rielflow node add-ons. Applies to workflow.nodes[].addon, built-in rielflow add-ons, local scoped add-ons, third-party add-on resolvers, addon.config, addon.inputs, addon.env, node add-on validation, and add-on-backed worker nodes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `claude-code-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.
Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `codex-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.
Use when requested work should first be converted into a project-scope Rielflow workflow and then executed through Rielflow. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when requested work should first be converted into a project-scope Rielflow workflow and then executed through Rielflow. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when running, editing, or troubleshooting the packaged claude-code-deepdesign rielflow workflow for design-doc specification authoring with deep and broad review loops.
Use when installing a rielflow workflow bundle from a public GitHub directory URL with workflow checkout. Covers project/user scope destinations, duplicate handling, overwrite behavior, registry metadata, validation, and checkout troubleshooting.
| name | rielflow-node-addons |
| description | Use when using, reviewing, or implementing rielflow node add-ons. Applies to workflow.nodes[].addon, built-in rielflow add-ons, local scoped add-ons, third-party add-on resolvers, addon.config, addon.inputs, addon.env, node add-on validation, and add-on-backed worker nodes. |
| metadata | {"short-description":"Use rielflow node add-ons"} |
Use this skill for add-on-backed workflow node registry entries.
Current built-ins, version 1:
rielflow/chat-reply-workerrielflow/chat-persona-routerrielflow/codex-workerrielflow/claude-code-workerrielflow/workflow-package-sandbox-reviewrielflow/x-gateway-readrielflow/x-gatewayrielflow/mail-gateway-readrielflow/mail-gatewayrielflow/git-commitrielflow/git-pushRead references/addons-reference.md for field contracts and resolver guidance.
{
"id": "reply",
"addon": {
"name": "rielflow/chat-reply-worker",
"version": "1",
"config": {
"textTemplate": "Thanks {{event.actor.displayName}}.",
"visibility": "public",
"threadPolicy": "same-thread"
},
"inputs": {}
}
}
nodeFile or addon.nodes/node-*.json payloads.version.rielflow/ names are reserved for built-ins.addon.inputs becomes resolved node variables.addon.config is validated by the add-on descriptor.addon.env is explicit; ambient environment variables are not forwarded implicitly.execution.runtimeHints.rielflow/chat-persona-router for provider-neutral chat persona
selection instead of Discord-, Telegram-, or Matrix-specific routing prompts.rielflow/chat-reply-worker for chat replies so provider destinations own
Discord Gateway, Telegram Gateway, Matrix, or Chat SDK send behavior.