ClawAudit verdict

twitter-post

45
🟠 Risky
Significant concerns — only install if you understand the risks

The skill requires Twitter API credentials and uses them to interact with the Twitter API, which could be exploited if credentials are not properly secured.

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

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

70
security
50
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (4)

Coarse signal — prose, single-step high

Instruction-prose smuggling shape detected: collects a sensitive target ("API Key") and emits it outward ("POST"). 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. Go to [developer.x.com](https://developer.x.com) → Dashboard → Create App 2. Set **App permissions** to **Read and Write** 3. Go to **Keys and tokens** tab 4

Pattern match medium

HTTP request to bare IP address — common in malicious payloads

SKILL.md · prose · downgraded · http://127.0.0.1

Pattern match low

Node http/https module — low-level network access

scripts/tweet.js · prose · downgraded · require('https')

Pattern match low

Accesses sensitive environment variables

scripts/tweet.js · prose · downgraded · process.env.TWITTER_CONSUMER_KEY

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

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