Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

running-performance-tests运行性能测试

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

654

周安装

27

GitHub Stars

2,128

下载量

214
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:running-performance-tests(运行性能测试)
来源仓库:https://github.com/jeremylongshore/claude-code-plugins-plus-skills
仓库路径:skills/running-performance-tests
安装命令:
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill running-performance-tests
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill running-performance-tests

简介

用于辅助测试设计、自动化测试、用例整理和回归验证。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中编写单元测试、端到端测试或根据失败日志定位问题。
  • 使用时需确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑。
  • 涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。
  • 安装方式:github,安装命令:npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill running-performance-tests

SKILL.md

Performance Test Suite

Overview

Execute load testing, stress testing, and performance benchmarking to identify bottlenecks, establish baseline metrics, and verify SLA compliance. Supports k6 (recommended), Artillery, Apache JMeter, Locust (Python), and autocannon (Node.js).

Prerequisites

  • Performance testing tool installed (k6, artillery, locust, jmeter, or autocannon)
  • Target application deployed in a production-like environment (not local dev)
  • Baseline performance metrics or SLA targets (e.g., p95 < 200ms, 99.9% availability)
  • Monitoring stack accessible (Grafana, CloudWatch, Datadog) for resource metrics during tests
  • Test data sufficient to avoid cache-only responses

Instructions

  1. Define performance test scenarios based on production traffic patterns:

- Load test: Simulate expected peak traffic (e.g., 500 concurrent users for 10 minutes). - Stress test: Ramp beyond expected capacity to find the breaking point. - Spike test: Sudden burst of traffic (0 to 1000 users in 10 seconds). - Soak test: Sustained moderate load for extended duration (1-4 hours) to detect memory leaks.

  1. Create test scripts targeting critical endpoints:

- Identify the top 5-10 most-hit API endpoints from production access logs. - Include both read (GET) and write (POST/PUT/DELETE) operations. - Simulate realistic user behavior with think time between requests. - Use parameterized data to avoid cache-only hits (randomize query parameters, user IDs).

  1. Configure load profiles:

- Define virtual user (VU) ramp-up stages (e.g., 10 VUs for 1 minute, then 50 VUs for 5 minutes). - Set test duration appropriate to the scenario (load: 10-15 min, soak: 1-4 hours). - Configure request timeouts matching production settings.

  1. Execute the performance test:

- Run from a machine with sufficient network bandwidth and CPU. - Avoid running from the same host as the application under test. - Monitor application metrics (CPU, memory, DB connections) during execution.

  1. Analyze results against SLA thresholds:

- p50, p90, p95, p99 response times. - Requests per second (throughput). - Error rate (target: < 0.1% for load test, higher tolerance for stress test). - Resource utilization (CPU < 80%, memory < 85% at peak load).

  1. Identify and document bottlenecks:

- Slow database queries (check slow query logs). - CPU-bound operations (profiling data). - Memory leaks (growing RSS over soak test). - Connection pool exhaustion (database or HTTP client).

  1. Generate a performance report with visualizations and recommendations.

Output

  • Performance test scripts (k6 .js, Artillery .yml, or Locust .py files)
  • Execution results with response time percentiles, throughput, and error rates
  • Performance report comparing results against SLA thresholds
  • Bottleneck analysis with specific recommendations
  • CI integration configuration for automated performance regression detection

Error Handling

ErrorCauseSolution
Connection reset by peerServer or load balancer dropping connections under loadCheck max connections settings; increase connection pool size; verify keep-alive configuration
Timeouts spike at certain VU countApplication thread pool or database connection pool exhaustedProfile connection usage; increase pool size; add connection queuing; optimize slow queries
Inconsistent results between runsCache warming, garbage collection pauses, or noisy neighbor effectsRun a warm-up phase before measurement; use dedicated test infrastructure; average across 3 runs
Load generator CPU maxed outSingle machine cannot generate sufficient loadDistribute load generation across multiple machines; use cloud-based load generation services
All requests return cached responsesTest data not sufficiently variedRandomize request parameters; use unique IDs per request; disable CDN caching for test environment

Examples

k6 load test script:

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

export const options = {
  stages: [
    { duration: '2m', target: 50 },   // Ramp up
    { duration: '5m', target: 50 },   // Sustained load
    { duration: '2m', target: 200 },  // Stress  # HTTP 200 OK
    { duration: '1m', target: 0 },    // Ramp down
  ],
  thresholds: {
    http_req_duration: ['p(95)<200', 'p(99)<500'],  # 500: HTTP 200 OK
    http_req_failed: ['rate<0.01'],
  },
};

export default function () {
  const res = http.get('https://api.test.com/products');
  check(res, {
    'status is 200': (r) => r.status === 200,  # HTTP 200 OK
    'response time OK': (r) => r.timings.duration < 300,  # 300: timeout: 5 minutes
  });
  sleep(1); // Think time
}

Artillery test configuration:

config:
  target: "https://api.test.com"
  phases:
    - duration: 120
      arrivalRate: 10
      name: "Warm up"
    - duration: 300  # 300: timeout: 5 minutes
      arrivalRate: 50
      name: "Sustained load"
  ensure:
    p95: 200  # HTTP 200 OK
    maxErrorRate: 1
scenarios:
  - flow:
      - get:
          url: "/api/products"
      - think: 1
      - post:
          url: "/api/cart"
          json: { productId: "{{ $randomString() }}" }

Resources

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.44%
按下载量换算69

Claude

29.25%
按下载量换算63

Cursor

19.92%
按下载量换算43

Gemini CLI

8.59%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills