Shellbot Website
v1.1.0Build, deploy, and design micro apps and websites on Cloudflare Workers. Scaffolds from templates (React Router + Hono, Next.js, Astro, Remix), deploys, sets...
⭐ 0· 105·0 current·0 all-time
by@cohnen
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (Cloudflare Workers scaffolding, deploy, domain, resources) match the declared primary credential (CLOUDFLARE_API_TOKEN) and the included scripts (create, deploy, provision, domain, secrets, teardown). Required binaries/env are proportionate to those tasks.
Instruction Scope
SKILL.md instructs the agent to run the provided bash scripts and use wrangler/curl to talk to api.cloudflare.com — exactly what a Cloudflare worker management tool needs. However, create-project.sh supports a --template-url and uses `npm create cloudflare` which will fetch and run code from external template repos (npm / GitHub). That is expected for scaffolding but increases the runtime attack surface (untrusted template code can execute during scaffold). The skill documents OAuth storage (~/.wrangler/config/default.toml) and uses wrangler whoami as fallback — the scripts rely on Cloudflare credentials (token or local OAuth). No instructions were found that read or exfiltrate unrelated system data or call unexpected external endpoints beyond Cloudflare and npm/template hosts.
Install Mechanism
There is no install spec; this is instruction+script based. All code is contained in repository scripts (no remote install step in the skill package itself). The risk from installs comes from the normal operations the scripts perform (npm create, npm install) which will fetch dependencies from public registries — expected for project scaffolding.
Credentials
The skill requests one main credential (CLOUDFLARE_API_TOKEN) and optionally an account ID — appropriate for modifying Workers, DNS, D1, KV, R2, Queues. This credential has broad power over the Cloudflare account; the skill's actions (create projects, provision resources, manage DNS/custom domains, secrets) legitimately require elevated Cloudflare scopes. Users should create a least-privilege API token with only the required scopes rather than a full global API key.
Persistence & Privilege
always:false and the skill is user-invocable. It does not request permanent platform-level presence and does not modify other skills or global agent configuration. It may read/create files in project directories and relies on wrangler OAuth tokens if present in the user's home directory (standard behaviour).
Assessment
This skill is coherent for building and deploying Cloudflare Workers, but before installing or running it: 1) Treat the CLOUDFLARE_API_TOKEN as a high-privilege secret — create a narrowly-scoped API token (Workers Script: Edit, D1/KV/R2/Queue edits only as needed, DNS edit only if you need domain setup). 2) Review/manage any template URL you pass (--template-url) before using it — npm create / npm install will execute code from registries or GitHub during scaffolding. 3) Run scripts locally (not on untrusted remote agents) if you need to perform OAuth-based wrangler login (the OAuth flow relies on localhost callbacks). 4) Inspect scripts/manage-secrets.sh and other omitted files to confirm they handle secrets appropriately (they should use wrangler secret put and avoid echoing secrets to logs). 5) For CI use, prefer API tokens over OAuth and store tokens in your secret manager; avoid giving the token wider scopes than required.Like a lobster shell, security has layers — review code before you run it.
latestvk979egv9jnyjhwxmezh1z5mxy9834axy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis
Primary envCLOUDFLARE_API_TOKEN