cloudflare-operator
/cloudflare-operator
Administruje DNS, proxy, TLS, tunelami i Access, Workers, Pages, WAF, limitami i przekierowaniami w Cloudflare z zachowaniem punktu powrotu.
- Autor
- PapeMati98 ↗
- Repozytorium
- Ai-Stack ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Administruje DNS, proxy, TLS, tunelami i Access, Workers, Pages, WAF, limitami i przekierowaniami w Cloudflare z zachowaniem punktu powrotu.
Oryginalny opis (EN)
Operate Cloudflare DNS, proxy and TLS, Tunnel and Access, Workers and Pages, WAF, rate limits, cache and redirects. Use for scoped Cloudflare administration, deployment troubleshooting, access checks and usage diagnosis; distinguish account/zone/environment and preserve rollback before changes.
Jak działa
- Resolve before acting
- Keep the change bounded
- Honest verification
Podgląd SKILL.md
--- name: cloudflare-operator description: Operate Cloudflare DNS, proxy and TLS, Tunnel and Access, Workers and Pages, WAF, rate limits, cache and redirects. Use for scoped Cloudflare administration, deployment troubleshooting, access checks and usage diagnosis; distinguish account/zone/environment and preserve rollback before changes. metadata: version: "0.1.0" --- # Cloudflare Operator ## Resolve before acting Read the project brief through `llm-wiki` and reconcile it with live state. Identify project, customer, account ID, zone ID, hostname, environment and owner of the configuration (Terraform, Wrangler, Git deployment or dashboard). A domain name or currently selected browser account alone is not sufficient identity. Do not infer a client account from a similarly named zone or inherited CLI login. Read only the applicable procedure: - [Identity and operations](references/identity-operations.md): tokens, API/MCP, inventory, usage, error diagnosis and receipt. - [DNS and TLS](references/dns-tls.md): domains, records, proxy, certificates. - [Tunnel and Access](references/tunnel-access.md): connector lifecycle and interactive/machine access to local or remote applications. - [Workers and Pages](references/workers-pages.md): builds, environments, bindings, deployments, logs and rollback. - [Edge protection](references/edge-protection.md): WAF, limits, cache, redirects. ## Keep the change bounded Read-only discovery can proceed within the user's resource/data scope. Before a write, record exact IDs, expected result, current state, rollback and approval. Public DNS/tunnel/domain changes, production deployment, IAM/secret changes, destructive operations and paid resource activation require explicit owner scope. Skill installation is not such approval. Once authorized, execute the bounded operation without asking again at every command. Prefer the project's existing IaC owner, installed CLI or supported API. Use an available authorized Cloudflare connector if appropriate; this skill does not install a plugin, grant permissions or guarantee a connector exists. Dashboard automation is a fallback, not permission to switch accounts or expose tokens. Recheck official API schemas, installed `--help`, plan features and prices before use; do not copy obsolete commands or assume a successful login authorizes a write. Large changes use existing planning, `agent-graph`, `agent-loop` and `accept-system`; this skill supplies Cloudflare-specific operations and oracles. Fleet remains the contractor/model router. `ngrok-operator` is a separate provider, not an automatic fallback. Use `data-governance` for storage/migration/retention and `remote-computer-use` for relevant user-journey verification on the test VM. ## Honest verification HTTP 200 alone is not PASS: check API `success`/errors, live resource state and the consumer's actual behavior. Include an authorized and unauthorized access case where protection changes. Use synthetic DEV/TEST identities and technically block real email/payment/webhook effects before testing. Restore only changed, owned resources; re-read live state before rollback to avoid overwriting concurrent work. Never treat DNS propagation, cache purge or external side effects as instantly reversible. Report gaps, not invented PASS. End with changed IDs, expected/actual checks, usage if measured and rollback readiness. Record material integration/deploy/auth changes with a redacted Hub handoff. Skill installed, credentials configured, native discovery and live operation verified are separate states, especially across machines.
Pliki w paczce (6)
- SKILL.md 4 KB
- references/dns-tls.md 2 KB
- references/edge-protection.md 2 KB
- references/identity-operations.md 4 KB
- references/tunnel-access.md 2 KB
- references/workers-pages.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie cloudflare-operator.
Migawka bazy z 13.11.2026 · wersja paczki 7b3dd66ce138 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 96cloudflare
Zarządza strefami DNS, pamięcią podręczną, tunelami i Workers w Cloudflare przez API. - 95Cloudflare
Wdraża aplikacje Workers i Pages w Cloudflare i wskazuje, gdzie szukać dokumentacji. - 90connector-cloudflare
Zarządza infrastrukturą Cloudflare dla produktu legal-tech: rekordy DNS, Pages, Workers, R2 i KV z poziomu przepływu AI. - 100mcp-server-cloudflare
Instaluje serwer MCP Cloudflare do zarządzania DNS, Workers i pamięcią podręczną CDN oraz wykonuje jego narzędzia. - 95cloudflare-manager
Zarządza kontem Cloudflare: wdraża Workers, KV, R2, Pages, DNS i trasy, wymaga CLOUDFLARE_API_KEY w .env i środowiska Bun. - 100cloudflare-manager
Zarządza kontem Cloudflare: wdraża Workers, KV, R2, Pages, DNS i trasy, wymagając CLOUDFLARE_API_KEY w .env i środowiska Bun.