[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-n8n-one-off-operations":3,"mdc--r0v3ea-key":51,"related-org-n8n-one-off-operations":340,"related-repo-n8n-one-off-operations":497},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":46,"sourceUrl":49,"mdContent":50},"one-off-operations","execute one-off n8n operations","Handles one-off operations: the request is a concrete effect that happens once — export or copy data somewhere, a migration, a backfill, a cleanup — with no trigger, schedule, or reuse intent. The workflow is the vehicle, not the deliverable. Users rarely say \"one-off\"; infer it from the task's shape. Load before building for such a request, or when a build-workflow result contains postBuildFlow.reason \"direct-one-off-build-succeeded\". Do not load for automations the user will run again — that is the normal build + post-build-flow path.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},"n8n","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fn8n.png","n8n-io",[12,14,17,20],{"name":8,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Operations","operations",{"name":18,"slug":19,"type":13},"Automation","automation",{"name":21,"slug":22,"type":13},"Workflow Automation","workflow-automation",198156,"https:\u002F\u002Fgithub.com\u002Fn8n-io\u002Fn8n","2026-08-15T03:47:40.122664",null,59655,[29,30,19,31,32,33,34,35,36,37,38,39,40,41,8,42,43,44,45,22],"ai","apis","cli","data-flow","development","integration-framework","integrations","ipaas","low-code","low-code-platform","mcp","mcp-client","mcp-server","no-code","self-hosted","typescript","workflow",{"repoUrl":24,"stars":23,"forks":27,"topics":47,"description":48},[29,30,19,31,32,33,34,35,36,37,38,39,40,41,8,42,43,44,45,22],"Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.","https:\u002F\u002Fgithub.com\u002Fn8n-io\u002Fn8n\u002Ftree\u002FHEAD\u002Fpackages\u002F@n8n\u002Finstance-ai\u002Fskills\u002Fone-off-operations","---\nname: one-off-operations\ndescription: >-\n  Handles one-off operations: the request is a concrete effect that happens\n  once — export or copy data somewhere, a migration, a backfill, a cleanup —\n  with no trigger, schedule, or reuse intent. The workflow is the vehicle, not\n  the deliverable. Users rarely say \"one-off\"; infer it from the task's shape.\n  Load before building for such a request, or when a build-workflow result\n  contains postBuildFlow.reason \"direct-one-off-build-succeeded\". Do not load\n  for automations the user will run again — that is the normal build +\n  post-build-flow path.\nrecommended_tools:\n  - build-workflow\n  - workflows\n  - executions\n  - ask-user\n  - verify-built-workflow\n---\n\n# One-Off Operations\n\nUse this skill when the request is a **one-off operation**: a concrete effect\nthat needs to happen once, where a workflow is only the vehicle to make it\nhappen. Typical shapes: \"put this data in a spreadsheet\", \"copy these rows to\nX\", \"migrate\u002Fbackfill\u002Fclean up Y\".\n\nThese instructions are in English, but user-visible text you write while\nfollowing them stays in the user's conversation language.\n\n## Recognizing a one-off\n\nUsers rarely label a task \"one-off\" — **infer it from the task's shape**, not\nfrom explicit phrasing. It is a one-off when the deliverable is a *state\nchange*, not an automation:\n\n- The user asks for an effect on data that **already exists and is bounded** —\n  pasted into the chat, sitting in a named node, table, file, or sheet — rather\n  than data that will keep arriving over time.\n- The request is imperative about the here-and-now (\"add these rows\", \"export\n  what's in X\", \"clean out the duplicates\"), with no trigger, schedule, or\n  event vocabulary — no \"when\", \"every\", \"whenever\", \"daily\", \"each time\".\n- Nothing suggests the user wants to keep and rerun the workflow; the workflow\n  is never mentioned as the thing they want, only the outcome is.\n\nExplicit markers (\"just this once\", \"I won't need this again\") confirm the\nclassification but are not required — most one-offs arrive without them.\nSignals against: trigger\u002Fschedule vocabulary, \"from now on\", a named event\nsource, or any hint the user wants the automation itself. **When in doubt,\ntreat the request as reusable** and follow the normal build flow — a reusable\nworkflow that runs once is harmless; a one-off flow applied to an automation\nskips verification the user would have wanted.\n\nA one-off that touches external systems is still workflow-anchored (you cannot\nwrite to external services directly) — the intent changes the *post-build\nflow*, not the anchor.\n\n## The one-off flow\n\n1. **Build** the workflow with a **manual trigger** — always. A one-off is\n   never published, so an event trigger (webhook, form, schedule) would never\n   fire and only misleads. If the task genuinely needs an event source or a\n   future run time, it is not a one-off — reclassify it as a reusable\n   automation or a scheduled task and use the normal flow. Pass\n   `executionIntent: \"one-off\"` to `build-workflow`. This marks verification\n   as optional in the build outcome — no verification follow-up is scheduled,\n   and the completion criterion becomes a live run whose output you read back.\n2. **Setup** is unchanged: if the build outcome requires credential or value\n   setup, route it through `workflows(action=\"setup\")` as usual. A one-off\n   still needs real credentials before it can run live.\n3. **Run live** with `executions(action=\"run\")`. The run-approval card is the\n   user's consent gate — for a one-off, the live run IS what the user asked\n   for, so the usual \"reserve live runs for explicit user requests\" rule is\n   satisfied by the request itself. Do not run before setup is complete.\n4. **Read back before reporting.** After the run, inspect the actual output of\n   the effect nodes with `executions(action=\"get-node-output\")` — the run\n   result data is truncated and not enough for quantitative claims. Check that\n   each write\u002Feffect node's input was the intended data (the rows you meant to\n   write), not an upstream node's API response. Report only numbers, columns,\n   and shapes you actually read. If the target system is cheap to read (e.g. a\n   read operation of the same node type), offer a read-back of the destination\n   as final confirmation.\n5. **Offer cleanup.** When the operation succeeded, ask whether to keep the\n   workflow for future reuse or delete it now that the job is done. Never\n   delete without asking. If the user keeps it, mention it stays unpublished\n   unless they say otherwise.\n\n## Optional pre-flight verification\n\n`verify-built-workflow` is available but **not required and never the\ncompletion criterion** for a one-off. Offer it before the live run only when\nthe wiring is complex (branching, merges, non-trivial transformations) or the\nuser is cautious about touching real data.\n\nWhen you do run it, present results honestly:\n\n- Say which nodes were **simulated** — external writes did not happen, and the\n  data flowing into simulated write nodes was NOT validated (their output is a\n  fabricated success fixture).\n- Never call the workflow \"verified\", \"tested\", or \"working\" from a simulated\n  pass alone, and never let it substitute for the live run and read-back.\n\n## Claiming success\n\nDo not make quantitative claims (\"22 rows written\", \"columns matched\") that\nyou did not read back from actual execution output or the target system. A\nsuccessful run status alone does not prove the *right data* was written — read\nthe effect node's real output first. If you could not read it back, say so\nplainly and name what is unconfirmed.\n",{"data":52,"body":59},{"name":4,"description":6,"recommended_tools":53},[54,55,56,57,58],"build-workflow","workflows","executions","ask-user","verify-built-workflow",{"type":60,"children":61},"root",[62,70,84,89,96,116,143,155,167,173,274,280,297,302,322,328],{"type":63,"tag":64,"props":65,"children":66},"element","h1",{"id":4},[67],{"type":68,"value":69},"text","One-Off Operations",{"type":63,"tag":71,"props":72,"children":73},"p",{},[74,76,82],{"type":68,"value":75},"Use this skill when the request is a ",{"type":63,"tag":77,"props":78,"children":79},"strong",{},[80],{"type":68,"value":81},"one-off operation",{"type":68,"value":83},": a concrete effect\nthat needs to happen once, where a workflow is only the vehicle to make it\nhappen. Typical shapes: \"put this data in a spreadsheet\", \"copy these rows to\nX\", \"migrate\u002Fbackfill\u002Fclean up Y\".",{"type":63,"tag":71,"props":85,"children":86},{},[87],{"type":68,"value":88},"These instructions are in English, but user-visible text you write while\nfollowing them stays in the user's conversation language.",{"type":63,"tag":90,"props":91,"children":93},"h2",{"id":92},"recognizing-a-one-off",[94],{"type":68,"value":95},"Recognizing a one-off",{"type":63,"tag":71,"props":97,"children":98},{},[99,101,106,108,114],{"type":68,"value":100},"Users rarely label a task \"one-off\" — ",{"type":63,"tag":77,"props":102,"children":103},{},[104],{"type":68,"value":105},"infer it from the task's shape",{"type":68,"value":107},", not\nfrom explicit phrasing. It is a one-off when the deliverable is a ",{"type":63,"tag":109,"props":110,"children":111},"em",{},[112],{"type":68,"value":113},"state\nchange",{"type":68,"value":115},", not an automation:",{"type":63,"tag":117,"props":118,"children":119},"ul",{},[120,133,138],{"type":63,"tag":121,"props":122,"children":123},"li",{},[124,126,131],{"type":68,"value":125},"The user asks for an effect on data that ",{"type":63,"tag":77,"props":127,"children":128},{},[129],{"type":68,"value":130},"already exists and is bounded",{"type":68,"value":132}," —\npasted into the chat, sitting in a named node, table, file, or sheet — rather\nthan data that will keep arriving over time.",{"type":63,"tag":121,"props":134,"children":135},{},[136],{"type":68,"value":137},"The request is imperative about the here-and-now (\"add these rows\", \"export\nwhat's in X\", \"clean out the duplicates\"), with no trigger, schedule, or\nevent vocabulary — no \"when\", \"every\", \"whenever\", \"daily\", \"each time\".",{"type":63,"tag":121,"props":139,"children":140},{},[141],{"type":68,"value":142},"Nothing suggests the user wants to keep and rerun the workflow; the workflow\nis never mentioned as the thing they want, only the outcome is.",{"type":63,"tag":71,"props":144,"children":145},{},[146,148,153],{"type":68,"value":147},"Explicit markers (\"just this once\", \"I won't need this again\") confirm the\nclassification but are not required — most one-offs arrive without them.\nSignals against: trigger\u002Fschedule vocabulary, \"from now on\", a named event\nsource, or any hint the user wants the automation itself. ",{"type":63,"tag":77,"props":149,"children":150},{},[151],{"type":68,"value":152},"When in doubt,\ntreat the request as reusable",{"type":68,"value":154}," and follow the normal build flow — a reusable\nworkflow that runs once is harmless; a one-off flow applied to an automation\nskips verification the user would have wanted.",{"type":63,"tag":71,"props":156,"children":157},{},[158,160,165],{"type":68,"value":159},"A one-off that touches external systems is still workflow-anchored (you cannot\nwrite to external services directly) — the intent changes the ",{"type":63,"tag":109,"props":161,"children":162},{},[163],{"type":68,"value":164},"post-build\nflow",{"type":68,"value":166},", not the anchor.",{"type":63,"tag":90,"props":168,"children":170},{"id":169},"the-one-off-flow",[171],{"type":68,"value":172},"The one-off flow",{"type":63,"tag":174,"props":175,"children":176},"ol",{},[177,210,228,246,264],{"type":63,"tag":121,"props":178,"children":179},{},[180,185,187,192,194,201,203,208],{"type":63,"tag":77,"props":181,"children":182},{},[183],{"type":68,"value":184},"Build",{"type":68,"value":186}," the workflow with a ",{"type":63,"tag":77,"props":188,"children":189},{},[190],{"type":68,"value":191},"manual trigger",{"type":68,"value":193}," — always. A one-off is\nnever published, so an event trigger (webhook, form, schedule) would never\nfire and only misleads. If the task genuinely needs an event source or a\nfuture run time, it is not a one-off — reclassify it as a reusable\nautomation or a scheduled task and use the normal flow. Pass\n",{"type":63,"tag":195,"props":196,"children":198},"code",{"className":197},[],[199],{"type":68,"value":200},"executionIntent: \"one-off\"",{"type":68,"value":202}," to ",{"type":63,"tag":195,"props":204,"children":206},{"className":205},[],[207],{"type":68,"value":54},{"type":68,"value":209},". This marks verification\nas optional in the build outcome — no verification follow-up is scheduled,\nand the completion criterion becomes a live run whose output you read back.",{"type":63,"tag":121,"props":211,"children":212},{},[213,218,220,226],{"type":63,"tag":77,"props":214,"children":215},{},[216],{"type":68,"value":217},"Setup",{"type":68,"value":219}," is unchanged: if the build outcome requires credential or value\nsetup, route it through ",{"type":63,"tag":195,"props":221,"children":223},{"className":222},[],[224],{"type":68,"value":225},"workflows(action=\"setup\")",{"type":68,"value":227}," as usual. A one-off\nstill needs real credentials before it can run live.",{"type":63,"tag":121,"props":229,"children":230},{},[231,236,238,244],{"type":63,"tag":77,"props":232,"children":233},{},[234],{"type":68,"value":235},"Run live",{"type":68,"value":237}," with ",{"type":63,"tag":195,"props":239,"children":241},{"className":240},[],[242],{"type":68,"value":243},"executions(action=\"run\")",{"type":68,"value":245},". The run-approval card is the\nuser's consent gate — for a one-off, the live run IS what the user asked\nfor, so the usual \"reserve live runs for explicit user requests\" rule is\nsatisfied by the request itself. Do not run before setup is complete.",{"type":63,"tag":121,"props":247,"children":248},{},[249,254,256,262],{"type":63,"tag":77,"props":250,"children":251},{},[252],{"type":68,"value":253},"Read back before reporting.",{"type":68,"value":255}," After the run, inspect the actual output of\nthe effect nodes with ",{"type":63,"tag":195,"props":257,"children":259},{"className":258},[],[260],{"type":68,"value":261},"executions(action=\"get-node-output\")",{"type":68,"value":263}," — the run\nresult data is truncated and not enough for quantitative claims. Check that\neach write\u002Feffect node's input was the intended data (the rows you meant to\nwrite), not an upstream node's API response. Report only numbers, columns,\nand shapes you actually read. If the target system is cheap to read (e.g. a\nread operation of the same node type), offer a read-back of the destination\nas final confirmation.",{"type":63,"tag":121,"props":265,"children":266},{},[267,272],{"type":63,"tag":77,"props":268,"children":269},{},[270],{"type":68,"value":271},"Offer cleanup.",{"type":68,"value":273}," When the operation succeeded, ask whether to keep the\nworkflow for future reuse or delete it now that the job is done. Never\ndelete without asking. If the user keeps it, mention it stays unpublished\nunless they say otherwise.",{"type":63,"tag":90,"props":275,"children":277},{"id":276},"optional-pre-flight-verification",[278],{"type":68,"value":279},"Optional pre-flight verification",{"type":63,"tag":71,"props":281,"children":282},{},[283,288,290,295],{"type":63,"tag":195,"props":284,"children":286},{"className":285},[],[287],{"type":68,"value":58},{"type":68,"value":289}," is available but ",{"type":63,"tag":77,"props":291,"children":292},{},[293],{"type":68,"value":294},"not required and never the\ncompletion criterion",{"type":68,"value":296}," for a one-off. Offer it before the live run only when\nthe wiring is complex (branching, merges, non-trivial transformations) or the\nuser is cautious about touching real data.",{"type":63,"tag":71,"props":298,"children":299},{},[300],{"type":68,"value":301},"When you do run it, present results honestly:",{"type":63,"tag":117,"props":303,"children":304},{},[305,317],{"type":63,"tag":121,"props":306,"children":307},{},[308,310,315],{"type":68,"value":309},"Say which nodes were ",{"type":63,"tag":77,"props":311,"children":312},{},[313],{"type":68,"value":314},"simulated",{"type":68,"value":316}," — external writes did not happen, and the\ndata flowing into simulated write nodes was NOT validated (their output is a\nfabricated success fixture).",{"type":63,"tag":121,"props":318,"children":319},{},[320],{"type":68,"value":321},"Never call the workflow \"verified\", \"tested\", or \"working\" from a simulated\npass alone, and never let it substitute for the live run and read-back.",{"type":63,"tag":90,"props":323,"children":325},{"id":324},"claiming-success",[326],{"type":68,"value":327},"Claiming success",{"type":63,"tag":71,"props":329,"children":330},{},[331,333,338],{"type":68,"value":332},"Do not make quantitative claims (\"22 rows written\", \"columns matched\") that\nyou did not read back from actual execution output or the target system. A\nsuccessful run status alone does not prove the ",{"type":63,"tag":109,"props":334,"children":335},{},[336],{"type":68,"value":337},"right data",{"type":68,"value":339}," was written — read\nthe effect node's real output first. If you could not read it back, say so\nplainly and name what is unconfirmed.",{"items":341,"total":496},[342,357,374,389,403,416,429,441,458,465,474,486],{"slug":343,"name":343,"fn":344,"description":345,"org":346,"tags":347,"stars":23,"repoUrl":24,"updatedAt":356},"config-evals","configure workflow evaluations","Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it does not touch on-canvas evaluation nodes.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[348,351,352,355],{"name":349,"slug":350,"type":13},"Evals","evals",{"name":8,"slug":8,"type":13},{"name":353,"slug":354,"type":13},"Testing","testing",{"name":21,"slug":22,"type":13},"2026-07-24T05:37:07.398695",{"slug":358,"name":358,"fn":359,"description":360,"org":361,"tags":362,"stars":23,"repoUrl":24,"updatedAt":373},"credential-recipe-research","research custom authentication recipe fields","Lookup procedure for Simplified Custom Auth recipe fields — sources the auth template, the key-issuing docsUrl and an auth-rejecting testUrl from the provider's real documentation instead of memory. Load before composing credentialHints for a service without a dedicated credential type (the post-build-flow setup step), or when asked to fix a recipe whose template, key page or test endpoint is wrong.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[363,366,369,370],{"name":364,"slug":365,"type":13},"API Development","api-development",{"name":367,"slug":368,"type":13},"Auth","auth",{"name":8,"slug":8,"type":13},{"name":371,"slug":372,"type":13},"Research","research","2026-08-09T04:33:26.609278",{"slug":375,"name":375,"fn":376,"description":377,"org":378,"tags":379,"stars":23,"repoUrl":24,"updatedAt":388},"credential-setup-with-computer-use","configure n8n credentials via browser","Guides n8n credential setup through Computer Use browser tools. Use when a user needs OAuth apps, API keys, client IDs, client secrets, or other credential values from an external service console.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[380,381,384,385],{"name":18,"slug":19,"type":13},{"name":382,"slug":383,"type":13},"Configuration","configuration",{"name":8,"slug":8,"type":13},{"name":386,"slug":387,"type":13},"OAuth","oauth","2026-06-30T07:40:45.54",{"slug":390,"name":390,"fn":391,"description":392,"org":393,"tags":394,"stars":23,"repoUrl":24,"updatedAt":402},"data-table-manager","manage n8n Data Tables","Load before calling data-tables or parse-file. Use for natural standalone requests like \"what data tables do I have?\", \"show\u002Flist my tables\", or \"what columns are in this table?\", and whenever the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables and rows, especially from CSV\u002FXLSX\u002FJSON attachments. Also load before building or planning workflows that create or write to Data Tables (then load workflow-builder before build-workflow).",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[395,398,401],{"name":396,"slug":397,"type":13},"Data Engineering","data-engineering",{"name":399,"slug":400,"type":13},"Database","database",{"name":8,"slug":8,"type":13},"2026-07-27T06:07:14.648144",{"slug":404,"name":404,"fn":405,"description":406,"org":407,"tags":408,"stars":23,"repoUrl":24,"updatedAt":415},"debugging-executions","debug failed n8n workflow executions","Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[409,410,413,414],{"name":18,"slug":19,"type":13},{"name":411,"slug":412,"type":13},"Debugging","debugging",{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},"2026-08-09T04:05:08.011605",{"slug":417,"name":417,"fn":418,"description":419,"org":420,"tags":421,"stars":23,"repoUrl":24,"updatedAt":428},"intent-recognition","classify automation requests by control flow","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.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[422,425,426,427],{"name":423,"slug":424,"type":13},"Agents","agents",{"name":18,"slug":19,"type":13},{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},"2026-08-15T03:22:45.378353",{"slug":430,"name":430,"fn":431,"description":432,"org":433,"tags":434,"stars":23,"repoUrl":24,"updatedAt":440},"n8n-cli","manage n8n workflows from the CLI","Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[435,436,438,439],{"name":18,"slug":19,"type":13},{"name":437,"slug":31,"type":13},"CLI",{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},"2026-04-06T18:38:40.360123",{"slug":442,"name":442,"fn":443,"description":444,"org":445,"tags":446,"stars":23,"repoUrl":24,"updatedAt":457},"n8n-docs-assistant","retrieve n8n documentation and guidance","Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Load n8n-docs via load_tool before calling it (search \"n8n docs\" if not visible). Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions opened from the credential modal.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[447,450,451,454],{"name":448,"slug":449,"type":13},"Documentation","documentation",{"name":8,"slug":8,"type":13},{"name":452,"slug":453,"type":13},"Reference","reference",{"name":455,"slug":456,"type":13},"Search","search","2026-07-27T06:07:15.692906",{"slug":4,"name":4,"fn":5,"description":6,"org":459,"tags":460,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[461,462,463,464],{"name":18,"slug":19,"type":13},{"name":8,"slug":8,"type":13},{"name":15,"slug":16,"type":13},{"name":21,"slug":22,"type":13},{"slug":466,"name":466,"fn":467,"description":468,"org":469,"tags":470,"stars":23,"repoUrl":24,"updatedAt":388},"planned-task-runtime","manage n8n task runtimes","Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[471,472,473],{"name":18,"slug":19,"type":13},{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},{"slug":475,"name":475,"fn":476,"description":477,"org":478,"tags":479,"stars":23,"repoUrl":24,"updatedAt":485},"planning","coordinate multi-artifact workflows","ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema\u002Fmigration across tasks, or the user explicitly asked to review a plan first. Load create-tasks via load_tool before calling it (search \"create tasks\" if not visible). Do NOT use for new one-off workflows, single-workflow edits, verification-only requests, or standalone data-table ops — use workflow-builder or data-table-manager instead.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[480,481,482,484],{"name":18,"slug":19,"type":13},{"name":8,"slug":8,"type":13},{"name":483,"slug":475,"type":13},"Planning",{"name":21,"slug":22,"type":13},"2026-08-09T04:05:09.986112",{"slug":487,"name":487,"fn":488,"description":489,"org":490,"tags":491,"stars":23,"repoUrl":24,"updatedAt":495},"post-build-flow","verify and set up n8n workflows","Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify\u002Fsetup follow-up turns.",{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[492,493,494],{"name":18,"slug":19,"type":13},{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},"2026-08-15T03:22:44.410727",27,{"items":498,"total":547},[499,506,513,520,526,533,540],{"slug":343,"name":343,"fn":344,"description":345,"org":500,"tags":501,"stars":23,"repoUrl":24,"updatedAt":356},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[502,503,504,505],{"name":349,"slug":350,"type":13},{"name":8,"slug":8,"type":13},{"name":353,"slug":354,"type":13},{"name":21,"slug":22,"type":13},{"slug":358,"name":358,"fn":359,"description":360,"org":507,"tags":508,"stars":23,"repoUrl":24,"updatedAt":373},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[509,510,511,512],{"name":364,"slug":365,"type":13},{"name":367,"slug":368,"type":13},{"name":8,"slug":8,"type":13},{"name":371,"slug":372,"type":13},{"slug":375,"name":375,"fn":376,"description":377,"org":514,"tags":515,"stars":23,"repoUrl":24,"updatedAt":388},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[516,517,518,519],{"name":18,"slug":19,"type":13},{"name":382,"slug":383,"type":13},{"name":8,"slug":8,"type":13},{"name":386,"slug":387,"type":13},{"slug":390,"name":390,"fn":391,"description":392,"org":521,"tags":522,"stars":23,"repoUrl":24,"updatedAt":402},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[523,524,525],{"name":396,"slug":397,"type":13},{"name":399,"slug":400,"type":13},{"name":8,"slug":8,"type":13},{"slug":404,"name":404,"fn":405,"description":406,"org":527,"tags":528,"stars":23,"repoUrl":24,"updatedAt":415},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[529,530,531,532],{"name":18,"slug":19,"type":13},{"name":411,"slug":412,"type":13},{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},{"slug":417,"name":417,"fn":418,"description":419,"org":534,"tags":535,"stars":23,"repoUrl":24,"updatedAt":428},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[536,537,538,539],{"name":423,"slug":424,"type":13},{"name":18,"slug":19,"type":13},{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},{"slug":430,"name":430,"fn":431,"description":432,"org":541,"tags":542,"stars":23,"repoUrl":24,"updatedAt":440},{"slug":8,"name":8,"logoUrl":9,"githubOrg":10},[543,544,545,546],{"name":18,"slug":19,"type":13},{"name":437,"slug":31,"type":13},{"name":8,"slug":8,"type":13},{"name":21,"slug":22,"type":13},13]