qa-localization

testland-qa

A rigorously curated quality-engineering plugin marketplace for Claude Code. 77 plugins, 695 components, every one rating-gated before merge.

Why testland-qa

• 6-dimension quality rubric (D1–D6) before merge, with a hard-reject for uncited claims (citation theater) via the d6 floor
• CI-validated composition: every agent's preloaded skills are reference-checked, no dangling deps
• Differentiation required: every component must articulate how it differs from its nearest neighbors. Generic, persona-shaped scopes that can't name a trigger condition get sent back for reshaping
• Reviewer-calibrated: two-evaluator rubric, A/C/F-grade exemplars in docs/REVIEWER_TRAINING.md

See Quality bar and docs/REVIEWER_CHECKLIST.md.

How it works

The marketplace ships three kinds of building block:

• Plugin — an installable bundle scoped to one QA area (e.g. qa-api-testing, qa-load-testing). You install only the plugins your stack needs.
• Skill — an atomic, self-contained capability inside a plugin, usually wrapping one tool or one technique (e.g. great-expectations, oauth-flow-test-author). Claude loads a skill when your request matches its trigger; you can also ask for it by name.
• Agent — a task-scoped subagent that runs one focused job (e.g. schema-diff-reviewer reviews a migration diff and returns a findings table). An agent may preload one or more skills to do its work.

Installed components stay dormant until a matching task comes up, so adding a plugin doesn't add noise — it adds capability that activates on demand.

Install

Claude Code marketplace (recommended)

/plugin marketplace add testland/qa
/plugin install <plugin-name>@testland-qa

For example:

/plugin install qa-data-quality@testland-qa

Direct URL

/plugin marketplace add https://github.com/testland/qa

Manual / hermetic environments

git clone https://github.com/testland/qa ~/.claude/marketplaces/testland-qa

Before you install: plugins run inside your Claude Code session and ship agent instructions and tool wrappers. Anthropic doesn't vet marketplace contents — review a plugin's components before installing it into a sensitive project. Every component here is rating-gated (see Quality bar), but you remain in control of what runs.

Start here

New to the marketplace? Install one or two plugins for your role rather than everything — components activate on demand, so a focused set keeps things sharp.

If you're a…	Try first
Manual / exploratory tester	qa-manual-testing · qa-bdd · qa-bug-repro
Test automation engineer	qa-web-e2e · qa-api-testing · qa-unit-tests-js
Performance engineer	qa-load-testing · qa-chaos-resilience
Security tester	qa-sast · qa-secrets · qa-dast
Lead / manager / head of quality	qa-roles · qa-test-management · qa-process

The full catalog is below; for versions and component counts see CATALOG.md.

Using an installed plugin

Once a plugin is installed, its skills and agents are available to Claude Code — invoke them by describing the task in plain language. Example with qa-data-quality:

/plugin install qa-data-quality@testland-qa

• Ask "add Great Expectations checks to my orders pipeline" → the great-expectations skill scaffolds an ExpectationSuite + Checkpoint and wires the results into a CI gate.
• On a database change, ask "review this migration's schema diff" → the schema-diff-reviewer agent returns a Critical / Warning / Info findings table covering breaking-vs-additive changes and downstream impact.

Each plugin's README.md lists its skills and agents and what each one does.

Plugin catalog