@n8n-as-code/n8nac 2.0.0-next.58 → 2.0.0-next.60

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/n8n-architect/SKILL.md +2 -2
  3. package/skills/n8n-manager/SKILL.md +23 -23
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@n8n-as-code/n8nac",
3
- "version": "2.0.0-next.58",
3
+ "version": "2.0.0-next.60",
4
4
  "description": "OpenClaw plugin for n8n-as-code — create and manage n8n workflows from OpenClaw",
5
5
  "keywords": [
6
6
  "n8n",
package/skills/n8n-architect/SKILL.md CHANGED
@@ -30,7 +30,7 @@ npx --yes n8nac workspace status --json
30
30
  1. `cd` to the context root.
31
31
  2. Run `npx --yes n8nac update-ai`, then read `AGENTS.md`.
32
32
  3. Run `npx --yes n8nac workspace status --json`.
33
- 4. If the context root is not ready, inspect instances with `n8n-manager instances list`.
33
+ 4. If the context root is not ready, inspect instances with `npx --yes @n8n-as-code/n8n-manager instances list`.
34
34
  5. Reuse an existing instance when suitable.
35
35
  6. If no suitable instance exists, stop and ask the user whether they want to reuse/configure an existing instance, create a managed local n8n instance, or connect an existing/remote n8n instance. Do not create infrastructure by default. If the user chooses a managed local instance, ask separately whether they want a public tunnel.
36
36
  7. Ask for host/API key only for an explicitly remote or existing n8n instance.
@@ -285,7 +285,7 @@ Run it whenever one of these is true:
285
285
  - the user asks to show, open, present, display, or give the URL/link for a workflow.
286
286
 
287
287
  ```bash
288
- n8n-manager presentWorkflowResult --workflow-id <workflowId> --workspace-root <contextRoot>
288
+ npx --yes @n8n-as-code/n8n-manager presentWorkflowResult --workflow-id <workflowId> --workspace-root <contextRoot>
289
289
  ```
290
290
 
291
291
  Rules:
package/skills/n8n-manager/SKILL.md CHANGED
@@ -12,7 +12,7 @@ Use this skill for global n8n instance management. `n8n-manager` is the source o
12
12
  - Generated context root hint: not embedded. Use the shell launch directory or the workspace path explicitly given by the user.
13
13
  - If `n8nac` is available, first run `npx --yes n8nac update-ai` from the context root, then read `AGENTS.md`. `update-ai` is designed to create or refresh the n8n-as-code block without destroying existing user or agent instructions.
14
14
  - Use the exact `n8n-manager command` and `n8nac command` listed in `AGENTS.md` when present. Those context-root commands override the portable examples in this skill.
15
- - Use `n8n-manager` for global instance, auth, runtime, tunnel, project-default, credential, and workflow-presentation operations.
15
+ - Use `npx --yes @n8n-as-code/n8n-manager` for global instance, auth, runtime, tunnel, project-default, credential, and workflow-presentation operations.
16
16
  - Use `npx --yes n8nac workspace ...` only for context-root overrides such as pinned instance, sync folder, and project override.
17
17
  - Use `npx --yes n8nac` workflow commands only after the effective context is ready.
18
18
  - Never edit `n8nac-config.json`, `~/.n8n-manager`, or n8n-manager secret files by hand.
@@ -22,9 +22,9 @@ Use this skill for global n8n instance management. `n8n-manager` is the source o
22
22
  Inspect existing instances before changing state:
23
23
 
24
24
  ```bash
25
- n8n-manager instances list
26
- n8n-manager instances --help
27
- n8n-manager config get
25
+ npx --yes @n8n-as-code/n8n-manager instances list
26
+ npx --yes @n8n-as-code/n8n-manager instances --help
27
+ npx --yes @n8n-as-code/n8n-manager config get
28
28
  ```
29
29
 
30
30
  Do not invent n8n-manager subcommands. In particular, `instances create` and `--type local` are not valid. Use `instances add --mode ...` exactly as documented by `instances --help`.
@@ -53,33 +53,33 @@ Only run these commands after the user has explicitly chosen the corresponding o
53
53
  Managed local Docker without public tunnel:
54
54
 
55
55
  ```bash
56
- n8n-manager instances add --name <name> --mode managed-local-docker
57
- n8n-manager instances setup <id-or-name>
58
- n8n-manager instances start <id-or-name>
59
- n8n-manager instances status <id-or-name>
56
+ npx --yes @n8n-as-code/n8n-manager instances add --name <name> --mode managed-local-docker
57
+ npx --yes @n8n-as-code/n8n-manager instances setup <id-or-name>
58
+ npx --yes @n8n-as-code/n8n-manager instances start <id-or-name>
59
+ npx --yes @n8n-as-code/n8n-manager instances status <id-or-name>
60
60
  ```
61
61
 
62
62
  Managed local Docker with public tunnel:
63
63
 
64
64
  ```bash
65
- n8n-manager instances add --name <name> --mode managed-local-docker --tunnel
66
- n8n-manager instances setup <id-or-name> --tunnel
67
- n8n-manager instances start <id-or-name>
68
- n8n-manager instances tunnel status <id-or-name>
65
+ npx --yes @n8n-as-code/n8n-manager instances add --name <name> --mode managed-local-docker --tunnel
66
+ npx --yes @n8n-as-code/n8n-manager instances setup <id-or-name> --tunnel
67
+ npx --yes @n8n-as-code/n8n-manager instances start <id-or-name>
68
+ npx --yes @n8n-as-code/n8n-manager instances tunnel status <id-or-name>
69
69
  ```
70
70
 
71
71
  Remote or existing instances require user-provided credentials. Prefer stdin for API keys:
72
72
 
73
73
  ```bash
74
- n8n-manager auth set --url <url> --api-key-stdin --name <name>
75
- n8n-manager auth test --instance <id-or-name>
74
+ npx --yes @n8n-as-code/n8n-manager auth set --url <url> --api-key-stdin --name <name>
75
+ npx --yes @n8n-as-code/n8n-manager auth test --instance <id-or-name>
76
76
  ```
77
77
 
78
78
  Project selection is instance-level unless the context root explicitly needs a workspace override:
79
79
 
80
80
  ```bash
81
- n8n-manager projects list --instance <id-or-name>
82
- n8n-manager projects select <project-id-or-name> --instance <id-or-name>
81
+ npx --yes @n8n-as-code/n8n-manager projects list --instance <id-or-name>
82
+ npx --yes @n8n-as-code/n8n-manager projects select <project-id-or-name> --instance <id-or-name>
83
83
  ```
84
84
 
85
85
  Self-hosted n8n may not expose the projects API or may return 401/403. In that case, do not retry project discovery. Use the n8n-architect workspace override path with the standard personal project unless the user gave another project:
@@ -91,18 +91,18 @@ npx --yes n8nac workspace set-project --project-id personal --project-name Perso
91
91
  Runtime and tunnel operations are per instance:
92
92
 
93
93
  ```bash
94
- n8n-manager instances start <id-or-name>
95
- n8n-manager instances stop <id-or-name>
96
- n8n-manager instances restart <id-or-name>
97
- n8n-manager instances tunnel status <id-or-name>
98
- n8n-manager instances tunnel start <id-or-name>
99
- n8n-manager instances tunnel refresh <id-or-name>
94
+ npx --yes @n8n-as-code/n8n-manager instances start <id-or-name>
95
+ npx --yes @n8n-as-code/n8n-manager instances stop <id-or-name>
96
+ npx --yes @n8n-as-code/n8n-manager instances restart <id-or-name>
97
+ npx --yes @n8n-as-code/n8n-manager instances tunnel status <id-or-name>
98
+ npx --yes @n8n-as-code/n8n-manager instances tunnel start <id-or-name>
99
+ npx --yes @n8n-as-code/n8n-manager instances tunnel refresh <id-or-name>
100
100
  ```
101
101
 
102
102
  Present workflow results after creating, modifying, pushing, or running a workflow:
103
103
 
104
104
  ```bash
105
- n8n-manager presentWorkflowResult --workflow-id <workflowId> --workspace-root <contextRoot>
105
+ npx --yes @n8n-as-code/n8n-manager presentWorkflowResult --workflow-id <workflowId> --workspace-root <contextRoot>
106
106
  ```
107
107
 
108
108
  ## Guardrails