Clawhub Search & Verify
Analysis
The skill’s goal is reasonable, but its safety claims are contradicted by a shell wrapper that uses an undeclared Clawhub CLI login and writes local logs.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Runs in sandboxed session with no filesystem write or exec capability ... **Tags**: safe, automation, verify, no-shell, trusted
These strong safety and trust claims are contradicted by the included bash wrapper, which executes the local clawhub CLI and writes to a log file.
# Risk score: low if downloads > 1000, medium if > 100, high if < 100 RISK="✅ Trusted"
The skill presents risk/trust guidance before installation, but the code bases trust labels only on install/download counts rather than actual security review.
#!/bin/bash RESULTS=$(clawhub search "$SEARCH_TERM" --limit 3 2>/dev/null)
The artifact includes shell execution and a local CLI dependency even though the metadata declares no required binaries and the SKILL.md claims no-shell behavior.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Error: clawhub CLI not installed or logged in. Run clawhub login first.
The wrapper expects an authenticated local Clawhub CLI session, while the metadata declares no credentials or required config paths.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
LOG_FILE="logs/clawhub-search.log" echo "$(date -u): SEARCH: $SEARCH_TERM" >> "$LOG_FILE"
The script persists user search terms to a local log file, with no retention or cleanup policy described.
