Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
4 business growth agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Customer success (health scoring, churn), sales engineer (RFP), revenue operations (pipeline, GTM), contract & proposal writer. Python tools (stdlib-only).
How this skill is triggered — by the user, by Claude, or both
Slash command
/business-growth-skills:business-growth-skillsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
4 production-ready skills for customer success, sales, and revenue operations.
4 production-ready skills for customer success, sales, and revenue operations.
/read business-growth/customer-success-manager/SKILL.md
npx agent-skills-cli add alirezarezvani/claude-skills/business-growth
| Skill | Folder | Focus |
|---|---|---|
| Customer Success Manager | customer-success-manager/ | Health scoring, churn prediction, expansion |
| Sales Engineer | sales-engineer/ | RFP analysis, competitive matrices, PoC planning |
| Revenue Operations | revenue-operations/ | Pipeline analysis, forecast accuracy, GTM metrics |
| Contract & Proposal Writer | contract-and-proposal-writer/ | Proposal generation, contract templates |
9 scripts, all stdlib-only:
python3 customer-success-manager/scripts/health_score_calculator.py --help
python3 revenue-operations/scripts/pipeline_analyzer.py --help
npx claudepluginhub dmlab3/claude-skills --plugin business-growth-skills27plugins reuse this skill
First indexed Jun 3, 2026
Showing the 6 earliest of 27 plugins
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.