Alibabacloud Flink Instance Manage

This wraps Alibaba Cloud's Flink VVP instance management into a single Python script that strictly handles create and query operations. It's built for AIOps workflows where you need to spin up Flink instances and namespaces or check their status, but deliberately excludes updates, deletes, and anything job or SQL related. The documentation is heavy on guardrails: mandatory confirmation flags for creates, read-back verification after every operation, and a two-retry limit to prevent runaway automation. If you're managing Flink infrastructure programmatically and need predictable, auditable instance lifecycle operations without touching the runtime layer, this gives you that narrow scope with training wheels on.

skills.sh installs: 237
GitHub stars: 289
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage --agent claude-code

Installs into .claude/skills of the current project.

Files

Alibaba Cloud Flink Instance Manage

Operate Alibaba Cloud Flink VVP resources with a strict create/query scope through one wrapper script.

Scope and Entrypoint

Always run operations through:

python scripts/instance_ops.py <command> [options]

Allowed commands: create, create_namespace, describe, describe_regions, describe_zones, describe_namespaces, list_tags
Out of scope: update/delete, Flink SQL/job runtime operations, and non-Flink services

Trigger Rules

Use this skill when prompts are about Flink instance/namespace lifecycle operations.

Positive intent examples:
- "Create a Flink instance in cn-beijing"
- "List Flink instances and status"
- "Describe namespaces for instance f-cn-xxx"
- "查询 Flink 实例标签"
- "Flink 可用区有哪些"
Negative intent examples:
- ECS/Kafka/OSS/DataWorks operations
- Generic questions (weather, translation, etc.)
- Flink SQL / Flink job authoring or runtime tuning
Ambiguous prompts:
- Ask one clarification question: instance/namespace management vs SQL/job operations.