/alibabacloud-pts-pilot

name: alibabacloud-pts-pilot
description: Router skill for Alibaba Cloud PTS (Performance Testing Service) operations. Resolves the user's PTS intent and delegates execution to the appropriate sub-skill. Itself does NOT execute any CLI / API / business logic. Triggers "PTS", "压测", "性能测试", "stress testing", "performance testing", "JMeter", "load testing", "压测调优".

alibabacloud-pts-pilot — PTS Operations Router

> **[MUST] Role Declaration — What I Do** > I am a **router-only** skill. My ONLY job: > 1. **Parse** user intent → **Match** to a sub-skill → **Call the Skill tool** to delegate. > 2. That's it. I never execute CLI, shell, or API commands myself. > > **My ONLY permitted action**: Call the **Skill tool** with the matched sub-skill name. > If a sub-skill is unavailable, I inform the user and stop — I never attempt manual execution.

---

Family Layout & Installation

This skill ships as a **parent-child bundle** in a single ZIP named after the parent (`alibabacloud-pts-pilot.zip`). To comply with Qoder's skill-loader contract (the ZIP root MUST directly contain a `SKILL.md`), the parent's `SKILL.md` sits at the ZIP root, and the two sub-skill folders sit beside it as peer directories. Qoder's recursive scan then registers all three `SKILL.md` files under a flat namespace.

alibabacloud-pts-pilot.zip
├── SKILL.md                    ← parent router (this file) — at ZIP root, required by Qoder
├── references/
│   └── routing-rules.md
├── alibabacloud-pts-task/               ← sub-skill (CRUD worker), peer of parent SKILL.md
│   ├── SKILL.md
│   └── references/             (acceptance-criteria, cli-installation-guide,
│                                 pts-scene-json-reference, ram-policies,
│                                 related-apis, verification-method)
└── alibabacloud-pts-reporter/           ← sub-skill (read-only PTS report analyzer), peer of parent SKILL.md
    ├── SKILL.md
    └── references/             (cli-installation-guide, ram-policies,
                                  report-analysis-knowledge-base)

**Installation (manual import):** 1. In Qoder, use "Import Skill ZIP" and point it at `alibabacloud-pts-pilot.zip`. Qoder will load the parent `SKILL.md` (this file) as the `alibabacloud-pts-pilot` skill. 2. After import, Qoder's recursive scan will also discover `alibabacloud-pts-task/SKILL.md` and `alibabacloud-pts-reporter/SKILL.md` as independent skills registered by their own `name:` field. 3. Trigger the parent by any PTS-related phrase (see frontmatter `Triggers`); the router will pick the correct sub-skill and hand off via the `Skill` tool.

> **Why this layout?** Qoder's loader requires `SKILL.md` at the ZIP root; it will reject ZIPs whose root contains only folders. Nesting sub-skills under an extra wrapper folder (e.g. `alibabacloud-pts-pilot/alibabacloud-pts-pilot/SKILL.md`) breaks this contract. Keeping the parent `SKILL.md` at the root while placing sub-skill folders as peers is the only layout that satisfies both the Qoder loader and the "one bundle, named after the parent" distribution requirement.

> **Integrity check after unzip**: the ZIP root must contain `SKILL.md` (parent) plus two sibling folders (`alibabacloud-pts-task/`, `alibabacloud-pts-reporter/`) each holding their own `SKILL.md`. Do not rename the folders — sub-skill `name:` fields must stay aligned with the delegation strings used in the Sub-Skill Registry below.

---

Sub-Skill Registry

| Sub-Skill | Status | Intent Signature | Positive Triggers (examples) | Negative Triggers (DO NOT route here) | Handoff | |-----------|--------|------------------|------------------------------|---------------------------------------|---------| | **alibabacloud-pts-task** | ✅ Active | CRUD actions on PTS scenarios: create / query / start / stop / report / delete, JMeter upload & run | "create scenario", "start stress-test", "stop stress-test", "view report", "delete scenario", "upload JMeter script", "list PTS scenes", "start scene" | Pure knowledge Q&A ("what is PTS"), tuning advice ("how to tune parameters") | Invoke Skill tool with `alibabacloud-pts-task`, pass resolved `{intent, RegionId, SceneId?, sceneConfig?}` | | **alibabacloud-pts-reporter** | ✅ Active | Read-only report analysis — interpret PTS report metrics, identify report-observable bottleneck patterns | "analyze stress-test report", "interpret report", "stress-test result analysis", "explain metrics", "PTS report analysis" | CRUD operations (create/start/stop), instance-level cloud product diagnosis | Invoke Skill tool with `alibabacloud-pts-reporter`, pass resolved `{RegionId, HistoryReportId, SceneId?, TopN?}` (HistoryReportId required) | | **alibabacloud-find-skills** | ✅ Active | Search / discover / install Alibaba Cloud agent skills; also triggered when user wants product-level diagnosis tools that this router cannot provide | "search alicloud skill", "any skill for PTS management", "find alicloud skills", "browse skill marketplace", "help me find a skill", "any skill for RDS/ECS/Redis diagnosis", "after bottleneck found, find product skill", "any tool for diagnosing RDS", "find database diagnostic tool", "deep-diagnose product after bottleneck" | PTS CRUD / report analysis / any concrete execution | Invoke Skill tool with `alibabacloud-find-skills`, pass user's search intent as-is |

> **Registry column semantics** > - **Status**: ✅ Active = ready to delegate · 🚧 Planned = reserved slot, not yet implemented > - **Intent Signature**: one-line semantic fingerprint used for matching > - **Positive / Negative Triggers**: concrete phrases that MUST / MUST NOT route here > - **Handoff**: exact delegation mechanism + minimum required context to pass in

---

Sub-Skill Contracts

Every active sub-skill declares an explicit **Input / Output Contract**. The router passes whatever the user explicitly provided — it does NOT need to gather every field or construct complex objects (like `sceneConfig`). Let the sub-skill ha