BD pixel-agents
Real-time pixel art ops dashboard for OpenClaw deployments. Visualizes agent activity as character sprites in a shared office with live activity bubbles, hardware monitoring, service controls, and task spawning.
As a process D 36/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
ReferenceAI and agentsData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
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:309High-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:323High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7pY+zoMV…h0x/Ptw8…8dg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:339High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…b00+Gxjx…zRc/oZwU…hzA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:403High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:435High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Dsc+j03S…0oA==",
detector
Files scanned: 78. 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 36/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (pixel-agents) differs from the folder (openclaw-pixel-agents-dashboard)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 281 tokens
- 100Running it twice. No mutating operations
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 211: enough signal without eating the budget
- +4Structure: 4 headings
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: suspicious
The dashboard’s purpose is mostly coherent, but it exposes powerful unauthenticated controls that can restart services, change config, run updates, and use SSH if the server is reachable.
LLM: suspicious (high) · VirusTotal: · 29 May 2026