Grailautomation Claude Plugins
grailautomation-claude-plugins is a Claude Code plugin marketplace for the Build phase that packages twenty-five automation, integration, and browser-testing plugins from Grail Automation.
by grailautomation · github.com/grailautomation/claude-plugins
Register Grail Automation’s marketplace when you want Claude Code plugins for Google Workspace, Salesforce, QuickBooks, Playwright scraping, OpenAPI specs, and macOS automation in one place.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install grailautomation-claude-plugins@grailautomation/claude-pluginsBuilt 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:grailautomation/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:grailautomation/claude-plugins").
What it does
grailautomation-claude-plugins is a large Claude Code plugin marketplace—twenty-five entries—aimed at developers and solo builders who treat Claude as an integration and automation workbench. Rather than one narrow skill, the bundle spreads across API connectors, spec-driven OpenAPI workflows, browser automation with Playwright, financial and CRM bridges, and macOS quality-of-life tooling. Indie SaaS founders can register it once when they are building glue code: parsing specs, filling forms, querying SOQL, managing issues, or generating SDK-shaped scaffolding. The canonical journey placement is Build integrations because most plugins reduce time-to-wire for external services, but several plugins naturally support ship-time testing and operate-time pipeline or edge configuration. Expect intermediate complexity: you still own credentials, rate limits, and idempotent job design. Grail’s collection reads like an automation studio inside Claude Code—commands, recipes, and connector patterns—rather than a methodology skill. Pick individual plugins selectively; the full marketplace is best when your product touches Google, Salesforce, browsers, or OpenAPI-first APIs.
Highlights
- Twenty-five-plugin Claude Code marketplace from Grail Automation covering broad automation scope.
- Google Workspace, Salesforce, QuickBooks, Namecheap, and GitHub-oriented integration and scaffolding patterns.
- Playwright and browser automation, scrapers, screenshots, and online research helpers.
- OpenAPI spec-driven generation, Context7-style discovery, and reusable skill or command libraries.
- macOS personal automation touches: Karabiner Elements, Espanso expander, and keyboard mapping utilities.
Why builders use it
Solo builders reimplement the same connector, scraper, and OpenAPI boilerplate across Claude sessions instead of reusing a shared plugin library.
After registration, you can install targeted Grail plugins for Google, CRM, finance, Playwright, and spec-driven codegen without hunting one-off repos each sprint.
At a glance
- Type - Plugin in Automation.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is grailautomation-claude-plugins for?
It is for Claude Code users—especially solo SaaS builders—who want Grail Automation’s connectors, scrapers, OpenAPI tooling, and desktop automation plugins in one marketplace.
When should I use grailautomation-claude-plugins?
Use it while building and integrating external services, and when you need Playwright, spec-driven codegen, or workspace automation during test and operate tasks.
How do I add grailautomation-claude-plugins to my agent?
Add the grailautomation/claude-plugins repository as a Claude Code marketplace source, then enable only the plugins that match your stack and credentials.
Comments
Share how you use grailautomation-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.