SKILLEMALL.ai

AC clawpulse

Configure and maintain ClawPulse integration for OpenClaw, including token-protected status bridge, Tailscale-safe access, iOS endpoint/token defaults, and troubleshooting for ATS/auth/sync issues. Use when setting up a new machine, rotating tokens, fixing ClawPulse connectivity, or enabling assistant name + token usage + thought metadata in status responses.

ClawHub Agent Skills author: virtual-ny v2.0.4 7 files · 3 scripts body ≈ 583 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
98
Quality 40%
81
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Dangerous commands cmd-background-process scripts/setup_clawpulse_bridge.sh:304
      Starts a background / autostarted process
      nohup python3 "$BRIDGE_PY" >"$LOG_FILE" 2>&1 &
    • low Dangerous commands cmd-background-process scripts/setup_clawpulse_monitor.sh:116
      Starts a background / autostarted process
      nohup python3 "$MONITOR_PY" >"$LOG_FILE" 2>&1 &

    Files scanned: 7. 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 53/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (clawpulse) differs from the folder (clawpulse-bridge)
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 17 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Execution cost. Instruction body is 583 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
    • -31 of 4 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 361: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 17 items
    • +4Has examples (4 code blocks)

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

    External checks

    ClawHub: suspicious
    The skill mostly does what it claims, but its monitor exposes an unauthenticated internal status endpoint on all network interfaces by default.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026