agentleFS
Sign inStart free
blitzhash360-webblitzhash360-web/blitzhash-cloudflare-production-skills/skills/cloudflare-turnstile/SKILL.md

cloudflare-turnstile

Skill0 starsChanged 10 days agoMITView on GitHub

Set up Cloudflare Turnstile (CAPTCHA alternative) end to end: create a widget, add the client widget to a form, and verify tokens server-side with siteverify (Next.js, Express, Workers). Use when the user wants to stop spam or bot signups on login, signup, contact or checkout forms.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run commands with npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command> or, inside a clone of the repo, node …

    line 8
  2. Very specific:

    Create the widget (dry run first): cf-skills turnstile create --name "Signup form" --domains example.com,www.example.com --secret-out …

    line 12
  3. Very specific:

    Put TURNSTILE_SECRET_KEY in the hosting provider env vars.

    line 16
  4. Very specific:

    Test with Cloudflare's documented dummy keys first (secret 1x0000000000000000000000000000000AA always passes, …

    line 17
  5. Very specific:

    Every write command is a dry run by default.

    line 28
  6. Very specific:

    Only after that "yes", re-run the same command with --apply --yes (your shell is not interactive).

    line 29
  7. Distinctive:

    Never delete records or rules the user did not name.

    line 30
  8. Very specific:

    Run cf-skills audit before and after changes and tell the user what moved.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloudflare Turnstile setup

Run commands with npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command> or, inside a clone of the repo, node bin/cf-skills.mjs <command>. Below, cf-skills means either. Zone is --zone <domain or zone id> or $CLOUDFLARE_ZONE_ID.

Steps

  1. Create the widget (dry run first): cf-skills turnstile create --name "Signup form" --domains example.com,www.example.com --secret-out .env.local
    • The site key (public) is printed. The secret is masked and only written to the git-ignored file given in --secret-out.
  2. Client: cf-skills turnstile snippet --framework html --sitekey <sitekey> and paste inside the form.
  3. Server (required, the widget alone protects nothing): cf-skills turnstile snippet --framework next|express|worker and copy snippets/turnstile/siteverify.mjs into the project.
  4. Put TURNSTILE_SECRET_KEY in the hosting provider env vars. Never in a NEXT_PUBLIC_ / VITE_ variable.
  5. Test with Cloudflare's documented dummy keys first (secret 1x0000000000000000000000000000000AA always passes, 2x0000000000000000000000000000000AA always fails).

Guidance

  • verifyTurnstile fails closed (network error = not verified), rejects tokens over 2048 chars, and can check the expected hostname and action.
  • Tokens are single use and expire after 300 seconds; verify once per submission.
  • Token: Account > Turnstile Edit (only for create/list); snippet needs no token.

Safety rules (always)

  • The API token lives only in the environment (CLOUDFLARE_API_TOKEN) or a git-ignored .env. Never ask the user to paste it into chat, never print it, never pass it as a flag, never commit it.
  • Every write command is a dry run by default. Run it without --apply first, show the user the printed plan, and wait for an explicit "yes" in chat.
  • Only after that "yes", re-run the same command with --apply --yes (your shell is not interactive). Never add --yes on your own initiative.
  • Never delete records or rules the user did not name. Never widen the token's permissions.
  • Run cf-skills audit before and after changes and tell the user what moved.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free