Blazemeter
- 29 skills
- 0 followers
- 1 day ago last updated
- ▌ Prisma Taurus · blazemeter bundleUse when the user wants to check, fix, or verify Prisma Cloud vulnerability scan results for the Taurus Docker image (blazemeter/taurus:unstable). Run this skill on Opus 5 (1M context) or newer — choosing and applying the correct CVE fix requires strong reasoning.
- ▌
- ▌ Jira · blazemeterCreate and transition Blazemeter MOB Jira tickets — project MOB / board 5348, type Task, custom fields (Product=Blazemeter, Scrum Team=Terra, active sprint), assignee resolved from the repo owner display name, status transitioned to In Review, with a structured description linking the PR and Jenkins build. The ticket's summary/name is supplied by whichever skill invokes this one — this skill doesn't invent ticket titles. Load when a flow needs to file or update a MOB ticket.
- ▌ Mend · blazemeter bundleRead and interpret Mend (formerly WhiteSource) SCA data — authenticate to the REST API v1.3, look up a project token, fetch SECURITY_VULNERABILITY alerts, and classify CVE severity. Load whenever the work involves Mend/WhiteSource, CVEs from Mend, or fetching/triaging vulnerability alerts. Generic SCA-read knowledge; the fix workflow lives in dep-remediation + the mend-blz recipe.
- ▌ Github · blazemeterBlazemeter GitHub branch and PR conventions — create a unique date-stamped Docker-safe branch off the integration branch, commit with the Co-Authored-By trailer, push via SSO-authorized gh, open a PR back into the integration branch, and prepend the tracking ticket id to the PR title. Load for branch/push/PR work on Blazemeter repos.
- ▌ Jenkins · blazemeterTrigger and gate on a Blazemeter blazect Jenkins multibranch build — POST buildWithParameters with PUSH_TO_GCR=true and PERFORM_WHITESOURCE_SCAN=true, track the queue item to the specific triggered build number and poll that (not lastBuild, which races with the branch's own auto-triggered build) until green (unit-test/prisms/mend stages), fix-forward on red, and never gate on the slow API_TESTS-CI suite. Also deploys a green branch's image to a denv environment via the shared 'Deploy environment' job (GIRO_BRANCH + USERNAME) and gates on that deploy job going green. Load when a flow needs to run, deploy, or wait on a Blazemeter CI build.
- ▌ Mend Blz · blazemeter bundleEnd-to-end Mend vulnerability remediation for Blazemeter components (a.blazemeter, dagger, search, crane components). Composes the mend, dep-remediation, jenkins, github, and jira skills into one loop — Mend alerts → dependency fix on a fresh date-stamped branch → Jenkins green → [crane only] a.blazemeter.com branch with updated HarborVersionsSettings.php → denv deploy + fix-related API tests (fix verified in denv) → Confluence report → Jira (MOB, created first) → PR (opened with the ticket id already in the title) → Jira description updated with the PR link. Load when the user wants to fix/remediate Mend/WhiteSource vulnerabilities for a Blazemeter service.
- ▌ To Issues · blazemeterBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
- ▌ Opensearch · blazemeterSearch BlazeMeter logs in a given environment (denv, bzdev, ci, staging, or prod) for a given subject, and return a condensed, relevant result list. Trigger phrases - "search opensearch for X in denv", "check logs for master 386 on bzdev", "opensearch <env> <subject>".
- ▌ Summarize Pr · blazemeter bundleSummarize a GitHub pull request — purpose, key changes, review state, CI status, and outstanding blockers. Use when the user pastes a PR URL (github.com/<org>/<repo>/pull/<n>), references a PR by number (e.g. "PR
- ▌ Example Skill · blazemeterTemplate skill — copy this directory and edit. Replace this description with WHEN Claude should invoke the skill (e.g. "Use when the user asks to inspect X" or "Triggers on mentions of Y"). The description is the only signal Claude uses to auto-load the skill, so be specific about the trigger surface.
- ▌ File Doc Task · blazemeter bundleFile or update a documentation-planning JIRA task for a customer-facing feature, using the documentation team's standard template. Idempotent create-or-update — safe to run early (draft a DOC-ready ticket from the specs/design to guide development) and again at finalize (reconcile the description against what was actually shipped). For FEATURE or USER-FACING work the skill first asks once whether the change needs customer-facing documentation, and only creates the ticket if it does. Also use when a developer explicitly asks to "create a doc task", "file a docs ticket", "DOC-ready ticket", "update the doc task", or hand work off to the documentation team. Do NOT use for pure refactors, internal-only fixes, or build/dependency chores.
- ▌ Jira Lifecycle · blazemeterKeep a related JIRA issue's status and comment trail in step with AI-driven work so the lifecycle is visible in JIRA metrics. Idempotent, forward-only transitions at each lifecycle point — move to In Progress when work starts, add progress comments for meaningful updates, post the PR link + summary when a PR opens (no status change), move to In Review when CI passes, move to Testing when on Staging, and Closed when verified on Production. Use whenever a Claude workflow acts on a related JIRA key (MOB-1234, SECVULN-99, …) at any of those points, or when a developer asks to "move the ticket to in progress / in review", "post the PR link on the ticket", or "close the ticket". Do NOT use when there is no related JIRA issue, and do NOT use to create issues.
- ▌ Address Pr Reviews · blazemeterUse when the user provides a GitHub PR URL or number and asks to address, action, or incorporate review comments for any repo. Also use when continuing an existing PR comment cycle after a new push. Stack-agnostic — auto-detects the target repo's own test/lint commands rather than assuming a specific language.
- ▌ Dep Remediation · blazemeterFix vulnerable dependencies correctly — the golden rule (bump the direct dependency / BOM, never pin the transitive), cross-check the fix version against ecosystem advisories, defer breaking-major upgrades, and compile + unit-test locally before pushing. Load for any dependency remediation or version-bump work in php-composer, gradle-springboot, maven-springboot, pip, or npm projects.
- ▌ Blazemeter Recorders · blazemeter bundleComprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder. Use when working with recorders for (1) Recording tests with Chrome Extension, (2) Creating and using Proxy Recorder, (3) Configuring browsers and devices for proxy recording, (4) Setting port ranges for proxy recorder, or any other recording tasks.
- ▌ Blazemeter Scripting · blazemeter bundleComprehensive guide for BlazeMeter Scripting, including Groovy/Beanshell, JMeter plugins, JMeter DSL, and API Monitoring scripting. Use when working with scripting for (1) Writing files in Groovy/Beanshell scripts, (2) Using non-standard JMeter plugins, (3) Creating JMeter tests with JMeter DSL, (4) Writing custom scripts for API Monitoring (custom libraries, included libraries, initial script, reusable snippets), or any other scripting tasks.
- ▌ Blazemeter Test Data · blazemeter bundleComprehensive guide for BlazeMeter Test Data Management, including data entities, parameters, generation, orchestration, and management operations. Use when working with test data for (1) Creating and managing data entities and parameters, (2) Generating synthetic test data with seed lists and functions, (3) Using test data in tests (CSV, Data Entities), (4) Managing test data (backup, import/export, sharing), (5) Using Test Data Orchestration and Profiler, (6) Working with Test Data Pro, or any other Test Data Management tasks.
- ▌ Blazemeter Integrations · blazemeter bundleComprehensive guide for BlazeMeter Integrations, including APM tools, CI/CD pipelines, and development tools. Use when working with integrations for (1) Integrating APM tools (AppDynamics, Datadog, New Relic, CloudWatch, DX APM, Dynatrace, Delphix), (2) Integrating CI/CD tools (Jenkins, GitHub Actions, GitLab CI/CD, Azure DevOps, AWS CodePipeline, Bamboo, TeamCity, CircleCI, Codeship), (3) Using development tools (Visual Studio Code Plugin, MCP Server), or any other integration tasks.
- ▌ Blazemeter API Reference · blazemeter bundleComprehensive reference for BlazeMeter REST APIs, including authentication, identifiers, and API endpoints. Use when working with BlazeMeter APIs for (1) Understanding BlazeMeter REST API structure, (2) Authenticating API requests, (3) Obtaining identifiers (Workspace ID, Project ID, Test ID, etc.), (4) Using Test Data API, (5) Using Cloning API, (6) Using Export API, (7) Using Service Virtualization Bulk Operations APIs, or any other API tasks.
- ▌ Blazemeter Usage Billing · blazemeter bundleGuide for BlazeMeter Usage & Billing, including credit types and charging. Use when working with usage and billing for (1) Understanding BlazeMeter credit types (VU, VUH, Tests), (2) Calculating credit consumption for different test types, or any other usage and billing tasks.
- ▌ Blazemeter Administration · blazemeter bundleComprehensive guide for BlazeMeter Administration, including workspaces, projects, security, alerts, and team management. Use when working with administration for (1) Managing workspaces and projects, (2) Configuring security settings (SAML SSO, 2FA, API keys), (3) Creating workspace alerts, (4) Managing private locations across workspaces, (5) Creating APM credentials, (6) Managing API Monitoring teams, (7) Configuring AI consent, or any other administration tasks.
- ▌ Blazemeter Getting Started · blazemeter bundleGetting started guides for BlazeMeter, including onboarding, migration guides, continuous testing journey, glossary, and mobile testing. Use when getting started with BlazeMeter for (1) Navigating BlazeMeter University onboarding, (2) Migrating from Runscope or JMeter, (3) Understanding the continuous testing journey, (4) Referencing BlazeMeter terminology, (5) Testing mobile sites and apps, or any other getting started tasks.
- ▌ Blazemeter Troubleshooting · blazemeter bundleComprehensive troubleshooting guide for BlazeMeter, covering API Monitoring, Performance Testing, general issues, integrations, and security. Use when troubleshooting for (1) API Monitoring issues (Radar Agent auth, SSL certificates, debug tests), (2) Performance Testing issues (high response time, 500 errors, partial load, tests not starting), (3) General issues (delete non-empty project, forbidden domains, Chrome Extension export failures), (4) Integration issues (New Relic reporting), (5) Security issues (Apache Log4j2 vulnerability), (6) Support requests and tickets, or any other troubleshooting tasks.
- ▌ Blazemeter Network Security · blazemeter bundleComprehensive guide for BlazeMeter Network & Security, including allowlisting, DNS configuration, and security best practices. Use when working with network and security for (1) Configuring allowlists for BlazeMeter engines and infrastructure, (2) Disabling DNS caching, (3) Implementing security best practices for API Monitoring, or any other network and security tasks.
- ▌ Blazemeter Private Locations · blazemeter bundleComprehensive guide for BlazeMeter Private Locations, including Radar Agent, installation (Docker, Kubernetes, Helm), configuration, management, and troubleshooting. Use when working with Private Locations for (1) Installing agents (Docker, Kubernetes, Helm Chart), (2) Configuring Radar Agent for API Monitoring, (3) Setting up environment variables and certificates, (4) Managing private locations and agents, (5) Troubleshooting installation and connectivity issues, or any other Private Location tasks.
- ▌ Blazemeter Functional Testing · blazemeter bundleComprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3) Using test data in Functional Tests, (4) Working with Action Library, (5) Debugging Functional Tests, (6) Understanding browser support, or any other Functional Testing tasks. Note - API Functional Tests are deprecated in favor of API Monitoring.
- ▌ Blazemeter Performance Testing · blazemeter bundleComprehensive guide for BlazeMeter Performance Testing, including load configuration, reporting, JMeter configuration, Taurus, scenarios, and advanced features. Use when working with Performance tests for (1) Configuring load settings and distribution, (2) Creating and running tests (JMeter, Browser, URL/API, Multi-Test), (3) Analyzing reports and filtering data, (4) Configuring JMeter properties and scenarios, (5) Using Taurus for test configuration, (6) Advanced features (AI Log Analysis, APM Integration, Network Emulation, Mainframe Testing), (7) Troubleshooting test issues, or any other Performance Testing tasks.
- ▌ Blazemeter Service Virtualization · blazemeter bundleComprehensive guide for BlazeMeter Service Virtualization, including virtual services, transactions, templates, and management. Use when working with Service Virtualization for (1) Creating virtual services and transactions, (2) Managing services (clone, export/import, rename/delete), (3) Using templates and environment variables, (4) Adding processing actions to transactions, (5) Using test data with virtual services, (6) Understanding transactional analytics, or any other Service Virtualization tasks.