Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Cloudflare Wrangler & Pages
v1.1.0Manage Cloudflare Workers, KV, D1, R2, and secrets using the Wrangler CLI. Use when deploying workers, managing databases, storing objects, or configuring Cl...
⭐ 0· 326·0 current·0 all-time
byItamar C@itamarcoh3n
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (Wrangler/Cloudflare resources) aligns with the instructions (wrangler CLI, KV, D1, R2, secrets, queues). However the SKILL.md specifies a particular secrets storage path (~/.openclaw/secrets.json) and env var usage that are not reflected in the declared metadata (which lists no required env vars or primary credential).
Instruction Scope
Runtime instructions tell the agent to read ~/.openclaw/secrets.json for Cloudflare API tokens and R2 keys, to export CLOUDFLARE_API_TOKEN, and to run/install tools (npm install -g wrangler, use jq). These file reads and environment operations involve sensitive credentials and are not described in the metadata; the SKILL.md also mixes sample code in multiple languages (Python/Node) and has a minor inconsistency about presigned URL expiration, showing lack of editorial rigor.
Install Mechanism
There is no install spec in the registry (instruction-only), which is low risk. But the documentation requires Node.js v20+ and suggests `npm install -g wrangler` (global npm install) or using npx; requiring a global install and privileged package management is a user-impactful step and should be noted by the user before proceeding.
Credentials
The skill expects Cloudflare credentials (cloudflare.apiToken) and R2 accessKeyId/secretAccessKey stored in ~/.openclaw/secrets.json and also suggests exporting CLOUDFLARE_API_TOKEN. Those sensitive credentials are proportionate to the skill's functionality (managing Cloudflare/R2), but the registry metadata does not declare them as required, creating an unexplained discrepancy and a risk that secrets may be read/used without explicit declaration.
Persistence & Privilege
The skill does not request always:true, does not include an install that writes persistent system-wide config, and does not claim to modify other skills. Autonomous invocation is enabled (default) which is normal; there is no evidence the skill will persist or escalate privileges on its own.
What to consider before installing
This skill appears to be what it says (Wrangler/Cloudflare helper) but has important mismatches you should address before using it:
- Expectation of sensitive credentials: The SKILL.md instructs you to store a Cloudflare API token and R2 access keys in ~/.openclaw/secrets.json and to export CLOUDFLARE_API_TOKEN. These are reasonable for a Cloudflare tool, but the registry metadata does not declare those required credentials — treat that as an omission. Do not give the agent access to more credentials than necessary.
- Secrets handling: Keep the secrets file encrypted or otherwise restricted. Prefer using the official CLOUDFLARE_API_TOKEN environment variable or the Wrangler-auth recommended flow rather than a custom secrets.json if possible. If you use ~/.openclaw/secrets.json, review and control its contents carefully.
- Installation impact: The guide asks for Node.js v20+ and suggests a global npm install (`npm install -g wrangler`). Installing global packages can require elevated privileges — consider using npx or a local project install to reduce system impact.
- Review code samples and edits: The SKILL.md includes Python and Node samples that will read secrets from disk; inspect and, if necessary, modify these before running. There is a small inconsistency about presigned URL expiry shown in text vs. code — verify timeout values you actually need.
- Metadata/documentation gap: Ask the skill author or registry maintainer to declare required env vars/primary credential in the metadata so you can audit what the skill will need. If you will allow an agent to invoke this skill autonomously, ensure the agent is not granted blanket access to your secrets file.
If you accept those caveats and secure the credentials appropriately, the skill is functionally coherent for Cloudflare management. If you cannot or do not want to store Cloudflare/R2 credentials locally, avoid installing/using this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk971f24r1y9sc8maax6ryswm4582fjdb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.