BB turnstile-spin
Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write the frontend snippets, validate, and persist the skill. Load this when a user asks to add Turnstile, set up CAPTCHA, protect a form from bots, or fix a Turnstile integration. Mirrors developers.cloudflare.com/turnstile/spin.
Set up Cloudflare Turnstile end-to-end in a project — scan the codebase, create the widget via the Cloudflare API, deploy the managed siteverify Worker, write…
As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions
How to improve
- 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 · 9
✓ No critical or high findings
Medium and low: 9
-
low Exfiltration
net-credential-useSKILL.md:147Credential used in a network call (verify the destination is the intended service) (documentation table row)| `EXPECTED_HOSTNAME` mismatch | Update widget domains via PUT, not PATCH (PATCH returns `10405 Method not allowed`): `curl -X PUT .../widgets/$SITEKEY -d '{"name":"...","mode":"managed","domains":[..table -
low Secrets in code
secret-high-entropy-tokentemplates/worker/README.md:153High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `1x00…0AA` | Always succeeds |
table -
low Secrets in code
secret-high-entropy-tokentemplates/worker/README.md:154High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `2x00…0AA` | Always fails |
table -
low Secrets in code
secret-high-entropy-tokentemplates/worker/README.md:155High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `3x00…0AA` | Returns `timeout-or-duplicate` |
table -
low Secrets in code
secret-high-entropy-tokentemplates/worker/test/integration.test.ts:9High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)* 1x00…0AA — always passes
fixture -
low Secrets in code
secret-high-entropy-tokentemplates/worker/test/integration.test.ts:10High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)* 2x00…0AA — always fails
fixture -
low Secrets in code
secret-high-entropy-tokentemplates/worker/test/integration.test.ts:11High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)* 3x00…0AA — already-spent token (timeout-or-duplicate)
fixture -
low Secrets in code
secret-high-entropy-tokentemplates/worker/test/integration.test.ts:27High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)const PASSING_SECRET = '1x00…0AA';
fixturequoted -
low Secrets in code
secret-high-entropy-tokentemplates/worker/test/integration.test.ts:28High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)const FAILING_SECRET = '2x00…0AA';
fixturequoted
Files scanned: 31. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "references"
Process rating: all ten parameters 66/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 85Steps. 56 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3363 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (10 tags): a typed call is more reliable
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
- -46 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 383: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (1 code blocks)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.