[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PDM8FEW3R6ZBX4VPVH5Q4":3,"skill-same:01M71PDM8FEW3R6ZBX4VPVH5Q4":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M71PDM8FEW3R6ZBX4VPVH5Q4","raticode-workflow-builder",null,"Create, edit, validate, and preflight Raticode workflows written in the Rattish language. Use for workflow authoring, graph changes, node configuration, routes, inputs, or execution readiness. Do not use the legacy TOML authoring commands for these tasks.","zacharyivie\u002FRaticode","zacharyivie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F105333103?v=4","01M71PDETJC7M5NX913P9M467M","Zachary Ivie","01M71PDEV8Z9PMZZ02QY2RBSY2",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fzacharyivie\u002FRaticode\u002Fblob\u002Fmain\u002Fskills\u002Fraticode-workflow-builder\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"workflow","workflow builder","raticode workflow builder","builder","workflows","Legacy","use","execution","authoring","validate","commands","toml","edit","node","for","readiness","changes","do","workflow authoring","create","2026-11-10 13:02:02",false,"---\nname: raticode-workflow-builder\ndescription: Create, edit, validate, and preflight Raticode workflows written in the Rattish language. Use for workflow authoring, graph changes, node configuration, routes, inputs, or execution readiness. Do not use the legacy TOML authoring commands for these tasks.\n---\n\n# Raticode workflow builder\n\nAuthor Raticode workflows as Rattish source. A registered workflow lives at\n`\u003Cproject>\u002F.raticode\u002F\u003Cworkflow-id>\u002Fworkflow.rattish`. Do not create or edit workflow TOML.\n\nIf the assistant prompt provides an exact Raticode CLI path, use it instead of bare\n`Raticode`. Run `Raticode rattish docs --format json` to locate the installed Rattish specification\nand machine-readable node contracts. This command works in desktop and wheel installs and\ndoes not require a Raticode source checkout.\n\n## Authoring workflow\n\n1. Inspect registered workflows with `Raticode rattish list --format json`.\n2. For a new workflow, run:\n\n   ```bash\n   Raticode rattish create \"Workflow name\" --project \u003Cproject-folder> --format json\n   ```\n\n   Read `workflow.sourcePath` from the JSON response. Edit that `workflow.rattish` file.\n3. For an existing workflow, edit the `sourcePath` supplied in the assistant's workflow\n   context or returned by `Raticode rattish list --format json`.\n4. Consult only the documentation needed for the change:\n   - `README.md` for the language overview and CLI.\n   - `grammar.ebnf` and `lexical-spec.md` for source spelling.\n   - `static-semantics.md` for bindings, routes, inputs, and path rules.\n   - `node-contracts.md` for shared execution fields and node behavior.\n   - The installed `contracts\u002F` directory for the exact fields, defaults, and schemas of\n     each node type. Machine contracts and compiler diagnostics override prose examples.\n5. Validate every edit:\n\n   ```bash\n   Raticode rattish format \u003Cworkflow.rattish>\n   Raticode rattish check \u003Cworkflow.rattish> --format json\n   Raticode rattish preflight \u003Cworkflow.rattish> --format json\n   ```\n\n   Fix error diagnostics and re-run the failed command. Report warnings instead of hiding\n   them. Do not run the workflow unless the user authorizes real execution.\n\n## Rattish essentials\n\nA minimal workflow is:\n\n```rattish\nRattish: 1\n\nWorkflow:\n  name: Daily review\n\nNode collect:\n  type: bash-command\n  command: git status --short\n  to: review\n\nNode review:\n  type: agent\n  provider: codex\n  prompt: Review the repository status.\n  needs: collect\n```\n\nUse kebab-case node IDs and field names. `needs` declares readiness. `to` declares routes.\nUse `with` for typed input bindings, such as `report: node.collect.output.stdout`. Workflow\ninputs use `input.\u003Cname>`. Paths in Rattish are project-relative and cannot escape the\nproject root.\n\nUse a `loop` node for iteration or fan-out. Agent nodes do not own fan-out. Use\n`allow-fail: true` plus a conditional route when an operation failure should be handled by\nthe graph. Set explicit workflow or node limits for intentional cycles.\n\nProvider profiles and secrets are global Raticode configuration. Reference them from\nRattish, but never write resolved credentials into `workflow.rattish`, prompts, logs, or\ngenerated files.\n\n## Boundaries\n\n- Preserve the user's project and requested trigger behavior.\n- Reuse project scripts and prompts when suitable.\n- Do not edit compiled JSON IR. The compiler owns IR and stores it internally.\n- Do not use `Raticode workflow create`, `Raticode workflow add-node`, or other legacy TOML mutation\n  commands for Rattish workflows.\n- If the user requests a trigger or feature that Rattish 1 does not support, report that\n  limitation. Do not create a legacy TOML workflow as a workaround unless the user asks.\n- If the CLI or filesystem is unavailable, provide a Rattish patch and say which validation\n  commands could not run.\n","# Raticode workflow builder\n\nAuthor Raticode workflows as Rattish source. A registered workflow lives at\n`\u003Cproject>\u002F.raticode\u002F\u003Cworkflow-id>\u002Fworkflow.rattish`. Do not create or edit workflow TOML.\n\nIf the assistant prompt provides an exact Raticode CLI path, use it instead of bare\n`Raticode`. Run `Raticode rattish docs --format json` to locate the installed Rattish specification\nand machine-readable node contracts. This command works in desktop and wheel installs and\ndoes not require a Raticode source checkout.\n\n## Authoring workflow\n\n1. Inspect registered workflows with `Raticode rattish list --format json`.\n2. For a new workflow, run:\n\n   ```bash\n   Raticode rattish create \"Workflow name\" --project \u003Cproject-folder> --format json\n   ```\n\n   Read `workflow.sourcePath` from the JSON response. Edit that `workflow.rattish` file.\n3. For an existing workflow, edit the `sourcePath` supplied in the assistant's workflow\n   context or returned by `Raticode rattish list --format json`.\n4. Consult only the documentation needed for the change:\n   - `README.md` for the language overview and CLI.\n   - `grammar.ebnf` and `lexical-spec.md` for source spelling.\n   - `static-semantics.md` for bindings, routes, inputs, and path rules.\n   - `node-contracts.md` for shared execution fields and node behavior.\n   - The installed `contracts\u002F` directory for the exact fields, defaults, and schemas of\n     each node type. Machine contracts and compiler diagnostics override prose examples.\n5. Validate every edit:\n\n   ```bash\n   Raticode rattish format \u003Cworkflow.rattish>\n   Raticode rattish check \u003Cworkflow.rattish> --format json\n   Raticode rattish preflight \u003Cworkflow.rattish> --format json\n   ```\n\n   Fix error diagnostics and re-run the failed command. Report warnings instead of hiding\n   them. Do not run the workflow unless the user authorizes real execution.\n\n## Rattish essentials\n\nA minimal workflow is:\n\n```rattish\nRattish: 1\n\nWorkflow:\n  name: Daily review\n\nNode collect:\n  type: bash-command\n  command: git status --short\n  to: review\n\nNode review:\n  type: agent\n  provider: codex\n  prompt: Review the repository status.\n  needs: collect\n```\n\nUse kebab-case node IDs and field names. `needs` declares readiness. `to` declares routes.\nUse `with` for typed input bindings, such as `report: node.collect.output.stdout`. Workflow\ninputs use `input.\u003Cname>`. Paths in Rattish are project-relative and cannot escape the\nproject root.\n\nUse a `loop` node for iteration or fan-out. Agent nodes do not own fan-out. Use\n`allow-fail: true` plus a conditional route when an operation failure should be handled by\nthe graph. Set explicit workflow or node limits for intentional cycles.\n\nProvider profiles and secrets are global Raticode configuration. Reference them from\nRattish, but never write resolved credentials into `workflow.rattish`, prompts, logs, or\ngenerated files.\n\n## Boundaries\n\n- Preserve the user's project and requested trigger behavior.\n- Reuse project scripts and prompts when suitable.\n- Do not edit compiled JSON IR. The compiler owns IR and stores it internally.\n- Do not use `Raticode workflow create`, `Raticode workflow add-node`, or other legacy TOML mutation\n  commands for Rattish workflows.\n- If the user requests a trigger or feature that Rattish 1 does not support, report that\n  limitation. Do not create a legacy TOML workflow as a workaround unless the user asks.\n- If the CLI or filesystem is unavailable, provide a Rattish patch and say which validation\n  commands could not run.\n",{"name":5,"description":7},"main","46643b33fcaa8c36e39e8b1cdbb230efea4a06c3","skills\u002Fraticode-workflow-builder","https:\u002F\u002Fgithub.com\u002Fzacharyivie\u002FRaticode","https:\u002F\u002Fgithub.com\u002Fzacharyivie","2026-11-07 05:06:20",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add zacharyivie\u002FRaticode --skill raticode-workflow-builder",{"tool":61,"command":62},"bunx","bunx skills add zacharyivie\u002FRaticode --skill raticode-workflow-builder",{"tool":64,"command":65},"pnpm","pnpm dlx skills add zacharyivie\u002FRaticode --skill raticode-workflow-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzacharyivie\u002FRaticode\u002Fblob\u002Fmain\u002Fskills\u002Fraticode-workflow-builder\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"agents\u002Fopenai.yaml","REFERENCE","参考文档",194,"https:\u002F\u002Fgithub.com\u002Fzacharyivie\u002FRaticode\u002Fblob\u002Fmain\u002Fskills\u002Fraticode-workflow-builder\u002Fagents\u002Fopenai.yaml",[76],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M71PDQ6BFKED7BP8C103C3XS","review","Review software changes","https:\u002F\u002Fgithub.com\u002Fzacharyivie\u002FRaticode\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fagent-company\u002Fskills\u002Freview\u002FSKILL.md",[],[78,83,40],"software"]