openclaw-workflowskill 0.3.2 → 0.3.4

package/README.md

@@ -26,7 +26,11 @@ Requires [OpenClaw](https://openclaw.ai).
 
 ### 1. Set your profile to Coding
 
-In OpenClaw settings, change your profile from `messaging` (the default) to `coding`. The `coding` profile grants the agent filesystem access, which is required to read and write workflow files. For more granular access configuration, refer to the [OpenClaw documentation](https://docs.openclaw.ai/).
+```bash
+openclaw config set tools.profile coding
+```
+
+The `coding` profile grants the agent filesystem access, which is required to read and write workflow files. For more granular access configuration, refer to the [OpenClaw documentation](https://docs.openclaw.ai/).
 
 ### 2. Install the plugin
 
@@ -34,13 +38,24 @@ In OpenClaw settings, change your profile from `messaging` (the default) to `cod
 openclaw plugins install openclaw-workflowskill
 ```
 
-### 3. Restart the gateway
+### 3. Configure
+
+```bash
+openclaw config set plugins.allow '["openclaw-workflowskill"]'
+openclaw config set tools.alsoAllow '["openclaw-workflowskill"]'
+```
+
+The first command allowlists the plugin so the gateway loads it. The second makes its tools available in every session — including cron jobs — so agents can invoke `workflowskill_run` to execute workflows autonomously.
+
+### 4. Restart the gateway
 
 ```bash
 openclaw gateway restart
 ```
 
-### 4. Verify
+The gateway loads plugins and config at startup. A restart is required to pick up the plugin installation and config changes from the previous steps.
+
+### 5. Verify
 
 ```bash
 openclaw plugins list
@@ -52,7 +67,7 @@ openclaw skills list
 
 > **Note:** `workflowskill_llm` uses your Anthropic credentials from the main agent — no separate API key configuration needed.
 
-### 5. Create a workflow
+### 6. Create a workflow
 
 Just tell the agent what you want to automate:
 
@@ -64,7 +79,7 @@ Just tell the agent what you want to automate:
 >
 > Run complete: 4 AI stories found, summary drafted. Ready to schedule — want me to set up a daily cron at 8 AM?
 
-### 6. Schedule it
+### 7. Schedule it
 
 Ask the agent to set up a cron job, or add one manually at `~/.openclaw/cron/jobs.json`:
 
@@ -80,6 +95,14 @@ Ask the agent to set up a cron job, or add one manually at `~/.openclaw/cron/job
 
 Your agent will use `"model": "haiku"` for cron jobs, ensuring execution is cheap and lightweight.
 
+> **Important:** Plugin tools are not available in sessions by default. Before scheduling, ensure `tools.alsoAllow` includes `openclaw-workflowskill`:
+>
+> ```bash
+> openclaw config set tools.alsoAllow '["openclaw-workflowskill"]'
+> ```
+>
+> Without this, cron sessions cannot invoke `workflowskill_run` and will fail silently.
+
 ## Tools
 
 Registers four tools with the OpenClaw agent:
@@ -177,9 +200,12 @@ To test changes, link the plugin locally and restart the OpenClaw gateway:
 ```bash
 openclaw plugins install --link "$(pwd)"
 openclaw gateway restart
-openclaw tools invoke workflowskill_validate '{"content": "..."}'
 ```
 
+Then verify tools work by asking the agent:
+
+> Validate this workflow: `inputs: { url: { type: string } }`
+
 ## License
 
 MIT

package/lib/adapters.ts

@@ -10,12 +10,11 @@ export interface GatewayConfig {
   timeoutMs?: number;
 }
 
-// Tools this plugin registers — must not be forwarded to the gateway to prevent infinite recursion.
+// Only workflowskill_run is truly recursive — a workflow step calling it
+// would launch another workflow with the same adapter, risking infinite loops.
+// The other plugin tools (validate, runs, llm) are leaf operations and safe.
 const SELF_REFERENCING_TOOLS = new Set([
-  'workflowskill_validate',
   'workflowskill_run',
-  'workflowskill_runs',
-  'workflowskill_llm',
 ]);
 
 /** ToolAdapter that delegates to the Gateway HTTP API via POST /tools/invoke. */

package/lib/openclaw-context.md

@@ -25,3 +25,12 @@ Always set `"model": "haiku"` on cron payloads — cron runs are lightweight orc
   }
 }
 ```
+
+> **Important:** Plugin tools are not available in sessions by default.
+> Before scheduling, ensure `tools.alsoAllow` includes `openclaw-workflowskill`:
+>
+> ```bash
+> openclaw config set tools.alsoAllow '["openclaw-workflowskill"]'
+> ```
+>
+> Without this, cron sessions cannot invoke `workflowskill_run` and will fail silently.

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "openclaw-workflowskill",
   "name": "WorkflowSkill",
   "description": "Author, validate, run, and review WorkflowSkill YAML workflows",
-  "version": "0.3.1",
+  "version": "0.3.4",
   "skills": ["skills/workflowskill-author"],
   "configSchema": {
     "type": "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openclaw-workflowskill",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "WorkflowSkill plugin for OpenClaw — author, validate, run, and review YAML workflows",
   "type": "module",
   "main": "index.ts",
@@ -35,7 +35,7 @@
     ]
   },
   "dependencies": {
-    "workflowskill": "^0.3.1"
+    "workflowskill": "^0.3.2"
   },
   "devDependencies": {
     "@types/node": "^25.3.0",