qianwenai-operate

Original：🇨🇳 Chinese

Translated

Diagnose why an application deployed by qianwenai-deploy to the Aliyun China site (aliyun.com) is unavailable or significantly slower, and perform a safe recovery only after the user explicitly confirms it. Read the .qianwenai-deploy state file in the project directory to identify ECS (and optionally RDS MySQL) resources, begin with minimal read-only diagnostics, and then propose only one recovery action at a time (starting the ECS instance, restarting the application service, or reloading Nginx), explaining the impact and obtaining confirmation before each action. Use cases: the user says the application will not open / returns 502 / cannot connect to the database, or requests a restart and confirmation that the application has recovered. Do not use: there is no .qianwenai-deploy state file; the target is the Aliyun International site (use qwencloud-operate); or the user only wants a status/cost overview (use qianwenai-observe).

5installs

Sourceqianwen-ai/qianwenai-deploy

Added on2026-09-18

NPX Install

npx skill4agent add qianwen-ai/qianwenai-deploy qianwenai-operate

SKILL.md Content (Chinese)

View Translation Comparison →

Qwen AI Operations

Performs fault diagnosis and confirmation-based recovery for applications deployed by

qianwenai-deploy

on the Aliyun China site. Diagnostics are read-only and require no confirmation; any action that changes cloud resources or the application runtime state requires explicit confirmation.

Interaction Flow

text

Identify the application and resources
→ Minimal diagnostics (read-only)
→ Present the cause, evidence, and recommended action
→ Explain the impact and request confirmation
→ Execute one recovery action
→ Verify the application, ECS, and RDS
→ Return the results and audit information
→ Propose re-scoring via qianwenai-observe (before recovery → after recovery)

Interaction Format

Read-only information (diagnostics, causes, evidence, verification results): plain text, with one line of evidence after each finding (metrics, status, RequestId).
State-changing actions (starting or stopping ECS, restarting the application, reloading Nginx, or any other write call): first use AskUserQuestion and clearly state what will be done · the impact (downtime/irreversibility) · how it will be verified. Do not execute before confirmation; propose only one recovery action at a time.
Proactive discipline: after recovery, if the result is normal, wrap up quietly; only proactively present a next step when risks remain or recovery has not succeeded, allowing the user to choose.

Scope

In Scope	Out of Scope
Applications deployed by `qianwenai-deploy` (state file exists)	Applications without a `.qianwenai-deploy` state file
A single ECS, or ECS + RDS MySQL 8.0	Other topologies / self-managed servers
Diagnostics + confirmation-based recovery (starting ECS, restarting the application, reloading Nginx)	Destructive data operations, scaling, configuration restructuring
Locating application-layer errors (which layer is broken and what error occurred)	Source-code review, finding bugs/vulnerabilities, determining which line of code is incorrect, modifying code
Aliyun China site	International site → use `qwencloud-operate`

Code Issues Are Outside This Skill's Scope

This skill handles infrastructure and runtime failures; it does not perform source-code review, defect localization, or code modification. Diagnostics can identify application-layer errors and what was reported, helping narrow down the problem, but the skill does not determine which line of code is incorrect or modify code.

When code is involved, explicitly inform the user that code modification is outside this skill's scope. The user must decide whether and how to make the changes and bears the corresponding consequences. Do not include any code changes in a recovery action.

Prerequisites

Aliyun CLI:
aliyun version
(3.x required). All commands use the native camelCase form to call OpenAPI directly and do not depend on plugins. Use
aliyun configure list
only to view credential status. Never read, echo, print, or request AK/SK/Token. If there is no valid configuration set → stop and ask the user to configure credentials outside this session. See
references/cli_installation_guide.md
.

How to Proceed

Identify the application — identify the application from
```
.qianwenai-deploy
```
. See workflow.
Diagnose (read-only, no confirmation required) — determine which layer is broken, the likely cause, the evidence, and how to proceed. See diagnose.
Recover one thing at a time, and confirm first. Select the action that matches the diagnosis, show the user its impact, obtain consent, and then execute only that action:
- Start a stopped server → recover-ecs
- Reboot a hung server → recover-reboot
- Restart the application service → recover-app
- Reload Nginx after
```
nginx -t
```
  passes → recover-nginx
- Rebind an EIP after it has been unbound → recover-eip
- Allow inbound traffic on security group ports 80 / 443 → recover-securitygroup
- Database-related issues → recover-rds
- The root partition is nearly full / remains insufficient after cleanup and needs expansion → recover-disk
Verify whether the application has recovered, then record what was done. See workflow.

Rules for Safe Recovery

Diagnostics are read-only; recovery uses only a small set of known-safe commands.
Confirm with the user before any state-changing action. If canceled, nothing is changed.
Perform one action at a time, verify it, and then decide on the next step—never combine multiple recovery steps.
Recovery actions can be safely repeated.
If a timeout, permission error, or unexpected state change occurs, stop before the next modification.
Passwords, Tokens, and complete connection strings must never appear in audit records or conversations.

Before any change, the confirmation information must tell the user: which resource will be affected, what action will be performed, whether the application will be briefly interrupted, whether the version will change, whether new charges will be incurred, and how the result will be verified (including what happens if verification fails).

Required Permissions

See

references/ram_policies.md

. Read-only:

ecs:DescribeInstances

,

ecs:DescribeInvocations

,

ecs:DescribeSecurityGroupAttribute

,

ecs:DescribeDisks

,

vpc:DescribeEipAddresses

, and RDS describe/performance/slow-log operations. Write operations (recovery):

ecs:StartInstance

,

ecs:RebootInstance

,

ecs:AuthorizeSecurityGroup

,

ecs:ResizeDisk

,

vpc:AssociateEipAddress

, and

ecs:RunCommand

(whitelisted recovery commands only).

More Details

The step-by-step guide has already been linked above under How to Proceed. Additional references include:

CLI Configuration — installation and credential checks.
CLI Troubleshooting Quick Reference — common pitfalls involving parameter forms, time formats, and response parsing.
RAM Permissions — permissions required by this skill.