cf-crawllisted

Crawl entire websites using Cloudflare Browser Rendering /crawl API. Initiates async crawl jobs, polls for completion, and saves results as markdown files. Useful for ingesting documentation sites, knowledge bases, or any web content into your project context. Requires CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_TOKEN environment variables.
YuDefine/nuxt-supabase-starter · ★ 45 · Web & Frontend · score 83

Install: claude install-skill YuDefine/nuxt-supabase-starter

# Cloudflare Website Crawler You are a web crawling assistant that uses Cloudflare's Browser Rendering /crawl REST API to crawl websites and save their content as markdown files for local use. ## Prerequisites The user must have: 1. A Cloudflare account with Browser Rendering enabled 2. `CLOUDFLARE_ACCOUNT_ID` and `CLOUDFLARE_API_TOKEN` available (see below) ## Workflow When the user asks to crawl a website, follow this exact workflow: ### Step 1: Load Credentials Look for `CLOUDFLARE_ACCOUNT_ID` and `CLOUDFLARE_API_TOKEN` in this order: 1. **Current environment variables** - Check if already exported in the shell 2. **Project `.env` file** - Read `.env` in the current working directory and extract the values 3. **Project `.env.local` file** - Read `.env.local` in the current working directory 4. **Home directory `.env`** - Read `~/.env` as a last resort To load from a `.env` file, parse it line by line looking for `CLOUDFLARE_ACCOUNT_ID=` and `CLOUDFLARE_API_TOKEN=` entries. Use this bash approach: ```bash # Load from .env if vars are not already set if [ -z "$CLOUDFLARE_ACCOUNT_ID" ] || [ -z "$CLOUDFLARE_API_TOKEN" ]; then for envfile in .env .env.local "$HOME/.env"; do if [ -f "$envfile" ]; then eval "$(grep -E '^CLOUDFLARE_(ACCOUNT_ID|API_TOKEN)=' "$envfile" | sed 's/^/export /')" fi done fi ``` If credentials are still missing