Agent skill · n8n-io
one-off-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.
What it needs
About 4k tokens when loaded.
What this skill does
One-Off Operations Use this skill when the request is a one-off operation: a concrete effect that needs to happen once, where a workflow is only the vehicle to make it happen. Typical shapes: "put this data in a spreadsheet", "copy these rows to X", "migrate/backfill/clean up Y". These instructions are in English, but user-visible text you write while following them stays in the user's conversation language. Recognizing a one-off Users rarely label a task "one-off" — infer it from the task's shape, not from explicit phrasing. It is a one-off when the deliverable is a state change, not an automation: The user asks for an effect on data that already exists and is bounded — pasted into the chat, sitting in a named node, table, file, or sheet — rather than data that will keep arriving over time. The request is imperative about the here-and-now ("add these rows", "export what's in X", "clean out the duplicates"), with no trigger, schedule, or event vocabulary — no "when", "every", "whenever", "daily", "each time". Nothing suggests the user wants to keep and rerun the workflow; the workflow is never mentioned as the thing they want, only the outcome is. Explicit markers ("just this once", "I won't need this again") confirm the classification but are not required — most one-offs arrive without them. Signals against: trigger/schedule vocabulary, "from now on", a named event source, or any hint the user wants the automation itself. When in doubt, treat the request as reusable and follow the normal build flow — a reusable workflow that runs once is harmless; a one-off flow applied to an automation skips verification the user would have wanted. A one-off that touches external systems is still workflow-anchored (you cannot write to external services directly) — the intent changes the post-build flow, not the anchor. The one-off flow 1. Build the workflow with a manual trigger — always. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/one-off-operations