BC openclaw-deck
Multi-column chat deck UI for OpenClaw agents. Launch a local web interface to manage and chat with multiple agents side-by-side.
Multi-column chat deck UI for OpenClaw agents.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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:294High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…SzS+cfgl…B0A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:308High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…ToE+vYgD…UJ8+N1Am3Mz4+xOBy…f4D+CpkA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:512High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…mp4+hpaf…WbT//d20x…uaA/eGVw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:648High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…HlP+kuwq…IXN/mDJIfGXvcMqCgYKekoQw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:699High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…4A7+DKln…5u0+9Pq0…OyP+8Bsg==",
detector
Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 9 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 244 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +4No input/output examples
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 9 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.