尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证Revenue Growth Agent plugin for Claude: meeting prep, MEDDIC discovery, deal checks, proposals and SOWs.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Run Revenue Growth Agent (RGA) from Claude with a plain request: meeting prep, MEDDIC discovery analysis, deal checks, proposals and SOWs. The plugin bundles the RGA connector with skills that run each workflow in the right order, with the right checkpoints.
You need an RGA account. Sign up at revenuegrowthagent.com.查看完整 README ↗Run Revenue Growth Agent (RGA) from Claude with a plain request: meeting prep, MEDDIC discovery analysis, deal checks, proposals and SOWs. The plugin bundles the RGA connector with skills that run each workflow in the right order, with the right checkpoints.
You need an RGA account. Sign up at revenuegrowthagent.com.
| Skill | Ask something like |
|---|---|
meeting-prep | "Run a meeting prep on Jordan Lee at Acme." Or paste a list of trade show leads. |
daily-briefing | "Prep everyone I'm meeting for the first time today." Runs as a 7am scheduled task. |
discovery-analysis | "Here's my transcript from the Acme call. Run a MEDDIC analysis." |
deal-check | "Where do we stand with Acme? What are the open gaps?" |
proposal-sow | "Create a proposal for Acme: $15,000 a month for three months, built around a $1M ROI." |
call-autopilot | "Score my sales calls from today and log them to the CRM." Runs every 2 hours as a scheduled task. |
crm-sync | "Add this prep to HubSpot." / "Log the MEDDIC on the Acme opportunity in Salesforce." |
setup | "Is RGA connected? Which org am I in?" |
daily-briefing and call-autopilot also use your own calendar, email, notetaker and CRM connectors in Claude. RGA never writes to your CRM itself: crm-sync has Claude do it through your CRM connector (HubSpot, Salesforce, Microsoft Dynamics 365, Pipedrive, GoHighLevel and others), finding records before creating them, adding one consistent note with the RGA link, and asking before it writes.
Everything RGA does runs through the RGA connector this plugin includes, under your own RGA login and the organization you choose when connecting.
discovery-analysis and call-autopilot skills have Claude upload it directly to www.revenuegrowthagent.com with a one-time upload link (a curl command in Claude's code sandbox), so long transcripts aren't retyped into the chat. Nothing is uploaded anywhere else.crm-sync, daily-briefing and call-autopilot skills have Claude write contacts and notes to your CRM through your own CRM connector in Claude. RGA itself never connects to your CRM. Notes hold summaries and RGA links, never transcripts.The plugin itself stores nothing and runs no code of its own; it contains only skill instructions and the connector address. See the privacy policy and terms.
Claude (web, desktop, mobile) and Cowork
mattoess/rga-plugin.Already connected RGA as a connector? That's fine. Keep it, or remove it and use the plugin's.
Claude Code
/plugin marketplace add mattoess/rga-plugin
/plugin install rga@rga
Teams: a Team or Enterprise owner can install it for everyone under Organization settings > Plugins & skills.
Setup guide and FAQ: revenuegrowthagent.com/mcp-connector
.claude-plugin/plugin.json plugin manifest (bump version on every release)
.claude-plugin/marketplace.json lets this repo act as its own install source
.mcp.json the RGA connector (remote, OAuth)
skills/<name>/SKILL.md one folder per workflow
The connector itself lives in the rga-mcp repo. It enforces the rules that matter whatever a skill says: tenant isolation, a closed list of industries, explicit confirmation before a prep runs, explicit deal choice before a transcript is added to an existing opportunity, and human approval in RGA before a SOW. The skills cover the order of steps, what to ask the seller, and how to present results. They don't restate the server's rules, so there's nothing here to drift.
The connector also ships the same seven workflows as MCP prompts, for clients that don't install plugins.
claude plugin validate --strict .claude-plugin/plugin.json
claude --plugin-dir .
CI runs the same validation, checks each skill's name matches its folder, and fails if a skill names a tool the connector doesn't register.