agentleFS
Sign inStart free
neurawork-gitneurawork-git/n8n-autopilot/skills/test-manual/SKILL.md

test-manual

Skill18 starsChanged 43 days agoMITView on GitHub

Hand-driven UI test of a workflow — only when the native n8n MCP test path (docs/rules/testing.md) is not registered. Resolves the UI URL, waits for you to run it and report the execution-id, then inspects the run. Resolves the n8n UI URL, waits for you to run it and report the execution-id, then inspects the run. Read-only against the instance.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use $ARGUMENTS as the workflow id.

    line 27
  2. Very specific:

    If triggerType is webhook / chat / form (i.e.

    line 36
  3. Very specific:

    If schedule / manual / errorTrigger → continue.

    line 38
  4. Very specific:

    Stop and wait for the user to report the execution-id.

    line 58
  5. Very specific:

    Read the output and report: success/failure, which node failed (if any), and the relevant output/error data.

    line 66
  6. Distinctive:

    Read-only against the instance — this skill only resolves URLs and reads execution data.

    line 71
  7. Distinctive:

    If the user reports no execution-id (the run did not start), re-check the URL and that the user clicked "Execute Workflow" (not "Save").

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test a Non-HTTP-Trigger Workflow

Since 5.4.0 this is not the default. Every trigger type is tested headless through the native n8n MCP (pinned test_workflow, or live execute_workflow) — see docs/rules/testing.md. Use this skill only when the n8n-native MCP server is not registered, or to watch a run in the UI.

npx n8nac test can only fire webhook / chat / form triggers. For schedule, manual, and errorTrigger workflows the run must be started in the n8n UI. This skill packages that detour into one flow so you do not have to hand-assemble the URL and the execution get command each time.

Why this exists: non-HTTP manual-test detours were the single most frequent friction observed in real production runs.

Steps

1. Resolve the workflow id

Use $ARGUMENTS as the workflow id. If empty, ask the user (or extract it from the .workflow.ts they name: grep -oE "id:[[:space:]]*['\"][A-Za-z0-9]{10,}['\"]" <file> | head -1).

2. Confirm it really is a non-HTTP trigger

npx n8nac test-plan <workflowId> --json
  • If triggerType is webhook / chat / form (i.e. testable: true) → STOP and tell the user to use npx n8nac test <workflowId> (or /n8n-autopilot:deploy) instead — no manual step needed.
  • If schedule / manual / errorTrigger → continue.

3. Resolve the UI URL (never string-concat the host)

npx n8nac workflow present <workflowId> --json

Surface a clear instruction to the user with the URL from the output:

▶  MANUAL EXECUTION REQUIRED — <triggerType> trigger (n8nac cannot fire it)

Open n8n UI:  <url from `n8nac workflow present`>
Click:        "Execute Workflow"
Then paste the execution-id here (top of the execution, or from the URL).

4. Wait for the execution-id

Stop and wait for the user to report the execution-id. Do not fabricate one.

5. Inspect the run

npx n8nac execution get <executionId> --include-data

Read the output and report: success/failure, which node failed (if any), and the relevant output/error data. If it failed on a wiring error, hand back to /n8n-autopilot:deploy's fix loop.

Notes

  • Read-only against the instance — this skill only resolves URLs and reads execution data. The actual run is started by the user in the UI.
  • If the user reports no execution-id (the run did not start), re-check the URL and that the user clicked "Execute Workflow" (not "Save").

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free