About this skill

What It Solves

CTyun console and OpenAPI calls are scattered, so checking instance IDs, security groups, EIPs, bills, and monitoring items can become manual. This skill wraps common APIs into executable commands for terminal-based resource lookup, status checks, billing review, and routine operations.

Core Capabilities And Usage

Resource management: Covers ECS, VPC, EBS, ELB, CCE, Redis, RDS, and Kafka, with commands for instances, subnets, routes, security groups, nodes, listeners, and clusters.
Monitoring and billing: Supports metric data, alert rules, alert history, bill details, transaction bills, and pricing queries for capacity and cost checks.
Output and debugging: Use --output json for scripting, --debug for request inspection, and --profile for environment-specific configurations.
Security and auth: Prefer environment variables for access key and secret key instead of embedding credentials in commands.

Limits To Know

The command set is query-heavy and suited to day-to-day operations; write actions depend on specific subcommands.
Many commands require explicit resource IDs such as instance-id, vpc-id, or cluster-id.
For large inventories, add pagination, filters, or JSON output to avoid fetching too much data at once.

Screenshots

Use Cases

Investigate ECS, VPC, security groups, EIPs, and NAT status to verify network and instance configuration.
Check Redis instances, nodes, backups, logs, and metrics to troubleshoot cache service issues.
Review bill details, transaction bills, and pricing queries to reconcile costs and estimate capacity.
Inspect CCE clusters, nodes, Pods, Deployments, and Services to validate application runtime status.

Best For

Operations engineers responsible for routine CTyun inspection and incident diagnosis
Platform engineers querying cloud resource status and billing data from scripts
SREs managing Redis, CCE, and ELB resources while verifying configurations
Cloud administrators switching multi-environment credentials and debugging commands