Back to catalog
Human reviewedDevelopment

Skill dossier

test-master

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A testing skill that plans scope, writes unit, integration and E2E tests, executes them, triages failures and flaky tests, and reports findings with severity ratings.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Defines test scope and strategy across functional, performance and security perspectives.
  • Writes tests with specific assertions and mocked external dependencies.
  • Classifies failures and isolates flaky tests.
  • Reports findings with severity ratings and coverage gaps.

Limitations & scope

  • The inline example is a Jest test; other frameworks are covered through reference files.
  • Performance and security testing depend on external tools such as k6 and need setup.
  • Coverage targets are not defined in the skill and must come from the project.

Relevant for

  • QA engineers and test automation developers
  • Developers writing unit and integration tests
  • Teams fixing flaky suites

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
11
Markdown files
11
scripts
0
references
10
Size
46 KB
Structural complexity
Moderate

File inventory

PathTypeBytes
skills/test-master/references/automation-frameworks.mdReference7.2 KB
skills/test-master/references/e2e-testing.mdReference3.3 KB
skills/test-master/references/integration-testing.mdReference2.7 KB
skills/test-master/references/performance-testing.mdReference2.6 KB
skills/test-master/references/qa-methodology.mdReference6.2 KB
skills/test-master/references/security-testing.mdReference3.3 KB
skills/test-master/references/tdd-iron-laws.mdReference4.3 KB
skills/test-master/references/test-reports.mdReference2.3 KB

SKILL.md frontmatter

{
  "name": "test-master",
  "description": "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.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.1",
    "domain": "quality",
    "triggers": "test, testing, QA, unit test, integration test, E2E, coverage, performance test, security test, regression, test strategy, test automation, test framework, quality metrics, defect, exploratory, usability, accessibility, localization, manual testing, shift-left, quality gate, flaky test, test maintenance",
    "role": "specialist",
    "scope": "testing",
    "output-format": "report",
    "related-skills": "fullstack-guardian, playwright-expert, devops-engineer, debugging-wizard, code-reviewer, feature-forge"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Define scope

    Identify what to test and which testing types apply.

  2. 02
  3. 03
    Decision

    Triage failures

    If tests fail, classify the failure as assertion error or environment/flakiness, fix the root cause and re-run.

  4. 04
    Output

    Report findings

    Provide scope, test cases, coverage analysis, severity-rated findings and fix recommendations.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

147 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

130 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 130 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

8 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

9 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 9 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Check that generated tests and fixtures never touch real APIs, databases or production data before running them.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/test-master # .claude/skills/test-master
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/test-master/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm SKILL.md is discoverable at the destination, then ask Claude Code to use test-master on a small task.

Prerequisites

  • The inline example is a Jest test; other frameworks are covered through reference files.
  • Performance and security testing depend on external tools such as k6 and need setup.
  • Coverage targets are not defined in the skill and must come from the project.

Example prompts

Representative task

Use the test-master skill to write Jest unit tests for calculateDiscount covering happy paths, negative prices and boundary values, then list any coverage gaps in a severity-rated report.

Inspect before use

Read the test-master skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/test-master/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Clear MUST and MUST NOT rules, such as no order-dependent tests and no production data.
  • Ten reference files, including TDD and anti-pattern guidance.

Considerations

  • Very broad scope, so output depth depends on which references get loaded.
  • Mocking guidance should be checked against the project's actual test setup.
Research conclusion

A broad, rule-driven QA skill that works best when paired with a project's existing test framework.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/test-master
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.