alibabacloud-flink-instance-manage — Claude Code skill
alibabacloud-flink-instance-manage is a Claude Code skill that creates and lists Alibaba Cloud Flink VVP instances and namespaces. It also checks regions, zones, and tags.
Apache-2.0 239 installs ★ 300 updated 2026-10-23
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a claude-codeWhat alibabacloud-flink-instance-manage does
This skill works with Flink VVP instances and namespaces on Alibaba Cloud, and it only creates or reads. Every call goes through python scripts/instance_ops.py <command>. The commands are create, create_namespace, describe, describe_regions, describe_zones, describe_namespaces and list_tags.
Both create commands refuse to run without --confirm. After a create, the skill reads the state back with describe or describe_namespaces instead of trusting the create response. Before adding a namespace it checks the instance status and what is already allocated. A new instance gets 10 minutes to reach RUNNING, then the chain stops.
You need the Python packages from assets/requirements.txt, working Alibaba Cloud credentials and network access to the Flink OpenAPI (2021-10-28). Aliyun CLI is optional. Updates and deletes are off the table, so removing an old instance happens elsewhere. If namespace creation fails with InsufficientResources, you scale the instance by hand.
What it helps with
- create a Flink instance in
cn-beijing - list the instances in a region with their status
- add a namespace to a running instance
- find out which regions and zones Flink supports
- look up tags on an instance or other resource
Example prompts for the agent
- List all Flink instances in cn-beijing with their status
- Create a namespace in Flink instance f-cn-xxx
- Which Flink zones are available in cn-beijing?
How to install alibabacloud-flink-instance-manage
1Skills CLI (Vercel)
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a claude-code2Manually: put the files in place
~/.claude/skills/alibabacloud-flink-instance-manage/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/alibabacloud-flink-instance-manage/
1Skills CLI (Vercel)
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a codex2Manually: put the files in place
.agents/skills/alibabacloud-flink-instance-manage/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a cursor2Manually: put the files in place
.cursor/skills/alibabacloud-flink-instance-manage/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aliyun/alibabacloud-aiops-skills skills/analyticscomputing/sc/alibabacloud-flink-instance-manage2Manually: put the files in place
.github/skills/alibabacloud-flink-instance-manage/SKILL.md1Skills CLI (Vercel)
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a gemini-cli2Platform CLI
gemini skills install https://github.com/aliyun/alibabacloud-aiops-skills --path skills/analyticscomputing/sc/alibabacloud-flink-instance-manageManually: put the files in place
.devin/skills/alibabacloud-flink-instance-manage/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about alibabacloud-flink-instance-manage
How do I install alibabacloud-flink-instance-manage in Claude Code?
Run npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-flink-instance-manage -a claude-code. The skill file lands in ~/.claude/skills/alibabacloud-flink-instance-manage/SKILL.md.
What does alibabacloud-flink-instance-manage do?
It creates and lists Flink VVP instances and their namespaces on Alibaba Cloud, and looks up regions, zones and tags. It does not update or delete anything, and it turns down Flink SQL and job requests.
What does the skill need to run?
The Python packages from assets/requirements.txt, valid Alibaba Cloud credentials and network access to the Flink OpenAPI. Aliyun CLI is only used for environment diagnostics.
Source text
SKILL.md · Apache-2.0
--- name: alibabacloud-flink-instance-manage description: > Manage Alibaba Cloud Flink VVP instances and namespaces through create/query operations only. Use when user asks to create or query Flink instances, namespaces, regions, zones, or tags in Chinese or English. Reject Flink SQL/job requests, unrelated cloud services (ECS/Kafka/OSS/DataWorks), and all update/delete operations. license: Apache-2.0 compatibility: > Requires Python dependencies from assets/requirements.txt, valid Alibaba Cloud credentials, and network access to Flink OpenAPI (2021-10-28). Aliyun CLI is optional and only used for environment diagnostics/credential inspection. metadata: domain: aiops owner: flink-team contact: [email protected] --- # 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: ```bash 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. ## Intent to Command Mapping | User intent | Command | |---|---| | Query all instances in a region | `describe --region_id <REGION>` | | Create instance | `create ... --confirm` | | Query namespaces under an instance | `describe_namespaces --region_id <REGION> --instance_id <ID>` | | Create namespace | `create_namespace ... --confirm` | | Query supported regions/zones | `describe_regions` / `describe_zones --region_id <REGION>` | | Query tags | `list_tags --region_id <REGION> --resource_type <TYPE> [--resource_ids ...]` | ## Operating Rules 1. **Confirmation is mandatory for create commands** - `create` and `create_namespace` must include `--confirm`. 2. **Verify create results with read-back** - Do not conclude success from create response alone. 3. **Retry policy is strict** - Maximum 2 attempts for the same command (initial + one corrected retry). 4. **No automatic operation switching** - If an operation fails, do not switch to a different operation without user approval. 5. **Lifecycle target lock** - In `create -> create_namespace` flow, namespace must target the same newly created `InstanceId` unless user approves fallback. 6. **Namespace pre-check is required** - Before `create_namespace`, check instance status/resources and existing namespace allocation. 7. **No secret exposure** - Do not output or request plaintext AK/SK. Use default credential chain guidance. 8. **Do not invent parameters** - Never fabricate VPC/VSwitch/instance IDs. 9. **Keep auditable confirmation evidence** - Lifecycle outputs must contain `SafetyCheckRequired` or explicit `--confirm` evidence. 10. **No partial-completion claims for lifecycle flows** - For flows requiring both `create` and `create_namespace`, overall status can be `completed` only when both create operations succeed. 11. **No automatic capacity scaling** - If `create_namespace` fails due to insufficient resources, report it clearly and ask user to manually scale resources outside this skill scope. ## Execution Protocol ### Step 1: Classify request - In-scope create/query for Flink instance/namespace/tag/region/zone -> continue. - Out-of-scope or non-Flink -> reject or route with explanation. ### Step 2: Validate parameters - Apply `references/parameter-validation.md`. - If required parameters are missing, ask user or return clear remediation. ### Step 3: Execute command - Query commands: run once unless transient query error. - Create commands: construct final command string and verify `--confirm` is present before execution. ### Step 4: Verify create outcomes - For `create`: verify with `describe --region_id <REGION>`. - For `create_namespace`: verify with `describe_namespaces --region_id <REGION> --instance_id <ID>`. - Use up to 3 read checks with short backoff before concluding the create is not reflected yet. - For chained `create -> create_namespace`: - poll `describe --region_id <REGION>` on the same `InstanceId` every 30 seconds - max wait: 10 minutes - if still not `RUNNING`, stop and provide next action (wait/retry later) - do not switch to another instance without explicit user approval - if namespace create fails, mark lifecycle chain as `failed`/`not_ready`, not `completed` - for `InsufficientResources`, ask user to manually scale the instance and retry later ## Key References - Start here: - `references/README.md` - `references/quick-start.md` - `references/trigger-recognition-guide.md` - `references/core-execution-flow.md` - `references/command-templates.md` | Document | Purpose | |----------|---------| | `references/parameter-validation.md` | Pre-execution validation checklist | | `references/e2e-playbooks.md` | Complete execution sequences | | `references/common-failures.md` | Typical mistakes and fixes | | `references/required-confirmation-model.md` | Confirmation gate rules | | `references/instance-state-management.md` | Instance state and readiness checks | | `references/output-handling.md` | Output parsing and retry policy | | `references/verification-method.md` | Verification patterns after create/query | | `references/acceptance-criteria.md` | Completion checklist for normal operations | | `references/python-environment-setup.md` | Python dependency and auth setup | | `references/cli-installation-guide.md` | Aliyun CLI diagnostics setup | | `references/ram-policies.md` | Required RAM permissions | | `references/related-apis.md` | API and command mapping | ## Output Format All commands return JSON: ```json { "success": true, "operation": "<command>", "confirmation_check": { "required_flag": "--confirm", "provided": true, "status": "passed" }, "data": {}, "request_id": "..." } ``` `confirmation_check` appears on create operations and is used for auditable safety evidence. Exit codes: `0` = success, `1` = error.
© aliyun · Apache-2.0 · aliyun/alibabacloud-aiops-skills