intent-solutions-io/testing-load-balancers
010-archive/backups-20251108/skill-structure-cleanup-20251108-073936/plugins/testing/load-balancer-tester/skills/load-balancer-tester/SKILL.md
This skill enables Claude to test load balancing strategies. It validates traffic distribution across backend servers, tests failover scenarios when servers become unavailable, verifies sticky sessions, and assesses health check functionality. Use this skill when the user asks to "test load balancer", "validate traffic distribution", "test failover", "verify sticky sessions", or "test health checks". It is specifically designed for testing load balancing configurations using the `load-balancer-tester` plugin.
$ install --global
skillsauthnpx skillsauth add intent-solutions-io/plugins-nixtla testing-load-balancersInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 7:08 AM88.1s4 files scanned
SKILL.md
- name:
- testing-load-balancers
- description:
- |
- allowed-tools:
- Read, Bash, Grep, Glob
- version:
- 1.0.0
Overview
This skill empowers Claude to thoroughly test load balancing configurations, ensuring high availability and optimal performance. It automates the process of validating traffic distribution, simulating server failures, and verifying session persistence.
How It Works
- Initiating the Test: Claude receives a request to test the load balancer.
- Executing the Test Suite: Claude uses the
load-balancer-testerplugin to run a series of tests, including traffic distribution validation, failover testing, sticky session verification, and health check testing. - Presenting the Results: Claude provides a summary of the test results, highlighting any issues or areas for improvement.
When to Use This Skill
This skill activates when you need to:
- Validate traffic distribution across backend servers.
- Test the load balancer's ability to handle server failures.
- Verify that sticky sessions are functioning correctly.
- Ensure that health checks are effectively removing unhealthy servers from the pool.
Examples
Example 1: Validating Traffic Distribution
User request: "Test load balancer traffic distribution for even distribution across servers."
The skill will:
- Execute the
lb-testcommand. - Analyze the traffic distribution across the backend servers.
- Report whether the traffic is evenly distributed.
Example 2: Simulating a Failover Scenario
User request: "Test failover when one of the backend servers becomes unavailable."
The skill will:
- Execute the
lb-testcommand. - Simulate a server failure.
- Verify that traffic is redirected to the remaining healthy servers.
- Report on the success of the failover process.
Best Practices
- Configuration: Ensure the load balancer is properly configured before testing.
- Realistic Scenarios: Test with realistic traffic patterns and failure scenarios.
- Comprehensive Testing: Test all aspects of the load balancer, including traffic distribution, failover, sticky sessions, and health checks.
Integration
This skill works independently using the load-balancer-tester plugin. It can be used in conjunction with other skills to configure and manage the load balancer before testing.
Related Skills
intent-solutions-io/managing-test-environments
testing
VerifiedTrustedCommunity
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/generating-test-doubles
tools
VerifiedTrustedCommunity
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/generating-test-data
tools
VerifiedTrustedCommunity
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/analyzing-test-coverage
development
VerifiedTrustedCommunity
This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".
6SKILL.mdUpdated Jun 5, 2026