commercial-skills
by alirezarezvanicommercial-skills is a Revenue Operations orchestrator for pricing, deal desk review, discount approval, partnership and channel economics, commercial policy, RFP/RFI response, and bookings forecasts. Use it to route commercial questions to focused sub-skills and return a decision digest.
This skill scores 68/100, which means it is acceptable for directory listing but should be presented as a lightweight written orchestrator rather than a fully packaged automation. Directory users get enough clarity to know when to install it for commercial-pricing and deal-economics reviews, but should expect some dependency and adoption risk because there are no bundled support files and the orchestrated sub-skills may need to exist separately.
- Strong triggerability: the frontmatter names concrete invocation phrases such as deal review, discount approval, pricing model, RFP response, bookings forecast, and channel mix.
- Clear domain boundary: it distinguishes commercial deal economics and packaging from sales execution and broader CRO strategy, reducing accidental overuse.
- Sub-skill routing table and a substantial SKILL.md body indicate real workflow content rather than a placeholder or demo.
- It appears to be a single SKILL.md with no bundled scripts, references, resources, or README, so execution depends on the written playbook rather than reusable artifacts.
- The skill is framed as an orchestrator for seven Commercial sub-skills; if those sub-skills are not installed or discoverable in the user’s environment, routing may require extra interpretation.
Overview of commercial-skills skill
What commercial-skills is for
commercial-skills is a Commercial domain orchestrator for Claude-style agent workflows. It helps route revenue questions to the right commercial lens: pricing strategy, deal desk review, partnership economics, channel economics, commercial policy, RFP/RFI response, or bookings forecasting. Instead of asking a general AI prompt to “look at a deal,” the commercial-skills skill frames the work around per-deal economics, packaging, approval logic, and revenue risk.
Best-fit users and teams
This skill is strongest for Revenue Operations, sales operations, pricing teams, deal desk leaders, partnership teams, CRO staff, and founders who need structured commercial judgment without building a full RevOps playbook first. It is useful when the question is not “how do we sell more?” but “is this commercial motion economically sound, approvable, forecastable, and aligned with policy?”
What makes this skill different
The main differentiator is routing. The upstream SKILL.md defines commercial-skills as an orchestrator that forks context and delegates to seven commercial sub-skills, then returns a digest. That matters for heavy inputs such as RFP text, pipeline exports, partner terms, or discount requests because the agent can isolate the working context instead of mixing every commercial concern into one broad answer.
Where it fits in a Revenue Operations stack
Use commercial-skills for Revenue Operations decisions that sit between sales execution and executive strategy: discount governance, pricing model design, channel mix, reseller economics, RFP positioning, and bookings forecast review. It is not a CRM integration, CPQ engine, legal reviewer, or source of financial truth; it is a reasoning layer for preparing, challenging, and summarizing commercial decisions.
How to Use commercial-skills skill
commercial-skills install and first files to inspect
Install from the repository path used by your skill manager, for example:
npx skills add alirezarezvani/claude-skills --skill commercial-skills
Then read commercial/skills/commercial-skills/SKILL.md first. This repository entry appears to be a single-file skill: there are no visible scripts/, references/, resources/, rules/, README.md, or metadata.json support files in the skill folder. That makes install lightweight, but it also means the routing rules and operating guidance in SKILL.md are the source of truth.
Inputs the skill needs for useful commercial judgment
For strong commercial-skills usage, provide the commercial object, the decision needed, and the constraints. Useful inputs include current price, proposed price, discount level, ACV/ARR, term length, segment, product package, margin sensitivity, competitor pressure, procurement deadline, partner obligations, renewal risk, forecast category, and approval threshold.
Weak prompt:
Review this deal and tell me if the discount is okay.
Stronger prompt:
Use commercial-skills for Revenue Operations deal review. Enterprise customer, $180k ARR list price, rep requests 35% discount for a 3-year term, competitor claims 25% lower price, customer wants security addendum, implementation cost is high, renewal expansion potential is uncertain. Decide whether to approve, counter, repackage, or escalate. Include risks, missing data, and approval conditions.
How to invoke the right sub-skill behavior
The skill’s trigger language includes phrases such as “review this deal,” “should we discount,” “pricing model,” “partner economics,” “RFP response,” “bookings forecast,” and “channel mix.” Include one of those intents explicitly if you want reliable routing. If the request spans multiple areas, say which decision is primary: pricing strategy, deal approval, partnership structure, channel economics, policy design, RFP response, or forecast confidence.
Example:
Use commercial-skills. Primary route: commercial-forecaster. Secondary lens: deal-desk. Review whether this late-stage opportunity should remain in commit given discount dependency and unresolved procurement.
Practical workflow for commercial-skills usage
Start with one decision, not a broad commercial audit. Ask the skill to produce a digest with: recommendation, rationale, risks, missing information, approval path, and next actions. After the first output, feed back hard numbers or policy constraints rather than asking for “more detail.” For example: “Our maximum standard discount is 20%; CFO approval required above 30%; services margin must stay above 35%.” This materially improves the commercial answer.
commercial-skills skill FAQ
Is commercial-skills suitable for beginners?
Yes, if the user can describe the deal or revenue question clearly. Beginners should use a structured prompt with known facts, unknowns, and the decision deadline. The skill can help expose missing commercial inputs, but it cannot infer reliable pricing, margin, approval policy, or pipeline truth from vague context.
How is it better than an ordinary prompt?
An ordinary prompt often blends pricing, sales strategy, forecasting, and executive advice into one generic response. The commercial-skills skill is narrower: it is designed around commercial motion and routes to specialized sub-skill perspectives. That makes it more consistent for Revenue Operations work where the output needs to support an approval, counteroffer, forecast call, or policy decision.
When should I not use commercial-skills?
Do not use it as the final authority for legal terms, revenue recognition, tax, procurement compliance, or board-level strategy. It is also a poor fit for pure sales coaching, outbound sequencing, or account planning unless the core issue is pricing, packaging, discounting, partner economics, RFP response, or forecast treatment.
Does it require a specific AI tool?
The skill frontmatter lists compatibility with tools such as claude-code, codex-cli, cursor, antigravity, opencode, and gemini-cli. In practice, adoption depends on whether your environment supports skill installation and invocation from a GitHub path. Since this skill has no extra helper files, compatibility risk is lower than for script-heavy skills.
How to Improve commercial-skills skill
Improve commercial-skills inputs before asking for judgment
The fastest way to improve commercial-skills output is to provide the commercial math and the approval context. Add list price, proposed discount, term, payment terms, expected usage, services burden, forecast stage, close date, customer segment, channel involvement, and the actual decision you need. If you do not know a value, label it unknown instead of omitting it.
Common failure modes to watch for
The skill can become too generic when the prompt lacks numbers, policy boundaries, or a decision owner. It may also over-focus on one lens if the request is ambiguous, such as mixing RFP response, discount approval, and forecast review in a single sentence. Prevent this by naming the primary route and asking for secondary considerations separately.
Iterate from recommendation to operating action
After the first digest, ask for a tighter operating artifact: an approval memo, counteroffer structure, forecast note, RFP response outline, partner economics checklist, or pricing experiment plan. Good iteration prompts include constraints such as “keep the discount under 25%,” “preserve annual prepay,” “avoid custom packaging,” or “write this for CFO approval.”
Add local policy context for better fit
The upstream skill is intentionally general. To make commercial-skills more valuable inside a company, pair it with your actual discount matrix, package definitions, approval thresholds, reseller margin rules, RFP standards, forecast definitions, and escalation owners. That turns the skill from a commercial reasoning aid into a practical Revenue Operations assistant aligned with your operating model.