Cloudflare
Use Cloudflare API credentials bound in Nuphos to inspect or change Cloudflare account resources.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Cloudflare when an AI agent needs a reusable SKILL.md workflow for this job: Use Cloudflare API credentials bound in Nuphos to inspect or change Cloudflare account resources.
When not to use it
Skip Cloudflare when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/cloudflare # Save SKILL.md to ~/.claude/skills/cloudflare/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cloudflare/SKILL.md. For a shared project, commit the folder at .claude/skills/cloudflare/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Cloudflare skill for this task: Use Cloudflare when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 69/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- chatgptinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- geminiinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- copilotinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- llamainferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- perplexityinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- mistralinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
- grokinferred
The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# cloudflare
## Session isolation
Keep CLI credentials and settings inside the current session's `HOME` (`NUPHOS_SESSION_HOME`) and respect the supplied CLI config environment variables. Do not copy another session's or the runtime owner's credentials. Without `NUPHOS_SESSION_HOME`, CLI defaults may use shared runtime configuration; be aware of the affected scope.
Changing runtime-global settings is possible, but strongly discouraged unless the user understands the impact on other sessions and explicitly requests it. Explain the shared scope first; do not unset session isolation variables, write to the runtime owner's home, use a shared OS credential store, or modify shared shell startup files as routine setup. This is configuration isolation, not an OS security boundary.
Use this skill when the user wants to inspect or change Cloudflare resources in a team-bound account.
## Setup
The bound Cloudflare accounts are already listed for you under **Cloudflare accounts:** in the credential section of the system prompt. Each line carries the `accountId`, `accountName`, and a ready-to-run `setupCommand`. Pick the matching account and run its `setupCommand` verbatim:
```bash bash skills/cloudflare/scripts/setup-credentials.sh <teamId> <accountId> ```
The script calls `GET /teams/$TEAM/cloudflare-accounts/$ACCOUNT_ID/credentials` on Nuphos backend with the user's `NUPHOS_TOKEN`. When running inside an Nuphos agent sandbox, it prefers the agent-session path automatically. It writes a private env file at `~/.cloudflare/nuphos.env`.
Then call Cloudflare with curl:
```bash source ~/.cloudflare/nuphos.env
curl -sS -H @<(printf 'Authorization: Bearer %s\n' "$CLOUDFLARE_API_KEY") \ "https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID" ```
If the credential section lists no Cloudflare accounts, tell the user a team admin needs to bind one first — you cannot bind it for them.
### Fallback: discover accounts yourself
Only if the credential section is missing or looks stale. `$TEAM` is exported in the runtime environment.
```bash # Reuse the helper from the nuphos-api skill (loads it if needed): ac() { curl -sS -H @<(printf 'Authorization: Bearer %s\n' "$NUPHOS_TOKEN") "${NUPHOS_BACKEND_URL:-https://api.nuphos.ai}$1" "${@:2}"; }
ac /teams/$TEAM/cloudflare-accounts | python3 -m json.tool ```
## Nuphos API
- `GET /teams/$TEAM/cloudflare-accounts` — list bound Cloudflare accounts (`accountId`, `accountName`) - `POST /teams/$TEAM/cloudflare-accounts` (admin) — bind an account with `accountId` and a scoped API token as `apiKey` - `GET /teams/$TEAM/cloudflare-accounts/$ACCOUNT_ID` — account detail without the secret - `DELETE /teams/$TEAM/cloudflare-accounts/$ACCOUNT_ID` (admin) - `GET /teams/$TEAM/cloudflare-accounts/$ACCOUNT_ID/credentials` — retrieve the bound API key/token for Cloudflare API calls
## Safety
- Use Cloudflare scoped API tokens. Global API Keys are not supported. - Treat the returned key as sensitive. Do not print it, commit it, or paste it into final answers. - Confirm with the user before mutations such as changing DNS records, zones, workers, rules, WAF, access policies, or account settings. - If a Cloudflare call returns 401/403, re-run the setup script first. If it still fails, explain the missing Cloudflare permission or account mismatch. - Zone GraphQL Analytics (`httpRequestsAdaptiveGroups` and similar) needs the `analytics.read` scope. Grants connected before Nuphos requested it fail with a missing `com.cloudflare.api.account.zone.analytics.read` permission: ask the user to reconnect the account with Update scopes on its Cloudflare permissions page instead of retrying.
Intended uses
- Use Cloudflare when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.