AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Sites

skill-xclouddev-xcloud-agent-skills-sites · by xCloudDev

Manage xCloud sites — list/inspect sites, status, events, deployment logs, monitoring, backups, rescue, snapshots, domains & redirections, cache purge, SSH/SFTP config, site cron jobs, git, and access logs. Use for any site lifecycle or delivery request. For SSL/certs see xcloud:ssl; for WordPress plugins/updates/vulnerabilities/PageSpeed see xcloud:wordpress; for server-level infra see xcloud:se…

No reviews yet
0 installs
33 views
0.0% view→install

Install

$ agentstack add skill-xclouddev-xcloud-agent-skills-sites

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-xclouddev-xcloud-agent-skills-sites)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Sites? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

xCloud Sites

Owns site lifecycle and delivery. Read the shared layer first for auth, base URL, envelope, pagination, and rate limits:

  • ${CLAUDE_PLUGIN_ROOT}/reference/auth.md
  • ${CLAUDE_PLUGIN_ROOT}/reference/conventions.md
XC="${CLAUDE_PLUGIN_ROOT}/scripts/xcloud.sh"

Scopes: reads need read:sites, writes need write:sites.

Response format

Brand every user-facing reply (see reference/conventions.mdResponse format): open with ☁️ **xCloud · Sites** — , give the trimmed result, and close with a _via xcloud:sites_ line.

Narrate each call (see Progress narration): before every $XC call print one line of what xCloud is doing, e.g. ☁️ xCloud is fetching site \\; 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 "Creating…" or "Polling…". Say xCloud is creating….

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

Sub-resources (load on demand)

| Sub-resource | Reference file | |---|---| | Backups (trigger, list, settings, status, count) | reference/backups.md | | Domains, redirections, web rules | reference/domains.md | | Cache (purge, purge-all, settings) | reference/cache.md | | SSH/SFTP config & keys | reference/ssh.md | | Site cron jobs | reference/cron-jobs.md | | Git deployment settings and manual deploys | reference/git.md |

Core endpoints

| Operation | Method + path | |---|---| | List sites | GET /sites | | Get site | GET /sites/{uuid} | | Status | GET /sites/{uuid}/status | | Events | GET /sites/{uuid}/events | | Deployment logs | GET /sites/{uuid}/deployment-logs | | Monitoring (+ history) | GET /sites/{uuid}/monitoring[/history] | | Access logs | GET /sites/{uuid}/access-logs | | Git deployment info | GET /sites/{uuid}/git | | Update Git deployment settings | PUT /sites/{uuid}/git | | Trigger Git deployment | POST /sites/{uuid}/git/deploy | | Snapshots | GET /sites/{uuid}/snapshots | | Staging sites | GET /sites/{uuid}/staging-sites | | Custom nginx / site scripts / IP access | GET /sites/{uuid}/{custom-nginx,site-scripts,ip-access} | | Rescue site | POST /sites/{uuid}/rescue |

Not here: SSL → xcloud:ssl; WordPress/vulns/pagespeed → xcloud:wordpress; servers → xcloud:servers.

Common reads

Find a site by domain (resolve its UUID first):

"$XC" GET "/sites?search=example.com&per_page=20" \
  | jq '(.data.items // .data.data // []) | map({uuid, name, domain: .domain_name, status, type})'

Status + recent events (the go-to triage pair):

SITE_UUID='replace-me'
"$XC" GET "/sites/$SITE_UUID/status" | jq '.data'
"$XC" GET "/sites/$SITE_UUID/events" | jq '(.data.items // .data) | .[0:10]'

Writes

Rescue a broken site (all flags optional booleans; pick the repairs you need):

"$XC" POST "/sites/$SITE_UUID/rescue" '{
  "isolate_user": true,
  "regenerate_nginx": true,
  "restart_nginx": true,
  "reinstall_php": false
}' | jq '.message'

Pitfalls

  • Many list endpoints differ in pagination shape — use

(.data.items // .data.data // []).

  • Writes are async; confirm via GET /sites/{uuid}/events.
  • A 502 with status still provisioned is usually a missing site OS user — pull

/sites/{uuid}/ssh (site_user) and the server tasks to confirm.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.