Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Multi-agent Playwright test generation system that creates thorough, production-ready test suites one page at a time
npx claudepluginhub trusted-american/marketplace --plugin playwrightYou are the final quality gate for Playwright test suites. You receive the spec file and findings from both the frequency-reviewer and flakiness-reviewer agents. Your job is to produce a production-ready test suite.
You are a test reliability engineer. You specialize in finding and eliminating sources of flakiness in Playwright tests. Your goal: every test must pass 100% of the time, in any order, in any environment.
You are a test efficiency analyst. You evaluate Playwright tests based on how likely the tested scenario is to occur in production and how valuable the test is for catching real bugs.
You are a senior QA engineer specializing in finding critical test gaps. You receive a page investigation summary and a list of edge cases already being covered by another agent. Your job is to find what's MISSING.
You are a Playwright test engineer specializing in writing thorough, reliable end-to-end tests. You receive a page investigation summary and a list of user-specified edge cases to cover.
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Production-grade Playwright testing toolkit. Generate tests from specs, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55+ ready-to-use templates, 3 specialized agents, smart reporting that plugs into your existing workflow.
End-to-end test automation with Playwright, Cypress, and Selenium for browser-based testing
Playwright E2E test debugging and interactive browser exploration. Runs tests with action capture (DOM snapshots, network, console, screenshots), diagnoses failures, and provides browser tools for navigating, clicking, and inspecting pages through ARIA snapshots.
Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing, visual regression, API testing, component testing in TypeScript/JavaScript and Python projects.
End-to-end test execution and recording for web applications
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Multi-agent algorithm intelligence system that analyzes codebases for optimization opportunities, researches cutting-edge algorithms via deep web research, identifies complexity bottlenecks, and applies superior data structures and algorithms with before/after benchmarking. 3 commands, 7 agents, 1 skill, 3 templates.
Fullstack development agent for the A3 platform — orchestrates Ember.js, Firebase/Firestore, and GCP Cloud Functions with deep codebase knowledge, round-robin review, and GitHub-authenticated access control
Multi-agent reverse engineering system with 10 specialized agents, 3 commands, and continuous fidelity assurance. Deeply researches any software via Firecrawl, Perplexity, and web intelligence; extracts architecture and features; analyzes competitors for UX, adoption, and feature parity; generates implementation blueprints; builds autonomous clones with orchestrated agent teams; and maintains fidelity through automated drift detection and self-healing loops. 3 commands, 10 agents, 1 skill, 4 templates.
Plugin registry for Claude Code, maintained by Trusted American Insurance Agency.
marketplace/
├── plugins/ # First-party plugins
├── community/ # Third-party forks and adaptations
├── .claude-plugin/
│ └── marketplace.json # Auto-generated plugin index (do not edit)
├── tools/
│ ├── lib/registry.js # Shared registry generation logic
│ ├── generate-marketplace-json.js # CLI script to regenerate marketplace.json
│ └── marketplace-mcp/ # MCP server for plugin management
├── .github/workflows/ci.yml # Validation + registry generation
└── .mcp.json # Auto-loads the MCP server in Claude Code
Every plugin in plugins/ or community/ must contain these files:
| File | Purpose |
|---|---|
README.md | Usage documentation |
LICENSE | License file |
.claude-plugin/plugin.json | Plugin manifest |
Components go in the plugin root, never inside .claude-plugin/:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Manifest — only file in this directory
├── skills/ # Each skill is a subdirectory with a SKILL.md
│ └── skill-name/
│ └── SKILL.md
├── agents/ # Agent definitions (.md files)
│ └── agent-name.md
├── commands/ # Slash command definitions (.md files)
│ └── command-name.md
├── hooks/ # Hook configurations (.json files)
│ └── hooks.json
├── templates/ # Output templates (.md files)
│ └── template-name.md
├── .mcp.json # MCP server config (optional)
├── README.md
└── LICENSE
The name field is required and must be kebab-case (^[a-z0-9-]+$). All other fields are optional but recommended.
{
"name": "my-plugin",
"version": "0.1.0",
"description": "What this plugin does",
"author": { "name": "Author Name" },
"license": "MIT",
"keywords": ["keyword1", "keyword2"],
"repository": "https://github.com/org/repo"
}
Names must be unique across the entire marketplace. If two plugins share a name, CI will warn and the second one overwrites the first in .claude-plugin/marketplace.json.
.claude-plugin/marketplace.json is a generated index of all plugins. It is not updated in PRs. The flow:
main.node tools/generate-marketplace-json.js, which scans plugins/ and community/, reads each plugin.json, collects component directories, and writes .claude-plugin/marketplace.json.main with [skip ci] to avoid a loop.The lastUpdated timestamp updates on every run. The generation logic lives in tools/lib/registry.js and is shared between the CLI script and the MCP server.
The MCP server at tools/marketplace-mcp/ auto-loads when you open this repo in Claude Code (configured in .mcp.json). It exposes 6 tools:
| Tool | What it does |
|---|---|
create_plugin | Scaffolds a new plugin with required files and correct directory structure |
validate_plugin | Checks a plugin for required files, valid manifest, and component structure |
validate_all | Validates every plugin in plugins/ and community/ |
list_plugins | Lists all plugins with version, description, and component breakdown |
add_component | Adds a skill, agent, command, hook, or template to an existing plugin |
get_conventions | Returns the full marketplace conventions document |
Validation checks: required files exist, plugin.json is valid JSON with a kebab-case name, and any component directories that exist contain correctly typed files (.md for skills/agents/commands/templates, .json for hooks).
Every push and PR runs two jobs:
plugins/ and community/ for README.md, LICENSE, and a valid .claude-plugin/plugin.json with a kebab-case name.npm test in tools/marketplace-mcp/ (vitest, 57 tests covering validation, registry generation, component handling, and security).On merge to main, a third job runs:
.claude-plugin/marketplace.json and commits it.Prerequisites: Claude Code and Node.js 18+ (22 recommended).
git clone https://github.com/trusted-american/marketplace.git
cd marketplace
npm ci --prefix tools/marketplace-mcp
Open the repo in Claude Code. The MCP server loads automatically. Run list plugins to verify.
If you use the jira-orchestrator plugin for Jira/Confluence integration: