Alibaba Cloud Tair DevToolset — full-lifecycle Tair (Redis-compatible) database operations (short listing)

Prerequisites: an Alibaba Cloud account with billed Tair usage (no usable free tier); aliyun CLI >= 3.3.3; jq installed; RAM account with the required R-KVStore permissions (see the repo's references/ram-policies.md) Install "Alibaba Cloud Tair DevToolset — full-lifecycle Tair database operations (short listing)" for me. It gives my agent @aliyun's official Tair development workflow: choose the right architecture (Standard vs Cluster, memory/persistent-memory/disk editions), design Redis and Tair extended data structures, create and configure Tair instances via the aliyun CLI, manage connections (standalone/proxy/cluster/TLS), run performance monitoring and error troubleshooting, and configure backups with point-in-time recovery. IMPORTANT: the license terms were not verifiable (the discovery manifest records no license) — fetch from the link only, reproduce nothing beyond the link, and read the terms yourself before use. Repository: https://github.com/aliyun/alibabacloud-aiops-skills/blob/main/skills/database/kvstore/alibabacloud-tair-devtoolset/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code — credentials only via the existing aliyun CLI profile, never echoed or pasted. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "alibabacloud-tair-devtoolset". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. verify aliyun CLI >= 3.3.3 and jq are installed, confirm RAM permissions per references/ram-policies.md, and confirm every parameter with me before any command runs — restores overwrite data and cannot be undone). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.