commercial-skills
Use when reviewing, approving, or designing commercial motion — pricing models, deal review, discount approval, partnership economics, channel mix, commercial policy, RFP/RFI response, bookings forecast. Triggers on "review this deal", "should we discount", "pricing model", "partner economics", "RFP response", "bookings forecast", "channel mix". Forks context to route to one of seven Commercial sub-skills (pricing-strategist, deal-desk, partnerships-architect, channel-economics, commercial-policy, rfp-responder, commercial-forecaster) and returns a digest. Distinct from business-growth (sales
npx skills add alirezarezvani/claude-skills --skill commercial-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Commercial — Domain Orchestrator The Commercial surface is **per-deal economics and packaging**: how the company prices, packages, approves, and forecasts revenue. This orchestrator forks its context, routes your inquiry to one of seven sub-skills, then returns a digest. Heavy intake (RFP PDFs, pipeline exports, partner agreements) stays in the forked context. ## When to invoke | Symptom | Sub-skill | |---|---| | "We're losing deals on price — should we drop prices or repackage?" | `pricing-strategist` | | "Can we approve a 40% discount on this Enterprise deal?" | `deal-desk` | | "Should we sign with this reseller? What's their tier?" | `partnerships-architect` | | "Is our partner channel actually profitable?" | `channel-economics` | | "What should our standard discount matrix look like?" | `commercial-policy` | | "Help me respond to this 60-page RFP" | `rfp-responder` | | "What's our Q4 bookings forecast at current conversion?" | `commercial-forecaster` | ## Routing logic (deterministic) Same two-signal threshold pattern as `business-operations-skills`. Single-signal → clarifying question. Mixed signals → highest-confidence first, chain second in follow-up turn. ### Signal table
- When to invoke
- Routing logic (deterministic)
- Signal table
- Workflow (Matt Pocock grill discipline)
- Step 1 — Explore before asking
- Step 2 — If still ambiguous, ONE forcing question with a recommended answer
- Step 3 — Decision-tree walk for multi-lane inquiries
- Step 4 — Invoke sub-skill in forked context
- Step 5 — Return digest with cited canon challenge
- Forcing-question library (grill-with-docs pattern)
- Assumptions
- Non-goals
- Distinct from
- Output artifacts
What does the commercial-skills skill do?
Use when reviewing, approving, or designing commercial motion — pricing models, deal review, discount approval, partnership economics, channel mix, commercial policy, RFP/RFI response, bookings forecast. Triggers on "review this deal", "should we discount", "pricing model", "partner economics", "RFP response", "bookings forecast", "channel mix". Forks context to route to one of seven Commercial sub-skills (pricing-strategist, deal-desk, partnerships-architect, channel-economics, commercial-policy, rfp-responder, commercial-forecaster) and returns a digest. Distinct from business-growth (sales
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill commercial-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.