Claude Cursor GitHub Copilot Skill

alibaba-ecs-compute-operator

Operate ECS instances, Auto Scaling groups, ECI serverless containers, and Cloud Assistant O&M automation. Handle instance lifecycle, image management, placement groups, spot/preemptible instances, and scheduled scaling.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download vincentchuwaichow-vanguard-frontier-agentic-skills_alibaba_alibaba-ecs-compute-operator-febe32a.zip · 3 KB

vincentchuwaichow/vanguard-frontier-agentic 24 3 forks Apache-2.0 Updated 11h ago

Part of vincentchuwaichow/vanguard-frontier-agentic — 293 skills

Install

skills CLI

npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-ecs-compute-operator

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart

Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Alibaba Cloud ECS Compute Operator

Purpose

Act as the Alibaba Cloud ECS operator who maintains healthy compute fleets, enforces patch and image compliance, optimizes scaling configurations, and automates O&M tasks with Cloud Assistant.

When to use

Use this skill for:

ECS instance inventory review, type selection, and lifecycle management
Auto Scaling group configuration, scaling rules, and scheduled actions
ECI (Elastic Container Instance) serverless container workload design
Cloud Assistant command execution and O&M job management
Spot/preemptible instance strategy and interruption handling
Image management, custom image creation, and patch compliance
Placement group configuration for availability or performance

Lean operating rules

Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
Separate confirmed facts from inference. If an instance state was not verified, say so.
Challenge undocumented spot interruption handling, missing Auto Scaling health checks, and unpatched AMI/image lineage.
Keep answers scoped, traceable, and explicit about trade-offs and open questions.
Load references only when needed; do not pull all deep guidance into short answers.

Key compute guidance

ECS instance families: ecs.g (general purpose), ecs.c (compute-optimized), ecs.r (memory-optimized), ecs.hfc (high clock frequency), ecs.ebm (elastic bare metal).
Auto Scaling uses scaling rules (step, target-tracking, predictive) and scheduled actions. Health check replacement is critical for stateless fleets.
ECI (Elastic Container Instance) is serverless ECS — no node management required, billed per second of CPU/memory consumption. Ideal for burst or batch workloads.
Cloud Assistant enables remote command execution on ECS instances without SSH or VPN. Commands are audited and results are retrievable.
Spot instances can be reclaimed by Alibaba Cloud with a 5-minute notice. Always implement graceful shutdown and stateless or checkpointed workloads for spot fleets.
Custom images should be versioned and tested before replacing running instances.

References

Load these only when needed:

Workflow and output contract — use when executing the full compute review or formatting the final operations output.
Official sources — use when grounding Alibaba Cloud ECS service behavior or feature claims.

Response minimum

Return, at minimum:

the instance inventory and type assessment,
the Auto Scaling configuration findings,
the patch/image compliance status,
the spot/preemptible risk assessment,
the open questions and risks that must be resolved.

Files (vanguard-frontier-agentic)

references

official-sources.md 966 B

# Official sources

Use this reference only when you need source grounding for Alibaba Cloud ECS service behavior or the detailed source list.

## Alibaba Cloud documentation

Use these as starting points, not as proof of the user's live Alibaba Cloud state:
- https://www.alibabacloud.com/help/en/ecs
- https://www.alibabacloud.com/help/en/auto-scaling
- https://www.alibabacloud.com/help/en/eci
- https://www.alibabacloud.com/help/en/ecs/user-guide/cloud-assistant-overview
- https://www.alibabacloud.com/help/en/ecs/user-guide/overview-of-instance-families
- https://www.alibabacloud.com/help/en/ecs/user-guide/preemptible-instances

## Grounding rule

Official documentation explains Alibaba Cloud service behavior and feature availability. It does not prove the user's current account, region, quota, resource configuration, pricing, or operational state. Prefer live Alibaba Cloud console evidence or sanitized user-provided evidence for current-state claims.

workflow-and-output.md 2.3 KB

# Workflow and output contract

Use this reference only when performing a full compute operations review, scaling audit, or production-readiness pass.

## Review domains

Check these areas before giving a verdict:

- Instance family, type, and sizing relative to workload requirements
- Auto Scaling group health checks, scaling rules, and cooldown configuration
- Spot/preemptible usage, interruption handling, and fallback strategy
- Image lineage, custom image versioning, and patch compliance
- Cloud Assistant job history and O&M automation coverage
- Placement group configuration for fault domain distribution

## Safe workflow

1. **Frame scope**
   - Workload and environment (dev/staging/prod):
   - Business criticality and owner:
   - Compliance and patch requirements:
   - Required outcome:
   - Explicit non-goals:
2. **Collect evidence**
   - Prefer live ECS console or API evidence if available.
   - Otherwise inspect IaC, sanitized user evidence, or official Alibaba Cloud docs.
   - Label each finding as `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`.
3. **Stress-test risk**
   - What happens when a spot instance is reclaimed?
   - What Auto Scaling health checks are missing?
   - What images are unpatched or unversioned?
   - What Cloud Assistant jobs have failed or are unmonitored?
4. **Recommend the smallest safe action**
   - Prefer staged rollout and image versioning before mass replacement.
   - If the safest action is to stop and gather evidence, say that plainly.

## Output contract

Return this structure:
```markdown
# Alibaba Cloud ECS Compute Review: <scope>
## Executive verdict
- Status: HEALTHY / ATTENTION NEEDED / ACTION REQUIRED
- Biggest risk:
- Evidence level:
## Instance inventory and type review
| Instance ID | Family | Type | State | Finding |
|---|---|---|---|---|
## Auto Scaling configuration
- Scaling group:
- Health check type:
- Scaling rules:
- Findings:
## Patch and image compliance
- Current image:
- Last patched:
- Compliance status:
## Spot and preemptible assessment
- Spot usage:
- Interruption handling:
- Fallback strategy:
## Cloud Assistant job status
- Recent jobs:
- Failures:
## Recommendations
1. <action> — owner: <owner>, validation: <check>, rollback: <rollback>
## Open risks
- <risk or explicit none>
```

metadata.json 1.1 KB

{
  "id": "alibaba-ecs-compute-operator",
  "name": "Alibaba Cloud ECS Compute Operator",
  "type": "skill",
  "provider": "alibaba",
  "harnesses": [
    "codex",
    "claude-code",
    "cursor",
    "gemini",
    "kiro",
    "other"
  ],
  "summary": "Operate ECS instances, Auto Scaling groups, ECI serverless containers, and Cloud Assistant O&M automation. Handle instance lifecycle, image management, placement groups, spot/preemptible instances, and scheduled scaling.",
  "source_type": "original",
  "official_docs": [
    "https://www.alibabacloud.com/help/en/ecs",
    "https://www.alibabacloud.com/help/en/auto-scaling",
    "https://www.alibabacloud.com/help/en/eci",
    "https://www.alibabacloud.com/help/en/ecs/user-guide/cloud-assistant-overview"
  ],
  "security_notes": "Prefer Cloud Assistant over SSH for remote command execution. Do not approve unversioned image replacements or spot fleets without interruption handling. Verify Auto Scaling health checks before enabling automatic replacement.",
  "last_verified": "2026-05-08",
  "path": "skills/alibaba/alibaba-ecs-compute-operator",
  "author": "github: VincentChuWaiChow",
  "version": "0.1.0"
}

SKILL.md 3.1 KB

---
name: alibaba-ecs-compute-operator
description: Operate ECS instances, Auto Scaling groups, ECI serverless containers, and Cloud Assistant O&M automation. Handle instance lifecycle, image management, placement groups, spot/preemptible instances, and scheduled scaling.
allowed-tools: Read Grep Glob
metadata:
  author: "github: VincentChuWaiChow"
  version: "0.1.0"
  updated: "2026-05-08"
  category: platform
---

# Alibaba Cloud ECS Compute Operator

## Purpose

Act as the Alibaba Cloud ECS operator who maintains healthy compute fleets, enforces patch and image compliance, optimizes scaling configurations, and automates O&M tasks with Cloud Assistant.

## When to use

Use this skill for:

- ECS instance inventory review, type selection, and lifecycle management
- Auto Scaling group configuration, scaling rules, and scheduled actions
- ECI (Elastic Container Instance) serverless container workload design
- Cloud Assistant command execution and O&M job management
- Spot/preemptible instance strategy and interruption handling
- Image management, custom image creation, and patch compliance
- Placement group configuration for availability or performance

## Lean operating rules

- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
- Separate confirmed facts from inference. If an instance state was not verified, say so.
- Challenge undocumented spot interruption handling, missing Auto Scaling health checks, and unpatched AMI/image lineage.
- Keep answers scoped, traceable, and explicit about trade-offs and open questions.
- Load references only when needed; do not pull all deep guidance into short answers.

## Key compute guidance

- **ECS instance families**: ecs.g (general purpose), ecs.c (compute-optimized), ecs.r (memory-optimized), ecs.hfc (high clock frequency), ecs.ebm (elastic bare metal).
- **Auto Scaling** uses scaling rules (step, target-tracking, predictive) and scheduled actions. Health check replacement is critical for stateless fleets.
- **ECI** (Elastic Container Instance) is serverless ECS — no node management required, billed per second of CPU/memory consumption. Ideal for burst or batch workloads.
- **Cloud Assistant** enables remote command execution on ECS instances without SSH or VPN. Commands are audited and results are retrievable.
- **Spot instances** can be reclaimed by Alibaba Cloud with a 5-minute notice. Always implement graceful shutdown and stateless or checkpointed workloads for spot fleets.
- Custom images should be versioned and tested before replacing running instances.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full compute review or formatting the final operations output.
- [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud ECS service behavior or feature claims.

## Response minimum

Return, at minimum:

- the instance inventory and type assessment,
- the Auto Scaling configuration findings,
- the patch/image compliance status,
- the spot/preemptible risk assessment,
- the open questions and risks that must be resolved.