Agent skill

Testing Perf

by yonatangross in yonatangross/orchestkit

Performance and load testing patterns — k6 load tests, Locust stress tests, pytest execution optimization (xdist parallel, plugins), test type classification, and performance benchmarking.

MITAuto-check passedTesting & QA

Install Testing Perf

skills CLI
$ npx skills add yonatangross/orchestkit --skill testing-perf -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yonatangross/orchestkit testing-perf --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/testing-perf .claude/skills/testing-perf && rm -rf skills-src

Use ~/.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/

Facts

Skill name
testing-perf
GitHub stars
289
Token cost
~1.6k tokens
SKILL.md length
397 words
Files
15 (incl. scripts, references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Performance and load testing patterns — k6 load tests, Locust stress tests, pytest execution optimization (xdist parallel, plugins), test type classification, and performance benchmarking.

  • Writing load tests
  • SKILL.md covers Quick Reference, k6 Quick Start, Performance Test Types and pytest Parallel Execution, plus 4 more sections
  • Calls pytest
  • Optimizing test execution speed

What it does

Testing Perf is an agent skill from yonatangross/orchestkit. Performance and load testing patterns — k6 load tests, Locust stress tests, pytest execution optimization (xdist parallel, plugins), test type classification, and performance benchmarking. Use when writing load tests, optimizing test execution speed, or setting up pytest infrastructure.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including scripts and reference files (for example `checklists/performance-checklist.md`, `checklists/pytest-production-checklist.md` and `references/custom-plugins.md`). Compatibility notes: Claude Code 2.1.277+.

It sits in Testing & QA, covering Load testing. It works with pytest. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.

When your agent uses it

  • Writing load tests
  • Optimizing test execution speed
  • Setting up pytest infrastructure

Example prompts

  • “/testing-perf”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Claude Code 2.1.277+.
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch

What it can do on your machine

Read from SKILL.md and the folder at commit 0ef71d2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • pytest

    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.

  • Compatibility

    Claude Code 2.1.277+.

    From compatibility in the SKILL.md frontmatter.

Context cost

Testing Perf loads about 1.6k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 397 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.3k

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

The full file from yonatangross/orchestkit at commit 0ef71d2, republished under its MIT licence (© yonatangross). 397 words, ~1,593 tokens.

Download SKILL.mdSave it as .claude/skills/testing-perf/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
testing-perf
description
Performance and load testing patterns — k6 load tests, Locust stress tests, pytest execution optimization (xdist parallel, plugins), test type classification, and performance benchmarking. Use when writing load tests, optimizing test execution speed, or setting up pytest infrastructure.
allowed-tools
Read, Glob, Grep, WebFetch, WebSearch
compatibility
Claude Code 2.1.277+.
license
MIT
user-invocable
false
disable-model-invocation
false
metadata.owner-agent
test-generator
metadata.category
document-asset-creation
metadata.version
2.1.0
metadata.author
OrchestKit
metadata.complexity
medium
metadata.tags
testing, performance, k6, locust, pytest, load-testing, benchmarking

Performance & Load Testing Patterns

Focused skill for performance testing, load testing, and pytest execution optimization. Covers k6, Locust, pytest-xdist parallel execution, custom plugins, and test type classification.

Quick Reference

AreaFilePurpose
k6 Load Testingrules/perf-k6.mdThresholds, stages, custom metrics, CI integration
Locust Testingrules/perf-locust.mdPython load tests, task weighting, auth flows
Test Typesrules/perf-types.mdLoad, stress, spike, soak test patterns
Executionrules/execution.mdCoverage reporting, parallel execution, failure analysis
Pytest Markersrules/pytest-execution.mdCustom markers, xdist parallel, worker isolation
Pytest Pluginsrules/pytest-plugins.mdFactory fixtures, plugin hooks, anti-patterns
k6 Patternsreferences/k6-patterns.mdStaged ramp-up, authenticated requests, test types
xdist Parallelreferences/xdist-parallel.mdDistribution modes, worker isolation, CI config
Custom Pluginsreferences/custom-plugins.mdconftest plugins, installable plugins, hook reference
Perf Checklistchecklists/performance-checklist.mdPlanning, setup, metrics, load patterns, analysis
Pytest Checklistchecklists/pytest-production-checklist.mdConfig, markers, parallel, fixtures, CI/CD
Test Templatescripts/test-case-template.mdFull test case documentation template

k6 Quick Start

Set up a load test with thresholds and staged ramp-up:

javascript
import http from 'k6/http';
import { check, sleep } from 'k6';

export const options = {
  stages: [
    { duration: '30s', target: 20 },  // Ramp up
    { duration: '1m', target: 20 },   // Steady state
    { duration: '30s', target: 0 },   // Ramp down
  ],
  thresholds: {
    http_req_duration: ['p(95)<500'],  // 95th percentile under 500ms
    http_req_failed: ['rate<0.01'],    // Less than 1% error rate
  },
};

export default function () {
  const res = http.get('http://localhost:8000/api/health');
  check(res, {
    'status is 200': (r) => r.status === 200,
    'response time < 200ms': (r) => r.timings.duration < 200,
  });
  sleep(1);
}

Run: k6 run --out json=results.json tests/load/api.js

k6 v1.0+ (May 2025) — what changed
  • Native TypeScript: k6 run tests/load/api.ts — no compilation step needed.
  • Auto extension provisioning: k6 run pulls required extensions automatically; manual xk6 build is superseded for most workflows.
  • Browser module import: import browser from 'k6/browser' — the old k6/experimental/browser path was removed in v0.52+. Any generated code using /experimental/ will fail.
  • OTLP output built in: k6 run --out experimental-opentelemetry=... — stream results straight to your tracing backend.
typescript
import http from 'k6/http'
import browser from 'k6/browser'
import { check } from 'k6'

export const options = { vus: 5, duration: '30s' }

export default async function () {
  const page = await browser.newPage()
  await page.goto('https://example.com')
  check(page, { 'title present': async p => (await p.title()).length > 0 })
  await page.close()
}
Show full SKILL.md (171 more words)Show less

Performance Test Types

TypeDurationVUsPurposeWhen to Use
Load5-10 minExpected trafficValidate normal conditionsEvery release
Stress10-20 min2-3x expectedFind breaking pointPre-launch
Spike5 minSudden 10x surgeTest auto-scalingBefore events
Soak4-12 hoursNormal loadDetect memory leaksWeekly/nightly

pytest Parallel Execution

Speed up test suites with pytest-xdist:

toml
# pyproject.toml
[tool.pytest.ini_options]
addopts = ["-n", "auto", "--dist", "loadscope"]
markers = [
    "slow: marks tests as slow",
    "smoke: critical path tests for CI/CD",
]
bash
# Run with parallel workers and coverage
pytest -n auto --dist loadscope --cov=app --cov-report=term-missing --maxfail=3

# CI fast path — skip slow tests
pytest -m "not slow" -n auto

# Debug mode — single worker
pytest -n 0 -x --tb=long

Worker Database Isolation

When running parallel tests with databases, isolate per worker:

python
@pytest.fixture(scope="session")
def db_engine(worker_id):
    db_name = f"test_db_{worker_id}" if worker_id != "master" else "test_db"
    engine = create_engine(f"postgresql://localhost/{db_name}")
    yield engine
    engine.dispose()

Key Thresholds

MetricTargetTool
p95 response time< 500msk6
p99 response time< 1000msk6
Error rate< 1%k6 / Locust
Business logic coverage90%pytest-cov
Critical path coverage100%pytest-cov

Decision Guide

ScenarioRecommendation
JavaScript/TypeScript teamk6 for load testing
Python teamLocust for load testing
Need CI thresholdsk6 (built-in threshold support)
Need distributed testingLocust (built-in distributed mode)
Slow test suitepytest-xdist with -n auto
Flaky parallel tests--dist loadscope for fixture grouping
DB-heavy testsWorker-isolated databases with worker_id
  • ork:testing-unit — Unit testing patterns, pytest fixtures
  • ork:testing-e2e — End-to-end performance testing with Playwright
  • ork:performance — Core Web Vitals and optimization patterns

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (scripts, references) in src/skills/testing-perf of yonatangross/orchestkit.

  • SKILL.md
  • checklists/performance-checklist.md
  • checklists/pytest-production-checklist.md
  • references/custom-plugins.md
  • references/k6-patterns.md
  • references/xdist-parallel.md
  • rules/_sections.md
  • rules/execution.md
  • rules/perf-k6.md
  • rules/perf-locust.md
  • rules/perf-types.md
  • rules/pytest-execution.md
  • rules/pytest-plugins.md
  • scripts/test-case-template.md
  • test-cases.json

Open the folder on GitHubat commit 0ef71d2

Compare with similar skills

Testing Perf 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.

Testing Perf compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Perf this skillyonatangross/orchestkit289—~1.6kAutomated safety check: PassMIT
Testing Strategy Builderaiskillstore/marketplace430—~3.6kAutomated safety check: PassNone
Adk Verify Snippetsgoogle/adk-python22k—~1.4kAutomated safety check: PassApache-2.0
Megatron Core Testing GuideNVIDIA/Megatron-LM18k1 repos~2.1kAutomated safety check: PassApache-2.0
Hermetic Python Unit TestsdimensionalOS/dimos4.6k—~1.4kAutomated safety check: PassCustom licence
Test GuardamElnagdy/guard-skills1.3k2 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Testing Strategy Builder

    aiskillstore/marketplace

    A skill your agent uses when creating comprehensive testing strategies for applications.

    430 GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Adk Verify Snippets

    google/adk-python

    Official

    Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail…

    22k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Megatron Core Testing Guide

    NVIDIA/Megatron-LM

    Official

    Guide to the Megatron-LM test system: layout, recipe YAML, running and adding unit and functional tests, golden values, marker filters and CI parity.

    18k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed
  • Hermetic Python Unit Tests

    dimensionalOS/dimos

    Rules for writing, fixing and reviewing pytest unit tests that are hermetic: behavior-focused, deterministic, isolated and cheap to run.

    4.6k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Guard

    amElnagdy/guard-skills

    Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.

    1.3k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed
  • Fla Optimization Loop

    fla-org/flash-linear-attention

    Disciplined, reproducible loop for making an FLA kernel faster (Triton, Gluon, TileLang, CuTe) without ever breaking or gaming correctness.

    5.8k GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed

More from yonatangross/orchestkit

All 108 skills in this repo
  • API Design

    yonatangross/orchestkit

    API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.

    289 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    289 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    289 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    289 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    289 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    289 GitHub stars~3.9k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Testing Perf

What does Testing Perf do?

Performance and load testing patterns — k6 load tests, Locust stress tests, pytest execution optimization (xdist parallel, plugins), test type classification, and performance benchmarking. Testing Perf is an agent skill from yonatangross/orchestkit. Performance and load testing patterns — k6 load tests, Locust stress tests, pytest execution optimization (xdist parallel, plugins), test type classification, and performance benchmarking.

When should I use Testing Perf?

Testing Perf fits situations like: writing load tests; optimizing test execution speed; setting up pytest infrastructure.

How do I install Testing Perf in Claude Code?

Run `npx skills add yonatangross/orchestkit --skill testing-perf -a claude-code`. Or copy the skill folder (src/skills/testing-perf in yonatangross/orchestkit) into .claude/skills/testing-perf in your project. Claude Code loads it when a task matches its description.

How do I install Testing Perf in Codex?

Run `npx skills add yonatangross/orchestkit --skill testing-perf -a codex`. Or copy the skill folder (src/skills/testing-perf in yonatangross/orchestkit) into .agents/skills/testing-perf in your project. Codex loads it when a task matches its description.

Can I use Testing Perf 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 yonatangross/orchestkit --skill testing-perf -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-perf, .gemini/skills/testing-perf, .github/skills/testing-perf and .opencode/skills/testing-perf in your project.

What does Testing Perf need to run?

Going by SKILL.md and its folder, Testing Perf needs the command-line tools its instructions call (pytest). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+..

Does Testing Perf 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 Testing Perf 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 Testing Perf use?

Testing Perf is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing Perf use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Testing Perf?

Skills that share tags, products or a category with Testing Perf: Testing Strategy Builder (aiskillstore/marketplace, 430 stars), Adk Verify Snippets (google/adk-python, 22k stars), Megatron Core Testing Guide (NVIDIA/Megatron-LM, 18k stars) and Hermetic Python Unit Tests (dimensionalOS/dimos, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Perf?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 289 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 7, 2026.

Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.