Hmps Claude Marketplace
hmps-claude-marketplace is a Claude Code plugin marketplace for the Ship phase that distributes official hmps testing extensions focused on Playwright and browser e2e automation.
by hmps · github.com/hmps/claude-marketplace
Add the official hmps marketplace when you need Playwright-style browser automation and e2e testing skills invoked from Claude Code during ship prep.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install hmps-claude-marketplace@hmps/claude-marketplaceBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:hmps/claude-marketplace") and the paste-ready config with skillselion.get_install_config("plugin:hmps/claude-marketplace").
What it does
hmps-claude-marketplace is the published hmps extension catalog for Claude Code, bundling two plugins aimed at developers who want agent-triggered end-to-end checks instead of manual QA loops. Keywords highlight Playwright, browser automation, e2e, frontend, and Vaam, with catalog categories spanning testing and admin—useful when you ship web apps or internal tools and need Claude to drive browsers, assert UI state, and fold results back into the same session. Solo builders on Cursor-adjacent stacks can still browse the marketplace for patterns, but install paths are framed for Claude Code and clawd-style model-invoked skills. Treat it as a focused testing shelf: you get a small, official set rather than a broad journey methodology. Intermediate complexity reflects real browser dependencies and flake handling. Confidence is solid on positioning from repo metadata though individual plugin README depth was not inlined here.
Highlights
- Official hmps plugin marketplace with 2 Claude Code extensions
- Keywords emphasize Playwright, browser-automation, e2e, and web-testing for frontend flows
- Includes model-invoked testing and Vaam-oriented tooling for agent-driven verification
- Tagged catalog categories: testing and admin for extension maintenance workflows
- Skills + tools layout suited to Claude Code rather than a standalone CLI-only runner
Why builders use it
Shipping without automated browser coverage means you catch broken flows only after users do, and manual Playwright runs do not stay attached to your agent session.
After registering the marketplace, you can install hmps testing plugins so Claude Code invokes structured e2e and web-testing skills during pre-release verification.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is hmps-claude-marketplace for?
It is for Claude Code users—often frontend-leaning solo builders—who need hmps-maintained plugins for browser automation, e2e, and web-testing rather than rolling their own Playwright prompts.
When should I use hmps-claude-marketplace?
Use it in the Ship phase when you are hardening releases, adding regression coverage, or letting the model invoke Vaam/Playwright workflows before you tag a version.
How do I add hmps-claude-marketplace to my agent?
Add the hmps/claude-marketplace source in Claude Code, install the two listed plugins, ensure Playwright/browser prerequisites for your stack, then trigger the testing skills from ship or review tasks.
Comments
Share how you use hmps-claude-marketplace, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.