octoperf

Plugin octoperf from marketplace octoperf in OctoPerf/octoperf-claude-plugins. Commands read from the repo's manifest — 18 days ago.

Skills (22)

• octoperf-async-polling

  Use whenever an OctoPerf operation runs asynchronously and the LLM has to wait for it to settle — `validate_virtual_user`, `run_scenario`, `export_bench_report_pdf`, the async correlation tasks behind `apply_correlations_to_virtual_user`, or any tool that returns a `taskId` / `benchResultId` instead

• octoperf-auto-correlation

  Use when an OctoPerf Virtual User imported from a HAR/Postman/JMX recording fails its validation run because dynamic values (session tokens, CSRF, signed URLs, anti-forgery inputs, auth challenges) captured at recording time are stale on replay. Triggers on requests for "auto-correlation", "correlat

• octoperf-bench-reports

  Use when reading or interpreting an OctoPerf bench report — picking the right `get_report_*_values` tool for a given report item, understanding the difference between flat, trend and comparison reports, reusing a report's shape through a report template, decoding semantic gotchas (Hits vs Hits CONTA

• octoperf-blazemeter-migration

  Use when migrating BlazeMeter tests to OctoPerf. Triggers on "migrate from BlazeMeter", "import my BlazeMeter tests", "we're leaving BlazeMeter", "leaving Perforce", "bzm to octoperf", "convert my Taurus test". Inventories a BlazeMeter account, brings the JMeter and Taurus tests across as Virtual Us

• octoperf-export-bench-report-pdf

  Use when the user asks to "export the report as PDF", "print the bench report", "get a PDF of report X", "export these reports", "share a PDF with stakeholders", or any variation that calls for a static artefact of one or several OctoPerf benchReports. Walks the LLM through the three-step async chai

• octoperf-gatling-migration

  Use when migrating Gatling simulations (Java, Scala or Kotlin) to OctoPerf. Triggers on "migrate from Gatling", "convert my Gatling simulation", "import a Gatling project", "can OctoPerf run my Gatling scripts", "we''re leaving Gatling". Decides first whether the project is worth migrating, then rew

• octoperf-har-recording

  Use when a Virtual User has to be built from real browser traffic — "record my application", "capture a HAR", "build a VU from what I do in the browser", "import this .har", "record the checkout journey". Covers driving the recording yourself with Playwright (the only route that names the containers

• octoperf-jtl-import

  Use when someone has JMeter result files and wants OctoPerf's analysis of them rather than a new run. Triggers on "import my JTL", "analyse these JMeter results", "I ran JMeter from the command line / in CI, can you build a report", "results.jtl", "turn my .jtl into a report". Covers what to check b

• octoperf-k6-scripting

  Use when writing, importing, editing, validating or exporting a K6 Virtual User on OctoPerf. Triggers on "import my K6 script", "run my k6 test on OctoPerf", "write a K6 script for this journey", "use a CSV in my K6 script", "read a project variable from K6", "why does my K6 validation fail", "creat

• octoperf-loadrunner-migration

  Use when migrating a LoadRunner script or Controller scenario to OctoPerf. Triggers on "migrate from LoadRunner", "import my VuGen script", "convert a .usr script", "import an .lrs scenario", "we''re leaving Micro Focus/OpenText LoadRunner", "can OctoPerf read a LoadRunner script". Decides first whe

• octoperf-monitoring

  Use when monitoring servers during an OctoPerf load test — OS, database, web/app server, JMX, Prometheus, New Relic or SLA monitors. Triggers on "monitor my servers during the test", "add a database monitor", "watch CPU/memory on the target", "why does my monitor collect nothing", "add a threshold o

• octoperf-neoload-migration

  Use when migrating a NeoLoad project to OctoPerf. Triggers on "migrate from NeoLoad", "import my NeoLoad project", "convert a .nlp project", "we're leaving Neotys/Tricentis NeoLoad", "can OctoPerf read config.zip". Decides first whether the project is worth migrating, imports what converts mechanica

• octoperf-notifications

  Use when managing OctoPerf workspace notifications — alerting a channel when a test run starts, ends or fails. Triggers on "notify Slack when a test fails", "send an email at the end of each run", "open a JIRA ticket on failure", "add a Teams / Google Chat / Webex / webhook notification", "which not

• octoperf-onpremise-agent

  Use when running OctoPerf load tests from the user's own machines instead of the Cloud — creating an on-premise provider, sizing it, installing agents, managing locations. Triggers on "run the test from my own servers", "install an on-premise agent", "load test an internal application", "how many ag

• octoperf-real-browser-probe

  Use when the user wants to run a real-browser probe alongside a JMeter HTTP load test to capture user-perceived metrics (page load time, render time, JS execution, Core Web Vitals) while JMeter generates the bulk HTTP load. Triggers on "real browser monitoring during load test", "EUM probe", "playwr

• octoperf-report-item-editing

  Use when changing what an OctoPerf bench-report item displays — its metrics, filters or curves — rather than reading its values (see octoperf-bench-reports for that). Triggers on "add a metric to this chart", "change the filter of this report item", "show errors per container in the report", "add a

• octoperf-scenario-composition

  Use when building or reshaping an OctoPerf scenario — its user profiles, load shapes, engines, set-up/tear-down and pass criteria. Triggers on "create a scenario with 100 users", "ramp up over 10 minutes", "add a user profile", "run this VU from another location", "set pass criteria on the test". Co

• octoperf-scenario-diagnosis

  Use when an OctoPerf load-test scenario has completed (or is running) and the user wants to understand why it failed, underperformed, or behaved unexpectedly. Triggers on "the load test failed", "why are response times so high", "high error rate in the scenario", "diagnose this bench", "the run look

• octoperf-scheduling

  Use when scheduling an OctoPerf scenario to run at a specific time (one-shot) or on a recurring cadence (cron), or when listing / pausing / resuming / deleting an existing schedule. Triggers on "schedule the scenario for tomorrow morning", "run this every weekday at 8am", "every night at midnight",

• octoperf-sla

  Use when defining pass/fail thresholds on an OctoPerf Virtual User's own metrics — a design SLA profile. Triggers on "define an SLA", "alert when response time exceeds 2s", "fail the test above 1% errors", "attach an SLA to this VU", "why doesn't my SLA raise anything". Covers the two things called

• octoperf-validation-triage

  Use when an OctoPerf Virtual User validation run has produced many failing actions and the user needs to diagnose them efficiently without reading every single failure serially. Triggers on "the validation is red", "lots of errors after import", "VU validation failed, what's wrong", "triage these fa

• octoperf-workspace

  Use when managing OctoPerf workspaces and their members — who works where and with which permissions. Triggers on "create a workspace", "add a colleague to the workspace", "change member permissions", "why can't I see this provider / project". Covers what a workspace scopes, creating sparingly (dele

MCP servers (1)

• octoperf

  connects to: https://api.octoperf.com/mcp

Similar plugins