AF shellbot-website
Build, deploy, and design micro apps and websites on Cloudflare Workers. Scaffolds from templates (React Router + Hono, Next.js, Astro, Remix), deploys, sets up custom domains, provisions resources (D1, KV, R2, Queues), manages secrets, and applies production-grade frontend design. Use when creating websites, web apps, landing pages, or any project on Cloudflare Workers.
As a process F 53/100 · Will not run — References files that are not bundled: scripts/provision-*.sh
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(curlallowed-tools: Bash(wrangler *) Bash(npx wrangler *) Bash(npm create cloudflare*) Bash(bash scripts/*) Bash(curl *api.cloudflare.com*) Bash(npm run *) Bash(npm install *) Bash(npx create-cloudflare*)
Files scanned: 23. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/provision-*.sh
Process rating: all ten parameters 53/100
- 0Tools and files. 1 referenced file(s) missing: scripts/provision-*.sh
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 22 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3422 tokens
- 100Running it twice. Mutating operations check current state
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 373: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (18 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
- +3All 10 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.