try-works/role-model / .agents/skills/turnstile-spin
turnstile-spin
VerifiedSet 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.
templates/worker/wrangler.toml
View on GitHubname = "turnstile-siteverify"
main = "src/index.ts"
compatibility_date = "2026-05-01"
compatibility_flags = ["nodejs_compat"]
# Serve the post-deploy form (public/post-deploy.html) as a static asset.
# After deploy, customers land on /post-deploy.html with their Worker URL
# prefilled, and can create a Turnstile widget without leaving the flow.
[assets]
directory = "./public"
binding = "ASSETS"
# Workers Observability — structured logs, latency tracking, error rates
# all surface in the Worker's Observability tab in the dashboard.
[observability]
enabled = true
[vars]
# CORS allowed origin. Override per-environment.
# In production, set this to your customer-facing domain (e.g. "https://example.com").
# Leaving as "*" for development; production deploys MUST set this explicitly.
ALLOWED_ORIGIN = "*"
# Optional: defense against cross-site token replay. If set, the Worker
# rejects siteverify responses whose hostname doesn't match. Set this to
# your customer-facing domain (e.g. "www.example.com") for additional safety
# on single-domain deployments. Leave empty for multi-site deployments.
# EXPECTED_HOSTNAME = ""
# Log verbosity. One of: debug, info, warn, error.
LOG_LEVEL = "info"
# Secrets — never commit. Set via:
# wrangler secret put TURNSTILE_SECRET_KEY
# For local dev, create .dev.vars (gitignored) with:
# TURNSTILE_SECRET_KEY=your-secret-here
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |