AC tidbyt-status
HTTP API server that exposes OpenClaw agent status for Tidbyt LED displays. Use when creating integrations with Tidbyt devices, building status dashboards, or displaying agent activity on 64x32 pixel displays. Returns JSON with agent status, emoji, activity level, and task counts.
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, progress reporting
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 Dangerous commands
cmd-background-processinstall.sh:47Starts a background / autostarted processnohup python3 scripts/status_server.py > /tmp/scout-status.log 2>&1 &
-
low Dangerous commands
cmd-privilegeinstall.sh:81Privilege escalation / world-writable permissions (string literal in code, not executed)echo " sudo cp $SERVICE_FILE /etc/systemd/system/"
code literal -
low Dangerous commands
cmd-background-processinstall.sh:83Starts a background / autostarted process (string literal in code, not executed)echo " sudo systemctl enable scout-status"
code literal -
low Dangerous commands
cmd-background-processSKILL.md:142Starts a background / autostarted processsudo systemctl enable scout-status
-
low Dangerous commands
cmd-background-processSKILL.md:149Starts a background / autostarted processnohup python3 scripts/status_server.py > /tmp/scout-status.log 2>&1 &
Files scanned: 5. 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
- 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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 35 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1199 tokens
- 100Running it twice. Mutating operations check current state
- low 11 top-level sections: this looks like several domains in one skill
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)
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 281: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (18 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.