New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Detecting Performance Regressions

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines.

MITAuto-check passedDevOps & Cloud

Install Detecting Performance Regressions

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill detecting-performance-regressions -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace detecting-performance-regressions --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/detecting-performance-regressions .claude/skills/detecting-performance-regressions && 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
detecting-performance-regressions
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
457 words
Files
7 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines.

  • Works in 3 steps: Analyze Performance Data: The plugin… → Detect Regressions: It employs methods… → Report Findings: The plugin generates a…
  • Validating builds
  • SKILL.md covers Overview, How It Works, When to Use This Skill and Examples, plus 7 more sections
  • Runs Python scripts from its folder

What it does

Detecting Performance Regressions is an agent skill from jeremylongshore/tons-of-skills-marketplace. Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines. Use when validating builds or analyzing performance trends. Trigger with phrases like "detect performance regression", "compare performance metrics", or "analyze performance degradation".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering OKRs and executive reporting and CI/CD. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Validating builds
  • Analyzing performance trends
  • With phrases like detect performance regression
  • Compare performance metrics

Example prompts

  • “detect performance regression”
  • “compare performance metrics”
  • “analyze performance degradation”
  • “/detecting-performance-regressions”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(ci:*), Bash(metrics:*), Bash(testing:*)

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Analyze Performance Data: The plugin gathers performance metrics from the CI/CD environment.
  2. Detect Regressions: It employs methods like baseline comparison, statistical analysis, and threshold checks to detect regressions.
  3. Report Findings: The plugin generates a report summarizing the detected performance regressions and their potential impact.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. 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
    • Write
    • Edit
    • Grep
    • Glob
    • Bash(ci:*)
    • Bash(metrics:*)
    • Bash(testing:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), 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.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Detecting Performance Regressions loads about 1.1k tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 457 words of instructions outside code blocks.

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

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 457 words, ~1,099 tokens.

Download SKILL.mdSave it as .claude/skills/detecting-performance-regressions/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
detecting-performance-regressions
description
Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines. Use when validating builds or analyzing performance trends. Trigger with phrases like "detect performance regression", "compare performance metrics", or "analyze performance degradation".
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(ci:*), Bash(metrics:*), Bash(testing:*)
compatibility
Designed for Claude Code
version
1.22.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
performance, ci-cd, detecting-performance

Performance Regression Detector

Detect performance regressions in CI/CD pipelines by comparing response times, throughput, and resource usage against historical baselines using statistical analysis.

Overview

This skill automates the detection of performance regressions within a CI/CD pipeline. It utilizes various methods, including baseline comparison, statistical analysis, and threshold violation checks, to identify performance degradation. The skill provides insights into potential performance bottlenecks and helps maintain application performance.

How It Works

  1. Analyze Performance Data: The plugin gathers performance metrics from the CI/CD environment.
  2. Detect Regressions: It employs methods like baseline comparison, statistical analysis, and threshold checks to detect regressions.
  3. Report Findings: The plugin generates a report summarizing the detected performance regressions and their potential impact.

When to Use This Skill

This skill activates when you need to:

  • Identify performance regressions in a CI/CD pipeline.
  • Analyze performance metrics for potential degradation.
  • Compare current performance against historical baselines.

Examples

Example 1: Identifying a Response Time Regression

User request: "Detect performance regressions in the latest build. Specifically, check for increases in response time."

The skill will:

  1. Analyze response time metrics from the latest build.
  2. Compare the response times against a historical baseline.
  3. Report any statistically significant increases in response time that exceed a defined threshold.
Example 2: Detecting Throughput Degradation

User request: "Analyze throughput for performance regressions after the recent code merge."

The skill will:

  1. Gather throughput data (requests per second) from the post-merge CI/CD run.
  2. Compare the throughput to pre-merge values, looking for statistically significant drops.
  3. Generate a report highlighting any throughput degradation, indicating a potential performance regression.
Show full SKILL.md (194 more words)Show less

Best Practices

  • Define Baselines: Establish clear and representative performance baselines for accurate comparison.
  • Set Thresholds: Configure appropriate thresholds for identifying significant performance regressions.
  • Monitor Key Metrics: Focus on monitoring critical performance metrics relevant to the application's behavior.

Integration

This skill can be integrated with other CI/CD tools to automatically trigger regression detection upon new builds or code merges. It can also be combined with reporting plugins to generate detailed performance reports.

Prerequisites

  • Historical performance baselines in ${CLAUDE_SKILL_DIR}/performance/baselines/
  • Access to CI/CD performance metrics
  • Statistical analysis tools
  • Defined regression thresholds

Instructions

  1. Collect performance metrics from current build
  2. Load historical baseline data
  3. Apply statistical analysis to detect significant changes
  4. Check for threshold violations
  5. Identify specific regressed metrics
  6. Generate regression report with root cause analysis

Output

  • Performance regression detection report
  • Statistical comparison with baselines
  • List of regressed metrics with severity
  • Visualization of performance trends
  • Recommendations for investigation

Error Handling

If regression detection fails:

  • Verify baseline data availability
  • Check metrics collection configuration
  • Validate statistical analysis parameters
  • Ensure threshold definitions are valid
  • Review CI/CD integration setup

Resources

  • Statistical process control for performance testing
  • CI/CD performance testing best practices
  • Regression detection algorithms
  • Performance monitoring strategies

© jeremylongshore, 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 6 other files (scripts, references, assets) in skills/.curated/detecting-performance-regressions of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • references/README.md
  • scripts/README.md
  • scripts/analyze_metrics.py
  • scripts/create_github_comment.py
  • scripts/generate_report.py

Open the folder on GitHubat commit cfae287

Compare with similar skills

Detecting Performance Regressions 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.

Detecting Performance Regressions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Detecting Performance Regressions this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Frontend Ops Expertmizchi/skills360—~446Automated safety check: PassNone
QA Dashboardpetrkindlmann/qa-skills170—~4.7kAutomated safety check: PassMIT
QA Metricspetrkindlmann/qa-skills170—~5.3kAutomated safety check: PassMIT
Analytics Opensearch Expertiseaws/tools-for-devops-agent103—~6.9kAutomated safety check: PassApache-2.0
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT

Similar skills

  • Frontend Ops Expert

    mizchi/skills

    Frontend Ops specialist perspective for the weekly review. An agent skill from mizchi/skills.

    360 GitHub stars~446 tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed

  • QA Dashboard

    petrkindlmann/qa-skills

    Build and visualize QA dashboards and reports with Allure Report, Grafana, and ReportPortal.

    170 GitHub stars~4.7k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

  • QA Metrics

    petrkindlmann/qa-skills

    Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites.

    170 GitHub stars~5.3k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • Analytics Opensearch Expertise

    aws/tools-for-devops-agent

    Official

    Amazon OpenSearch Service domain health assessment. An agent skill from aws/tools-for-devops-agent.

    103 GitHub stars~6.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed

  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    36k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Detecting Performance Regressions

What does Detecting Performance Regressions do?

Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines. Detecting Performance Regressions is an agent skill from jeremylongshore/tons-of-skills-marketplace. Automatically detect performance regressions in CI/CD pipelines by comparing metrics against baselines.

When should I use Detecting Performance Regressions?

Detecting Performance Regressions fits situations like: validating builds; analyzing performance trends; with phrases like detect performance regression; compare performance metrics.

How do I install Detecting Performance Regressions in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill detecting-performance-regressions -a claude-code`. Or copy the skill folder (skills/.curated/detecting-performance-regressions in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/detecting-performance-regressions in your project. Claude Code loads it when a task matches its description.

How do I install Detecting Performance Regressions in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill detecting-performance-regressions -a codex`. Or copy the skill folder (skills/.curated/detecting-performance-regressions in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/detecting-performance-regressions in your project. Codex loads it when a task matches its description.

Can I use Detecting Performance Regressions 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 jeremylongshore/tons-of-skills-marketplace --skill detecting-performance-regressions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/detecting-performance-regressions, .gemini/skills/detecting-performance-regressions, .github/skills/detecting-performance-regressions and .opencode/skills/detecting-performance-regressions in your project.

What does Detecting Performance Regressions need to run?

Going by SKILL.md and its folder, Detecting Performance Regressions needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(ci:*), Bash(metrics:*), Bash(testing:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Detecting Performance Regressions 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 Detecting Performance Regressions 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 Detecting Performance Regressions use?

Detecting Performance Regressions 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 Detecting Performance Regressions use?

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

What are the alternatives to Detecting Performance Regressions?

Skills that share tags, products or a category with Detecting Performance Regressions: Frontend Ops Expert (mizchi/skills, 360 stars), QA Dashboard (petrkindlmann/qa-skills, 170 stars), QA Metrics (petrkindlmann/qa-skills, 170 stars) and Analytics Opensearch Expertise (aws/tools-for-devops-agent, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Detecting Performance Regressions?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.