SKILLEMALL.ai
RU Sign in

BB roadrunner

Beeper Desktop CLI for chats, messages, contacts, connect info, websocket events, search, and reminders.

ClawHub Agent Skills author: johntheyoung v0.17.0 2 files body ≈ 2 560 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
55
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 111 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2560 tokens
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (10 tags): a typed call is more reliable

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)
  • +3Description length 104: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -5Long text without headings
  • +1No license
  • +2Single-language instructions
  • +3Step-by-step instructions: 111 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.

External checks

ClawHub: clean
This skill is a disclosed Beeper Desktop CLI helper for reading and acting on chats, with sensible safety instructions around private data and message-sending.
LLM: benign (high) · VirusTotal: benign · 10 Sept 2026