Loading...
Loading...
Found 25 Skills
Minimal TTS smoke test for Model Studio Qwen TTS.
Playwright E2E testing patterns. Trigger: When writing Playwright E2E tests (Page Object Model, selectors, MCP exploration workflow). For Prowler-specific UI conventions under ui/tests, also use prowler-test-ui.
Creates test documentation (testing-strategy.md + tests/README.md). Establishes testing philosophy and Story-Level Test Task Pattern. L2 Worker in ln-100-documents-pipeline workflow.
Smoke test for alicloud-media-video-translation. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-recommend-airec. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-entry-modelstudio-test. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-security-id-verification-cloudauth. Validate minimal authentication, API reachability, and one read-only query path.
Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test-result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports — without inventing facts. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Not for: general prose, blog, or marketing-copy cleanup — use the global humanizer skill. Not for: classifying or routing CI failures — use ai-bug-triage. Related: ai-bug-triage, qa-metrics, qa-dashboard, quality-postmortem.
Structure a freeform bug report into sections. Use in `prescribe` before `investigate`, or standalone whenever a raw bug report needs structuring.
Minimal routing smoke test for alicloud-ai-entry-modelstudio entry skill.
Minimal voice design TTS smoke test for Model Studio Qwen TTS VD.
Use when you need to produce a test-case suite for a feature, change, PR, or fixed bug — manual or automated — for delivery to Excel/xlsx, Markdown, CSV, or a tracker. Triggers on "write test cases", "create a test plan", "QA cases", "turn this spec/diff/bug into tests", or after a feature is built / a bug is fixed and before filing or sign-off. Every case is grounded in real evidence (docs, code, git, or the LIVE system); the skill refuses to invent values. Do NOT use to verify one already-finished task (that is dual-verifier), or to file findings as work items (that is the backlog plugins — this hands off to them).