AC agent-workflow
A structured workflow plugin for OpenClaw agents. Guides work through brainstorm → plan → execute → verify → deliver with persistent state and multi-project support. Trigger ONLY when the user explicitly requests a structured workflow (e.g. 'start a workflow', 'use agent-workflow', 'plan this project'). Do NOT trigger for: simple questions, one-off tasks, quick edits, routine conversations, or any task where the user has not requested workflow management.
As a process C 57/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:22High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-1ad+Sc/0sCt…16I+aF+Ywdi…k1d+8oE3C4ZEw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:53High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3wH+jfWB…yfN+lFri…oov+PzfnxxD5g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:151High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wIN//F77/IADDSs58i+MDaO…jeo+YFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:640High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…c1n+0dX79+i287…67A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:740High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…8tJ++Ku97…8Zu+xfBP…2pf+8SGN5/NoytfKgYPIw==",
detector
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 675 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 459: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.