cloudthinker-ai/CloudSkills / skills/connections/managing-anyscale
managing-anyscale
VerifiedUse when working with Anyscale — anyscale platform management covering Ray clusters, services, model deployments, jobs, and usage analytics. Use when monitoring deployed services, analyzing cluster utilization, reviewing job status, managing model endpoints, or troubleshooting Anyscale deployments.
Anyscale Management Skill
Manage and analyze Anyscale platform resources including services, clusters, jobs, and deployments.
API Conventions
Authentication
All API calls use Bearer API key, injected automatically.
Base URL
https://api.anyscale.com/v2
Core Helper Function
#!/bin/bash
anyscale_api() {
local method="$1"
local endpoint="$2"
local data="${3:-}"
if [ -n "$data" ]; then
curl -s -X "$method" \
-H "Authorization: Bearer $ANYSCALE_API_KEY" \
-H "Content-Type: application/json" \
"https://api.anyscale.com/v2${endpoint}" \
-d "$data"
else
curl -s -X "$method" \
-H "Authorization: Bearer $ANYSCALE_API_KEY" \
"https://api.anyscale.com/v2${endpoint}"
fi
}
Output Rules
- Target ≤50 lines per script output
- Use
jqto extract only needed fields - Never dump full API responses
Phase 1: Discovery
#!/bin/bash
echo "=== Services ==="
anyscale_api GET "/services?count=20" \
| jq -r '.results[] | "\(.id[0:16])\t\(.name)\t\(.state)\t\(.created_at[0:10])"' \
| column -t | head -15
echo ""
echo "=== Clusters ==="
anyscale_api GET "/sessions?count=20" \
| jq -r '.results[] | "\(.id[0:16])\t\(.name)\t\(.state)\t\(.created_at[0:10])"' \
| column -t | head -15
echo ""
echo "=== Jobs ==="
anyscale_api GET "/jobs?count=20" \
| jq -r '.results[] | "\(.id[0:16])\t\(.name[0:30])\t\(.state)\t\(.created_at[0:10])"' \
| column -t | head -15
echo ""
echo "=== Cloud Configurations ==="
anyscale_api GET "/clouds" \
| jq -r '.results[] | "\(.id[0:16])\t\(.name)\t\(.provider)\t\(.region)"' | head -10
Phase 2: Analysis
Service Health
#!/bin/bash
echo "=== Service Status Summary ==="
anyscale_api GET "/services?count=50" \
| jq -r '.results[] | .state' | sort | uniq -c | sort -rn
echo ""
echo "=== Running Services ==="
anyscale_api GET "/services?count=20&state=RUNNING" \
| jq -r '.results[] | "\(.name)\t\(.state)\t\(.current_version)\t\(.base_url[0:40])"' \
| column -t | head -15
echo ""
echo "=== Failed Services ==="
anyscale_api GET "/services?count=10&state=SYSTEM_FAILURE,UNHEALTHY" \
| jq -r '.results[] | "\(.name)\t\(.state)\t\(.status_message[0:60])"' | head -10
Job & Cluster Analytics
#!/bin/bash
echo "=== Job Status Summary ==="
anyscale_api GET "/jobs?count=100" \
| jq -r '.results[] | .state' | sort | uniq -c | sort -rn
echo ""
echo "=== Active Clusters ==="
anyscale_api GET "/sessions?count=20&state=RUNNING" \
| jq -r '.results[] | "\(.name)\t\(.state)\t\(.head_node_type)\t\(.num_workers) workers"' \
| column -t | head -10
echo ""
echo "=== Recent Failed Jobs ==="
anyscale_api GET "/jobs?count=10&state=FAILED" \
| jq -r '.results[] | "\(.id[0:16])\t\(.name[0:30])\t\(.created_at[0:10])\t\(.error_message[0:50] // "no error")"' \
| head -10
Output Format
=== Anyscale Account ===
Services: <n> Clusters: <n> Jobs: <n>
--- Service Health ---
Running: <n> Unhealthy: <n> Failed: <n>
--- Job Summary ---
Succeeded: <n> Running: <n> Failed: <n>
--- Clusters ---
Active: <n> Total Workers: <n>
Anti-Hallucination Rules
- NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
- NEVER fabricate metric names or dimensions — verify against the service documentation or
--helpoutput. - NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
- ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
- ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.
Counter-Rationalizations
| Shortcut | Counter | Why |
|---|---|---|
| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |
Common Pitfalls
- Service states:
STARTING,RUNNING,UPDATING,UNHEALTHY,SYSTEM_FAILURE,TERMINATED - Pagination: Use
countandpaging_tokenfor list endpoints - Rate limits: Check response headers for current rate limit status
- Cloud scoping: Resources are scoped to specific cloud configurations
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |