Skip to content
TrustedSkillsbeta
Back to all skills

Performance Analysis

Checked
proffesor-for-testing·vlatest·testing·MIT

Helps with testing, performance optimization, analysis as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it qe-performance-analysis, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add proffesor-for-testing/agentic-qe --skill qe-performance-analysis -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

proffesor-for-testing

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned proffesor-for-testing/agentic-qe at 124d8c735e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
124d8c735e
Manifest
.kiro/skills/qe-performance-analysis/SKILL.md
Scanned
1 file, 61 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, "proffesor-for-testing-performance-analysis," provides capabilities for analyzing API testing performance. It allows you to identify bottlenecks and areas for improvement in your API tests by providing detailed insights into response times and other key metrics. The tool is specifically designed for use with the sentinel-api-testing framework.

When to use it

  • Troubleshooting slow API responses: Use this skill when you're experiencing performance issues with an API endpoint and need to pinpoint the cause.
  • Optimizing test suite execution time: Identify tests that are taking longer than expected, allowing for optimization of your testing process.
  • Monitoring API stability over time: Track key performance indicators (KPIs) to ensure consistent API performance and detect regressions.
  • Comparing different API implementations: Evaluate the performance differences between various versions or implementations of an API.

Key capabilities

  • API Performance Analysis
  • Sentinel-API Testing Integration
  • Response Time Monitoring
  • Bottleneck Identification

Example prompts

  • "Analyze the performance of my sentinel API tests and identify any slow endpoints."
  • "Show me a report of response times for all API calls in the last week."
  • “Compare the performance of version 1.0 and version 2.0 of the /users endpoint.”

Tips & gotchas

  • This skill requires the sentinel-api-testing framework to be properly configured and running before it can analyze test results.
  • Ensure you have sufficient data collected by your API tests for accurate performance analysis.