SKILLEMALL.ai
RU Sign in

BB btw Command

Ask non-blocking clarifying questions during agent workflows. Use when agents need user input without halting execution. Handles deployment decisions, code review confirmations, data validation choices, and security checks with timeout defaults.

ClawHub Hermes author: claw0x v1.0.0 MIT-0 3 files body ≈ 1 762 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process B 72/100 · Nearly there — weak spots: when it triggers, consistency, running it twice

ProcedureInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
B
72/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-long-hermes description is 246 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "price_per_call"
  • note frontmatter-key unknown frontmatter key "input_schema"
  • note frontmatter-key unknown frontmatter key "output_schema"

Process rating: all ten parameters 72/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (btw Command) differs from the folder (btw-command)
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 10 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 1762 tokens
  • low 14 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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 245: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 10 items
  • +3Output format is stated explicitly
  • +4Has examples (11 code blocks)

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

External checks

ClawHub: suspicious
This local question helper is not malware, but it can let timeout defaults stand in for human approval in sensitive workflows and exposes supplied context in logs.
LLM: suspicious (high) · VirusTotal: · 29 May 2026