Writing Livekit Scenarios
livekit-examples/agent-starter-python
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.
A skill your agent uses when you need to design performance testing for load, stress, spike, endurance, or capacity objectives; triggers include 性能测试 and performance testing.
Install Performance Testing
$ npx skills add naodeng/awesome-qa-skills --skill performance-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install naodeng/awesome-qa-skills performance-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/zh/testing-types/performance-testing .claude/skills/performance-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "performance-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testing into .claude/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add naodeng/awesome-qa-skills --skill performance-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install naodeng/awesome-qa-skills performance-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/zh/testing-types/performance-testing .agents/skills/performance-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "performance-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testing into .agents/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add naodeng/awesome-qa-skills --skill performance-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install naodeng/awesome-qa-skills performance-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/zh/testing-types/performance-testing .cursor/skills/performance-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "performance-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testing into .cursor/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/naodeng/awesome-qa-skills.git --path skills/zh/testing-types/performance-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add naodeng/awesome-qa-skills --skill performance-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install naodeng/awesome-qa-skills performance-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/zh/testing-types/performance-testing .gemini/skills/performance-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "performance-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testing into .gemini/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install naodeng/awesome-qa-skills performance-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add naodeng/awesome-qa-skills --skill performance-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/zh/testing-types/performance-testing .github/skills/performance-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "performance-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testing into .github/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add naodeng/awesome-qa-skills --skill performance-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install naodeng/awesome-qa-skills performance-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/zh/testing-types/performance-testing .opencode/skills/performance-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "performance-testing" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/zh/testing-types/performance-testing into .opencode/skills/performance-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "performance-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
performance-testing- GitHub stars
- 243
- Token cost
- ~317 tokens
- SKILL.md length
- 65 words
- Files
- 49 (incl. scripts, references)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when you need to design performance testing for load, stress, spike, endurance, or capacity objectives; triggers include 性能测试 and performance testing.
- Works in 4 steps: 阅读并遵循「按需加载」中的主提示词（覆盖清单、输出结构、质量要求）。 → 只补充真正影响结果的项目上下文：范围、环境、限制、风险、依赖、期望产出。 → 信息不全时先给可用初版，并显式标出假设与信息缺口。 → …
- You need to design performance testing for load
- SKILL.md covers 何时使用, 执行流程, 核心约束 and 按需加载, plus 2 more sections
- Runs JavaScript and Shell scripts from its folder
What it does
Performance Testing is an agent skill from naodeng/awesome-qa-skills. Use this skill when you need to design performance testing for load, stress, spike, endurance, or capacity objectives; triggers include 性能测试 and performance testing.
Its SKILL.md is about 320 tokens, which your agent loads only when the skill is triggered. The skill folder holds 54 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `evals/cases/basic-success.yaml`).
It sits in Testing & QA, covering Load testing. The repository describes itself as: Awesome QA Skills is an open-source AI-native Quality Engineering skill system that helps engineering teams reason about, design, execute, evaluate, and continuously improve…
When your agent uses it
- You need to design performance testing for load
- Capacity objectives
- Triggers include 性能测试 and performance testing
Example prompts
- “/performance-testing”
Requirements
- Node.js
- A Bash shell
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 阅读并遵循「按需加载」中的主提示词（覆盖清单、输出结构、质量要求）。
- 只补充真正影响结果的项目上下文：范围、环境、限制、风险、依赖、期望产出。
- 信息不全时先给可用初版，并显式标出假设与信息缺口。
- 默认 Markdown；用户指定其他格式时再切换。
What it can do on your machine
Read from SKILL.md and the folder at commit 52c4eaf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript and Shell, from the files we listed), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Performance Testing loads about 317 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 65 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 65 words (~317 tokens).
- name
- performance-testing
Files
SKILL.md and 48 other files (scripts, references) in skills/zh/testing-types/performance-testing of naodeng/awesome-qa-skills.
- SKILL.md
- README.md
- agents/openai.yaml
- evals/cases/basic-success.yaml
- evals/cases/edge-domain-boundary.yaml
- evals/cases/edge-incomplete-input.yaml
- evals/eval.yaml
- examples/k6-load-testing/README.md
- examples/k6-load-testing/run-tests.sh
- examples/k6-load-testing/scripts/api-test.js
- examples/k6-load-testing/scripts/load-test.js
- examples/k6-load-testing/scripts/spike-test.js
- examples/k6-load-testing/scripts/stress-test.js
- output-formats.md
- output-templates
- … and 34 more
Open the folder on GitHubat commit 52c4eaf
Compare with similar skills
Performance Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Performance Testing this skillnaodeng/awesome-qa-skills | 243 | — | ~317 | Automated safety check: Pass | Custom licence | |
| Writing Livekit Scenarioslivekit-examples/agent-starter-python | 264 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Go Testingcxuu/golang-skills | 170 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Goalcraftgrp06/goalcraft | 102 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Thinking Partnermattnowdev/thinking-partner | 205 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Challengeblueberrycongee/termcanvas | 406 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Go Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
Goalcraft
grp06/goalcraft
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.
Thinking Partner
mattnowdev/thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
Challenge
blueberrycongee/termcanvas
Adversarial review skill. An agent skill from blueberrycongee/termcanvas.
Vision
kunchenguid/vision
Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.
More from naodeng/awesome-qa-skills
All 61 skills in this repoAccessibility Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.
API Test Bruno
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.
API Test Pytest
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Pytest API automation; triggers include Pytest API tests and API automation with Pytest.
API Test Restassure
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Rest Assured Java test classes; triggers include Rest Assured, RestAssured, and Java API automation.
API Test Supertest
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate executable Supertest scripts; triggers include Supertest, Node.js API testing, and Supertest automation.
API Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
Related
Categories
Questions about Performance Testing
What does Performance Testing do?
A skill your agent uses when you need to design performance testing for load, stress, spike, endurance, or capacity objectives; triggers include 性能测试 and performance testing. Performance Testing is an agent skill from naodeng/awesome-qa-skills. Use this skill when you need to design performance testing for load, stress, spike, endurance, or capacity objectives; triggers include 性能测试 and performance testing.
When should I use Performance Testing?
Performance Testing fits situations like: you need to design performance testing for load; capacity objectives; triggers include 性能测试 and performance testing.
How do I install Performance Testing in Claude Code?
Run `npx skills add naodeng/awesome-qa-skills --skill performance-testing -a claude-code`. Or copy the skill folder (skills/zh/testing-types/performance-testing in naodeng/awesome-qa-skills) into .claude/skills/performance-testing in your project. Claude Code loads it when a task matches its description.
How do I install Performance Testing in Codex?
Run `npx skills add naodeng/awesome-qa-skills --skill performance-testing -a codex`. Or copy the skill folder (skills/zh/testing-types/performance-testing in naodeng/awesome-qa-skills) into .agents/skills/performance-testing in your project. Codex loads it when a task matches its description.
Can I use Performance Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add naodeng/awesome-qa-skills --skill performance-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/performance-testing, .gemini/skills/performance-testing, .github/skills/performance-testing and .opencode/skills/performance-testing in your project.
What does Performance Testing need to run?
Going by SKILL.md and its folder, Performance Testing needs JavaScript and a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell.
Does Performance Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Performance Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Performance Testing use?
Performance Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Performance Testing use?
About 317 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 869 tokens, read only when the agent opens those files.
What are the alternatives to Performance Testing?
Skills that share tags, products or a category with Performance Testing: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 170 stars), Goalcraft (grp06/goalcraft, 102 stars) and Thinking Partner (mattnowdev/thinking-partner, 205 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Performance Testing?
naodeng (a GitHub user) maintains it in naodeng/awesome-qa-skills, which has 243 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 26, 2026.
Source: naodeng/awesome-qa-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.