business-growth-skills
by alirezarezvanibusiness-growth-skills routes Growth, revenue, sales, customer success, RevOps, RFP, and proposal requests to the right bundled specialist skill. Use it to choose customer-success-manager, sales-engineer, revenue-operations, or contract-and-proposal-writer with less guesswork.
This skill scores 67/100, which means it is acceptable for directory listing but should be presented as a lightweight router rather than a full workflow skill. Directory users get useful install-decision clarity about the bundle’s business-growth coverage, but the reviewed folder itself contains limited operational depth and depends on separate referenced skills for execution.
- Clear frontmatter description identifies when to use the router and names the four bundled business/growth domains.
- Routing table maps concrete request signals such as churn risk, RFP coverage, forecast accuracy, and SOWs to specific skill folders.
- Includes a simple rule to ask one clarifying question when multiple routing rows match.
- This is primarily a router/index, not a standalone business-growth workflow; actual execution depends on the four referenced sub-skills.
- No install command, README, support files, or deeper reference material are present in the reviewed skill folder.
Overview of business-growth-skills skill
What business-growth-skills is for
business-growth-skills is a routing skill for Growth, revenue, sales, customer success, and proposal work. Instead of trying to solve every business growth request itself, it helps an agent choose the right bundled specialist skill: customer-success-manager, sales-engineer, revenue-operations, or contract-and-proposal-writer.
Use it when the request is real but ambiguous, such as “which accounts are at risk?”, “should we bid on this RFP?”, “why is forecast accuracy slipping?”, or “draft a proposal for this opportunity.” The value is not a large knowledge base; it is faster skill selection with less guesswork.
Best-fit users and workflows
The business-growth-skills skill is best for operators, founders, RevOps teams, customer success leaders, sales engineers, and consultants who use an AI agent across mixed go-to-market tasks. It is especially useful when one conversation may move between account health, RFP response, pipeline inspection, and contract/proposal writing.
It fits Claude Code, Codex CLI, OpenClaw, or similar agent environments where skills are installed as reusable task instructions. It is less useful if you only ever need one fixed workflow, such as proposal writing only.
What makes this router different
The key differentiator is its explicit routing table. It maps request signals to a specific downstream skill path:
- Churn, health score, expansion →
customer-success-manager - RFP/RFI, competitive positioning, PoC plan →
sales-engineer - Pipeline coverage, forecast accuracy, GTM efficiency →
revenue-operations - Proposals, contracts, SOWs, DPAs →
contract-and-proposal-writer
This keeps the agent from using a generic “business strategy” response when a more structured specialist workflow should be loaded.
How to Use business-growth-skills skill
business-growth-skills install context
To install from the GitHub skill repository, use your skill manager’s GitHub installation flow. In environments that support npx skills add, the practical install pattern is:
npx skills add alirezarezvani/claude-skills --skill business-growth-skills
The source path is:
business-growth/skills/business-growth-skills/SKILL.md
This folder appears to contain only the router SKILL.md; there are no visible local rules/, resources/, references/, scripts/, or metadata.json files for this specific router. After installing, inspect the sibling specialist skill folders because the router’s main job is to send work there.
Inputs the skill needs to route correctly
Good business-growth-skills usage starts with a clear business request plus enough context to identify the correct lane. Include:
- The object of the work: account, opportunity, RFP, forecast, proposal, contract, pipeline segment
- The desired output: diagnosis, score, response plan, matrix, SOW, executive summary
- Any available data: CRM fields, account notes, usage trends, RFP requirements, renewal date, stage history
- Constraints: region, product line, deal size, legal limits, timeline, customer segment
- The decision you need to make: prioritize, bid/no-bid, escalate, forecast, expand, negotiate
Weak prompt:
Help with this customer.
Stronger prompt:
Use business-growth-skills to route this. I have a strategic account with declining product usage, a renewal in 60 days, two open support escalations, and a new executive sponsor. I need churn risk, health score reasoning, and the top three retention plays.
The stronger prompt points directly toward customer-success-manager and gives the downstream skill enough material to produce useful work.
Suggested routing workflow
Start by asking the agent to route before solving:
Use
business-growth-skillsfirst. Identify the best specialist skill, explain the routing reason in one sentence, ask one clarifying question only if multiple skills fit, then continue with the selected workflow.
For mixed requests, let the router sequence the work. Example:
We need to decide whether to respond to this RFP, assess competitive risk, and draft the first proposal outline. Use business-growth-skills to choose the right order of specialist skills.
A likely route would start with sales-engineer for RFP coverage and competitive positioning, then move to contract-and-proposal-writer once the bid strategy is clear.
Files to read first
Read business-growth/skills/business-growth-skills/SKILL.md first because it contains the routing table and quick-start logic. Then inspect the selected sibling skill’s SKILL.md before running a high-stakes task. The router itself is intentionally thin; output quality depends on loading the right specialist folder and providing enough business context.
business-growth-skills skill FAQ
Is business-growth-skills a standalone growth strategy skill?
Not really. business-growth-skills is primarily an index and router for Growth-related specialist skills. It can help an agent decide whether a request belongs to customer success, sales engineering, revenue operations, or contract/proposal writing, but the detailed work should happen in the selected specialist skill.
When should I use it instead of a normal prompt?
Use the business-growth-skills skill when the category of work is unclear or when a request spans multiple go-to-market functions. A normal prompt may produce a plausible but generic answer. This router improves the chance that the agent applies a more appropriate workflow, such as health scoring for churn risk or pipeline coverage analysis for forecast questions.
Is it beginner-friendly?
Yes, if you understand the basic business terms in the routing table. Beginners should phrase requests around the business decision they need, not around internal skill names. For example, say “I need to know whether to bid on this RFP” rather than guessing sales-engineer.
When is this skill a poor fit?
Do not use it for deep legal review, financial audit, CRM automation, data engineering, or market research that does not map to the four included business-growth categories. It also will not compensate for missing inputs. If you ask for churn risk without account data, the agent should ask for more context or produce only a lightweight framework.
How to Improve business-growth-skills skill
Improve business-growth-skills results with sharper requests
The fastest way to improve business-growth-skills output is to provide routing signals upfront. Instead of asking “what should we do about Q4 growth?”, specify whether the problem is retention, sales conversion, forecast quality, proposal creation, or deal qualification.
Better prompt pattern:
Route this with business-growth-skills. Context: [business situation]. Data available: [CRM/RFP/account/pipeline fields]. Decision needed: [retain, expand, bid, forecast, draft]. Output format: [table, action plan, scorecard, executive memo].
This reduces ambiguity and helps the agent avoid blending incompatible workflows.
Watch for common failure modes
The main failure mode is over-routing: the agent may try to use several specialist skills when one would be cleaner. Ask it to choose one primary skill unless the task clearly has phases.
Another failure mode is premature drafting. For example, a proposal should not be drafted before the RFP fit and competitive position are understood. In that case, instruct the agent to route to sales-engineer first, then move to contract-and-proposal-writer.
Iterate after the first routed output
After the first answer, improve the result by challenging the route:
- “What evidence made you choose this skill?”
- “Which sibling skill was the closest alternative?”
- “What missing data would change the route?”
- “Turn this into the selected skill’s ideal input brief.”
This is especially useful for ambiguous Growth work where customer success, sales engineering, and RevOps signals overlap.
Extend the router for your operating model
Teams can improve the business-growth-skills skill by adding internal routing rules, such as company-specific deal stages, health score inputs, RFP qualification thresholds, renewal risk definitions, or approval paths for SOWs and DPAs. Keep additions short and decision-oriented. A router should help the agent choose the right workflow quickly, not become a duplicate of every specialist skill.