How do I install the Account skill?

Run npx skillmds@latest add xclouddev/account in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Account safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Account?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Account free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Account?

xCloudDev (@xclouddev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Account by xclouddev — Agent Skill

Name: Account
Author: xCloudDev

Account

xCloud account, identity, and org-level reads — current user, API token listing and revocation, Cloudflare integrations, WordPress blueprints, and API health. Use for "who am I", token management, listing blueprints, or checking integrations. NOT server or site operations (see xcloud:servers / xcloud:sites).

xCloudDev Updated Sep 22, 2026

File contents

xCloud Account

Identity and org-level endpoints. For auth, base URL, and response conventions read the shared layer first:

${CLAUDE_PLUGIN_ROOT}/reference/auth.md
${CLAUDE_PLUGIN_ROOT}/reference/conventions.md
${CLAUDE_PLUGIN_ROOT}/reference/mcp.md — prefer the MCP tools when connected: user_show, blueprints_index, integrations_cloudflare_index. Exception: /health and API-token list/revoke are REST-only — the MCP never exposes token management; always use $XC for those.

XC="${CLAUDE_PLUGIN_ROOT}/scripts/xcloud.sh"

Response format

Brand every user-facing reply (see reference/conventions.md → Response format): open with ☁️ **xCloud · Account**, give the trimmed result, and close with a _via xcloud:account_ line.

Narrate each call (see Progress narration): before every $XC call print one line of what xCloud is doing, e.g. ☁️ xCloud is fetching your account…; the first call of a task opens with ☁️ xCloud is starting a session…. Every progress line and every action sentence must start with xCloud as the actor — never a bare verb like "Fetching…" or "Checking…". Say xCloud is fetching….

On the first xcloud reply in a conversation, lead with the xCloud startup banner (see reference/conventions.md → Startup banner) in a fenced code block — once per conversation.

What this skill owns

Operation	Method + path	Scope
API health	`GET /health`	none
Current user	`GET /user`	token
List API tokens	`GET /user/tokens`	token (`*`)
Revoke a token	`DELETE /user/tokens/{tokenUuid}`	token (`*`)
List Cloudflare integrations	`GET /integrations/cloudflare`	`read:servers`
List blueprints	`GET /blueprints`	`read:servers`

Not here: server management → xcloud:servers; site management → xcloud:sites.

Examples

Health (the only unauthenticated endpoint):

"$XC" GET /health | jq

Who am I (verifies the token):

"$XC" GET /user | jq '.data | {uuid, name, email, team: .team.name}'

List API tokens (needs the * scope) — note each token's uuid, which is what the revoke call below takes:

"$XC" GET /user/tokens | jq '(.data.items // .data.data // .data) | map({uuid, name, last_used_at})'

Revoke a token (pass the uuid from the list above — restate before running):

TOKEN_UUID='8c1f3a89-2c4e-4a73-9d4c-8b1f2a3d4e5f'
"$XC" DELETE "/user/tokens/$TOKEN_UUID" | jq '.message'

Cloudflare integrations on the team:

"$XC" GET /integrations/cloudflare | jq '.data'

Blueprints (resolve a blueprint_uuid before creating a WordPress site):

"$XC" GET "/blueprints?per_page=100" \
  | jq '(.data.items // .data.data // .data) | map({uuid, name, is_default, is_public})'

Pitfalls

Token revocation is keyed by the token's uuid (from GET /user/tokens), not a numeric id — DELETE /user/tokens/{tokenUuid}.
GET /user/tokens returns 403 unless the token carries the * scope.
blueprints requires read:servers, not read:sites.

---name: accountdescription: xCloud account, identity, and org-level reads — current user, API token listing and revocation, Cloudflare integrations, WordPress blueprints, and API health. Use for "who am I", token management, listing blueprints, or checking integrations. NOT server or site operations (see xcloud:servers / xcloud:sites).---# xCloud AccountIdentity and org-level endpoints. For auth, base URL, and response conventionsread the shared layer first:- `${CLAUDE_PLUGIN_ROOT}/reference/auth.md`- `${CLAUDE_PLUGIN_ROOT}/reference/conventions.md`- `${CLAUDE_PLUGIN_ROOT}/reference/mcp.md` — **prefer the MCP tools when connected**: `user_show`, `blueprints_index`, `integrations_cloudflare_index`. **Exception:** `/health` and API-token list/revoke are REST-only — the MCP never exposes token management; always use `$XC` for those.```bashXC="${CLAUDE_PLUGIN_ROOT}/scripts/xcloud.sh"```## Response formatBrand every user-facing reply (see `reference/conventions.md` →**Response format**): open with `☁️ **xCloud · Account**`, give the trimmedresult, and close with a `_via xcloud:account_` line.Narrate each call (see **Progress narration**): before every `$XC` call print oneline of what xCloud is doing, e.g. `☁️ xCloud is fetching your account…`; thefirst call of a task opens with `☁️ xCloud is starting a session…`. **Everyprogress line and every action sentence must start with `xCloud` as the actor —never a bare verb like "Fetching…" or "Checking…". Say `xCloud is fetching…`.**On the **first** xcloud reply in a conversation, lead with the xCloud startupbanner (see `reference/conventions.md` → **Startup banner**) in a fenced codeblock — once per conversation.## What this skill owns| Operation | Method + path | Scope ||---|---|---|| API health | `GET /health` | none || Current user | `GET /user` | token || List API tokens | `GET /user/tokens` | token (`*`) || Revoke a token | `DELETE /user/tokens/{tokenUuid}` | token (`*`) || List Cloudflare integrations | `GET /integrations/cloudflare` | `read:servers` || List blueprints | `GET /blueprints` | `read:servers` |**Not here:** server management → `xcloud:servers`; site management → `xcloud:sites`.## ExamplesHealth (the only unauthenticated endpoint):```bash"$XC" GET /health | jq```Who am I (verifies the token):```bash"$XC" GET /user | jq '.data | {uuid, name, email, team: .team.name}'```List API tokens (needs the `*` scope) — note each token's `uuid`, which is whatthe revoke call below takes:```bash"$XC" GET /user/tokens | jq '(.data.items // .data.data // .data) | map({uuid, name, last_used_at})'```Revoke a token (pass the `uuid` from the list above — restate before running):```bashTOKEN_UUID='8c1f3a89-2c4e-4a73-9d4c-8b1f2a3d4e5f'"$XC" DELETE "/user/tokens/$TOKEN_UUID" | jq '.message'```Cloudflare integrations on the team:```bash"$XC" GET /integrations/cloudflare | jq '.data'```Blueprints (resolve a `blueprint_uuid` before creating a WordPress site):```bash"$XC" GET "/blueprints?per_page=100" \ | jq '(.data.items // .data.data // .data) | map({uuid, name, is_default, is_public})'```## Pitfalls- Token revocation is keyed by the token's **`uuid`** (from `GET /user/tokens`), not a numeric id — `DELETE /user/tokens/{tokenUuid}`.- `GET /user/tokens` returns `403` unless the token carries the `*` scope.- `blueprints` requires `read:servers`, not `read:sites`.

Frequently asked questions