Agent skill · Security

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.

Jeffallangithub.com/JeffallanGitHub ↗
claude-codeMIT
Install
npx skills add Jeffallan/claude-skills --skill test-master --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.1.1
Declared author: https://github.com/Jeffallan
Path: skills/test-master/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Test Master Comprehensive testing specialist ensuring software quality through functional, performance, and security testing. ## Core Workflow 1. **Define scope** — Identify what to test and which testing types apply 2. **Create strategy** — Plan the test approach across functional, performance, and security perspectives 3. **Write tests** — Implement tests with proper assertions (see example below) 4. **Execute** — Run tests and collect results - If tests fail: classify the failure (assertion error vs. environment/flakiness), fix root cause, re-run - If tests are flaky: isolate ordering dependencies, check async handling, add retry or stabilization logic 5. **Report** — Document findings with severity ratings and actionable fix recommendations - Verify coverage targets are met before closing; flag gaps explicitly ## Quick-Start Example A minimal Jest unit test illustrating the key patterns this skill enforces: ```js // ✅ Good: meaningful description, specific assertion, isolated dependency describe('calculateDiscount', () => { it('applies 10% discount for premium users', () => { const result = calculateDiscount({ price: 100, userTier: 'premium' }); expect(result).toBe(90); // sp

What's inside
Steps it walks through
  1. Core Workflow
  2. Quick-Start Example
  3. Reference Guide
  4. Constraints
  5. Output Templates
Ships with 10 files
  • references/automation-frameworks.md
  • references/e2e-testing.md
  • references/integration-testing.md
  • references/performance-testing.md
  • references/qa-methodology.md
  • references/security-testing.md
  • references/tdd-iron-laws.md
  • references/test-reports.md
  • references/testing-anti-patterns.md
  • references/unit-testing.md
More from claude-skills
All skills →
About this skill
What does the test-master skill do?

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill test-master --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going