Caveat verdict

slack-lead-scanner

badgebot

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

The skill sends data to Apollo.io and HubSpot APIs, which may be beyond its need, and accesses Slack channels.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

100
security
90
transparency
70
maintenance

Findings (1)

Coarse signal — prose, single-step high

Instruction-prose smuggling shape detected: collects a sensitive target ("api_key") and emits it outward ("Append"). Phrased as prose with no trigger tokens — a semantic prompt-injection / data-exfil pattern the syntactic scanners can't see. Final tier capped at Caution; review the instructions before installing.

SKILL.md · 1. Load state from ~/clawd/memory/slack-lead-scanner-state.json 2. Fetch messages: `curl -H "Authorization: Bearer $SLACK_TOKEN" "https://slack.com/api/conversa

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API