04-cloudflare-rules
- **Target platform is Cloudflare** (Workers, R2, D1, Access, Tunnel, DNS/CDN). New work should prefer Cloudflare-native services over AWS. - Treat remaining AWS usage (SSM, SES, Cognito, S3, Lambda, Athena, etc.) as **legacy to migrate off**, not expand.
Install / Use
npx skills add Themis128/cloudless.grInstalls into whichever agent you are using.
.clinerules
Cline rules
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of 04-cloudflare-rules
04-cloudflare-rules scores 62/100 on our quality scale, 4007th of 4,619 Development & Engineering skills we index.
Its .clinerules is 2.5 KB long, well organised into 8 sections with 1 code example: a solid amount of guidance for an agent.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-10-18 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-12. Automated pattern scan on 2026-10-12. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
04-cloudflare-rules compared with similar skills
All 4 of these similar skills score higher than 04-cloudflare-rules; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| 04-cloudflare-rules (this skill)by Themis128 | 62 | 0 | — | .clinerules |
| taste-skillby Leonxlnx | 100 | 111.2k | 1d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 70.1k | 1d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 46.7k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 84.2k | today | MCP Server |
Frequently asked questions
- How do I install 04-cloudflare-rules?
- Run
npx skills add Themis128/cloudless.gr. The install tabs above show the steps for each supported agent. - Which AI agents does 04-cloudflare-rules work with?
- It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
- Is 04-cloudflare-rules safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is 04-cloudflare-rules still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubCloudflare Rules
AWS → Cloudflare Migration Preference
- Target platform is Cloudflare (Workers, R2, D1, Access, Tunnel, DNS/CDN). New work should prefer Cloudflare-native services over AWS.
- Treat remaining AWS usage (SSM, SES, Cognito, S3, Lambda, Athena, etc.) as legacy to migrate off, not expand.
- Do not install the AWS CLI on developer machines, Pi hosts, or CI agents.
- Do not add the AWS SDK to new code or scripts. Prefer existing in-repo wrappers only when touching legacy paths.
- Prefer Cloudflare APIs / Wrangler / existing
cloudflare-*skills and repo scripts over any AWS tooling.
Deployment Target
- Primary: Pi k3s cluster (omv node at 192.168.1.128)
- Proxy: Cloudflare Workers (
pi-origin) - Build: OpenNext.js Cloudflare (
pnpm cf:build→opennextjs-cloudflare build) - Deploy:
pnpm cf:deployorpnpm deploy(SST-based production)
Key Bindings (wrangler.jsonc)
| Binding | Type | Resource |
|---------|------|----------|
| NEXT_INC_CACHE_R2_BUCKET | R2 | cloudless-assets |
| NEXT_CACHE_D1_BINDING | D1 | user-auth-db |
| AUTH_DB | D1 | user-auth-db |
| ASSETS_BUCKET | R2 | cloudless-assets |
| ANALYTICS_BUCKET | R2 | cloudless-analytics |
| DATALAKE_BUCKET | R2 | datalake-bucket |
Secrets Management
- Non-secret config: D1
app_configtable (migration 0007) - Secrets: Wrangler secrets (not SSM, not .env files in prod)
- ETL scripts: Read from D1 via
/api/configendpoint or use environment variables - SSM escape hatch:
SSM_DISABLED=1environment variable disables SSM fallback
Cloudflare Tunnel
- Tunnel ID: e977a490-58c5-4fdb-9155-86832e3e636a
- Status: ACTIVE since 2026-07-20
- 11 services connected: grafana, kuma, n8n, ntfy, espocrm, meili, postiz, appflowy, docs, and main app
- Troubleshooting: Check tunnel status with
cloudflared tunnel info <tunnel-id>
OpenNext.js Build Pipeline
pnpm cf:build
└─► opennextjs-cloudflare build
├─► next build (via buildCommand in open-next.config.ts)
└─► OpenNext bundling → .open-next/worker.js
pnpm cf:deploy
└─► opennextjs-cloudflare deploy
├─► Uploads .open-next/worker.js to Cloudflare Worker
└─► Uploads static assets to R2
Workers AI
- Primary:
@cf/meta/llama-3.1-8b-instruct - Fallback chain: Workers AI → Google Gemini → Anthropic → Chat Service Binding
- Chat endpoint:
/api/chat(POST) - Admin AI:
/api/admin/ai/generate(requires admin auth)
Related Skills
taste-skill
111.2kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
70.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
46.7kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
84.2k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.