Aliyun Ecs Spot Provision logo

Aliyun Ecs Spot Provision

Community
cinience
aliyun-ecs-spot-provision

Plan, price, provision, and verify one Alibaba Cloud ECS spot instance with minimal VPC networking, restricted SSH access, a managed key pair, configurable system-disk size, and optional scheduled release. Use when Codex must buy, launch, or reproduce a complete preemptible/spot ECS workflow rather than only manage an existing instance.

Overview

Publishercinience
Repositoryalicloud-skills
Skill namealiyun-ecs-spot-provision
Stars
397
Forks
34
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cinience on GitHub. Read the source before you install it.

Installation

Install the Aliyun Ecs Spot Provision AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/cinience/alicloud-skills/tree/main/skills/compute/ecs/aliyun-ecs-spot-provision
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cinience/alicloud-skills.git /tmp/alicloud-skills
mkdir -p .claude/skills
cp -r /tmp/alicloud-skills/skills/compute/ecs/aliyun-ecs-spot-provision .claude/skills/aliyun-ecs-spot-provision
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Aliyun Ecs Spot Provision in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Aliyun Ecs Spot Provision on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Aliyun Ecs Spot Provision is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Provision an Alibaba Cloud Spot ECS Instance

Use the bundled CLI wrapper to preserve the fragile ordering and evidence trail of a spot purchase. Keep account-specific IDs, IP addresses, image dates, and prices out of the skill.

Preconditions

  • Require Alibaba Cloud CLI v3 and credentials with least-privilege ECS and VPC permissions.
  • Treat plan as read-only and run it before every apply.
  • Obtain an explicit region. Obtain an explicit SSH source CIDR when public SSH is requested.
  • Explain that spot capacity and price can change between planning and creation.
  • Write all evidence beneath output/aliyun-ecs-spot-provision/<name>/.

Workflow

  1. Run plan to discover exact CPU/memory matches, select an available zone and instance type, resolve a current Ubuntu image, verify a disk category, and query the current hourly quote.
  2. Review plan.json. Report compute, disk, and fixed bandwidth prices separately; pay-by-traffic outbound transfer is not an hourly fixed charge.
  3. Run apply --confirm-create only after the requested region, size, disk, public bandwidth, SSH CIDR, and release behavior are settled.
  4. Let the script create or reuse a VPC, vSwitch, security group, and key pair. Never print or commit the private key.
  5. Require the RunInstances dry run to return DryRunOperation before submitting the real request.
  6. Verify the returned instance with DescribeInstances until it reaches Running.
  7. Report all created IDs, the private-key path, current quote, verification evidence, and remaining interruption/data-retention risks.

Do not automatically delete partially created infrastructure after an error. Preserve state.json, diagnose, and resume with the same command so resource IDs are reused.

Commands

Read-only plan:

bash
python3 skills/compute/ecs/aliyun-ecs-spot-provision/scripts/provision_spot_ecs.py plan \
  --name batch-worker \
  --region ap-southeast-8 \
  --cpu 8 \
  --memory-gib 16 \
  --system-disk-size 800 \
  --internet-bandwidth-out 5 \
  --ssh-cidr 203.0.113.10/32

Create exactly one instance from the saved plan:

bash
python3 skills/compute/ecs/aliyun-ecs-spot-provision/scripts/provision_spot_ecs.py apply \
  --name batch-worker \
  --region ap-southeast-8 \
  --cpu 8 \
  --memory-gib 16 \
  --system-disk-size 800 \
  --internet-bandwidth-out 5 \
  --ssh-cidr 203.0.113.10/32 \
  --confirm-create

Prefer --instance-type and --zone when the user chooses an exact offer. Use --auto-release-time for a true scheduled release; --spot-duration 1 is only a one-hour protection period.

Safety Rules

  • Never infer 0.0.0.0/0 for SSH. Require an explicit CIDR for public SSH.
  • Default public bandwidth to zero. A public IP is requested only when --internet-bandwidth-out is positive.
  • Generate a new RSA private key with mode 0600; fail instead of overwriting an existing key.
  • Use automatic spot bidding by default. Use --spot-price-limit only when the user supplies a maximum hourly compute price.
  • Set the system-disk size during creation. For resizing an existing disk and filesystem, use aliyun-ecs-manage instead.
  • Warn that a system disk created with the instance is normally released with a reclaimed spot instance.
  • Never equate ExpiredTime=2099... or SpotDuration=1 with a scheduled deletion.

References

Read references/operations.md when diagnosing partial creation, interpreting prices, configuring release behavior, or validating the guest filesystem. See references/sources.md for the official ECS and VPC documentation checked for this skill.

Output And Evidence

  • Save the resolved request and current quote to output/aliyun-ecs-spot-provision/<name>/plan.json.
  • Save every CLI response and error stream beside the plan using operation-specific names.
  • Save created resource IDs and recovery state to state.json; save the final normalized result to summary.json.
  • Store generated private keys only below the evidence directory's private/ folder with directory mode 0700 and key mode 0600.
  • Never copy private keys, AccessKeys, or credential files into reports or committed fixtures.

Validation

bash
python3 -m py_compile skills/compute/ecs/aliyun-ecs-spot-provision/scripts/provision_spot_ecs.py
python3 skills/compute/ecs/aliyun-ecs-spot-provision/scripts/provision_spot_ecs.py --help
python3 /home/vipas/.codex/skills/.system/skill-creator/scripts/quick_validate.py \
  skills/compute/ecs/aliyun-ecs-spot-provision

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Aliyun Ecs Spot Provision AI skill do?

Plan, price, provision, and verify one Alibaba Cloud ECS spot instance with minimal VPC networking, restricted SSH access, a managed key pair, configurable system-disk size, and optional scheduled release. Use when Codex must buy, launch, or reproduce a complete preemptible/spot ECS workflow rather than only manage an existing instance.

Why use Aliyun Ecs Spot Provision on TypingMind?

Because you install it once and use it with any model. Aliyun Ecs Spot Provision is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Aliyun Ecs Spot Provision in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cinience/alicloud-skills/tree/main/skills/compute/ecs/aliyun-ecs-spot-provision. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Aliyun Ecs Spot Provision?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Aliyun Ecs Spot Provision?

As many as you like. As long as a model supports skills, you can use Aliyun Ecs Spot Provision with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Aliyun Ecs Spot Provision AI skill free?

Yes. It is published on GitHub by cinience under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇