Agent Workflow
v1.0.0A structured workflow plugin for OpenClaw agents. Guides work through brainstorm → plan → execute → verify → deliver with persistent state, branching, parall...
⭐ 0· 85·0 current·0 all-time
bynano@kangyishuai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (Agent Workflow) matches the code and SKILL.md: it registers an agent_workflow tool, provides workflow steps, and bundles SKILLs for brainstorming → plan → execute → verify → deliver. The plugin stores state (persistent workflows) and loads bundled skills — these capabilities are expected for a workflow manager. There are no declared env vars or external credentials that don't belong to this purpose.
Instruction Scope
SKILL.md explicitly tells agents to "explore project context — check existing files, docs, prior work" and to save artifacts (e.g., docs/specs/...). That file- and state-oriented behavior is coherent for a workflow plugin, but it does mean the plugin/skills will read and write workspace files and may dispatch subagents. Verify that behavior is acceptable for your environment (e.g., private repos, secrets in project files).
Install Mechanism
The SKILL.md instructs installation via the OpenClaw plugin hub (openclaw plugins install clawhub:agent-workflow). The repository provides code files rather than requiring arbitrary remote downloads or unusual install scripts. No extract-from-URL downloads or shorteners were present in the provided metadata.
Credentials
No environment variables, credentials, or config paths are required by the skill. One minor oddity: the included package-lock.json lists many SDKs (Anthropic, AWS clients, etc.) that are not present in package.json dependencies; these entries appear as dev or incidental entries in the lockfile. This is not necessarily malicious, but you should confirm the final published package contents and dev/vendor dependencies before installing from an untrusted source.
Persistence & Privilege
The plugin stores state under a storageDir (defaults to ~/.openclaw/workspace) and is not marked always:true. It requests normal plugin permissions (enable in openclaw.json and allow the agent_workflow tool). This level of persistence is expected for a workflow engine; ensure the default storage location and permissions are acceptable for your environment.
Assessment
This plugin appears to be what it claims — a persistent workflow engine that reads project files, writes workflow state, and dispatches subagents. Before installing: 1) Verify the plugin source (clawhub:agent-workflow) is trusted; if unsure, inspect the full source (especially src/state-store.ts and src/skill-loader.ts) for any network calls or unexpected file access. 2) Check the package contents that will be installed (the package-lock shows many SDKs not in package.json) to ensure no surprising third-party binaries are included. 3) Confirm you are comfortable with workflow state being written under ~/.openclaw (or set storageDir to a controlled location). 4) If you do not want autonomous agent invocation, keep disable-model-invocation or other policy controls in mind at the platform level. If you want, provide the contents of src/state-store.ts and src/workflow-engine.ts for a deeper review of file I/O and any network behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk971zjcps4wmb6nyay4e6fyfd583qje6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.