Agent skill · aliyun
alibabacloud-lingjun-node-ops
Manage Alibaba Cloud Lingjun (hyper-)node full-lifecycle ops: stop/reboot/reimage, subscription renewal (bssopenapi renew-instance), spec change (change-node-types), repair (report-node-status/approve-operation), run-command, node-group default update, tag/untag, change-resource-group, plus read-only inventory prerequisite (list-cluster-nodes/describe-node/list-cluster-hyper-nodes). change-node-group & send-file out of scope (see alibabacloud-lingjun-cluster-scaling). Triggers: "lingjun node ops", "灵骏节点运维", "节点停机", "stop nodes", "节点重启", "reboot nodes", "节点重装", "reimage nodes", "节点续费", "renew lingjun node", "节点规格修改", "change node types", "节点维修", "report node status", "节点执行命令", "run command", "节点分组更新", "update node group", "节点打标", "tag node", "节点资源转组", "change node resource group".
What it needs
About 10k tokens when loaded.
What this skill does
Alibaba Cloud Lingjun Node Operations (Full Lifecycle) Scenario Description Cover the post-provisioning day-to-day operations of Lingjun regular nodes (NodeId) and rack-level hyper-nodes (HyperNodeId). Provisioning/expansion/shrink/release is out of scope here - see the sister skill alibabacloud-lingjun-cluster-scaling. This skill focuses on 9 capability areas / 22 use cases (node-to-group move change-node-group and file delivery send-file are out of scope): # Capability Mutating CLI Sync/Async Reversible --- --- --- --- --- F1 Node Stop stop-nodes Async (TaskId) Yes (start later via reboot) F2 Node Reboot reboot-nodes Async (TaskId) N/A F3 Node Reimage reimage-nodes Async (TaskId) No (data loss) F4 Node Renew bssopenapi renew-instance Sync (OrderId) No (paid) F5 Node Spec Change change-node-types Async (TaskId) Yes (re-issue) F6 Repair report-node-status + approve-operation Sync N/A F7 Run Command run-command (+ describe-invocations / stop-invocation) Async (InvokeId) N/A F8 Node Group Update update-node-group (group default) Sync Yes F9 Tag & Resource Group tag-resources / untag-resources / change-resource-group Sync Yes Canonical Chinese feature names (MANDATORY in zh sessions) - the authoritative zh rendering strings live in lib/core/i18n.sh (render.feat.F1..render.feat.F9 keys, rendered via ljt); the agent must use them verbatim and never free-translate (e.g. F5 must never be rendered with a non-canonical synonym). The F1-F9 codes themselves are internal documentation indices - never show them in any user-facing output (confirmation-table titles, operation names, submission receipts, progress lines, final reports): write the canonical feature name plus the CLI name in parentheses, never the F-code; they may appear only in capability-overview tables that enumerate all features. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aliyun/alibabacloud-lingjun-node-ops