CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly structured, highly actionable instruction-only skill that sequences a one-off workflow with explicit read-back validation and honest verification guidance. The main gaps are minor over-justification prose and the absence of an explicit error-recovery feedback loop.

Suggestions

Trim the rationale paragraphs in steps 1 and 3 to the bare instruction to improve conciseness.

Add a short validate→fix→retry loop for the optional pre-flight verification (e.g., on simulated-failure findings, fix wiring and re-run verify-built-workflow).

Make the cross-skill reference an explicit link (e.g., "see post-build-flow > Cleaning up after a live test") for cleaner navigation.

DimensionReasoningScore

Conciseness

Dense and free of basic-concept padding, but several passages justify rules at length (e.g., why the live-run consent gate is already satisfied) that could be trimmed without losing the instruction.

4 / 5

Actionability

Gives concrete, executable tool invocations with parameters throughout (build-workflow with executionIntent: "one-off", workflows(action="setup"), executions(action="run"), executions(action="get-node-output")), fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

A clear five-step sequence with an explicit read-back validation checkpoint (step 4) and setup gating, but it lacks a validate→fix→retry feedback loop, capping it just below the top anchor.

4 / 5

Progressive Disclosure

Well-organized into clear sections with a single well-signaled one-level reference ("Cleaning up after a live test" in post-build-flow); content is appropriately self-contained with no bundle to split, leaving only minor navigation polish.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A precise, third-person description that explicitly covers both what the skill does and when to load it, with strong distinctiveness via a negative boundary against reusable automations. Slightly abstract effect phrasing and modest synonym coverage keep trigger/specificity just below the top anchor.

Suggestions

Tighten "export or copy data somewhere" into more concrete destinations (e.g., "export rows to a spreadsheet, copy records between nodes") to lift specificity.

Add a couple of natural user phrasings (e.g., "move this data", "do this just once") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete effect types ("export or copy data somewhere, a migration, a backfill, a cleanup"), giving multi-action coverage with only minor abstraction ("somewhere").

4 / 5

Completeness

Clearly states what ("concrete effect that happens once") and an explicit when with concrete trigger phrases ("Load before building for such a request, or when a build-workflow result contains postBuildFlow.reason 'direct-one-off-build-succeeded'") plus a negative boundary.

5 / 5

Trigger Term Quality

Good natural keyword coverage (export, copy, migration, backfill, cleanup, one-off) plus an explicit load trigger, though a few synonymous phrasings users might say are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (no trigger/schedule/reuse intent) with distinct triggers and an explicit exclusion ("Do not load for automations the user will run again"), minimizing conflict with the reusable-build path.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
n8n-io/n8n
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.