commercial-policy

Solid

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Use when authoring a policy charter, defining discount/payment/liability rules, auditing deals, or generating a regional policy.

AI & Automation 740 stars 135 forks Updated 4 weeks ago NOASSERTION

Install

View on GitHub

Quality Score: 83/100

Stars 20%
96
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Commercial Policy End-to-end commercial-policy authoring and governance: defining the rules that govern what sales can offer, what triggers approval, and what's prohibited. Pairs with our deal-desk (operational enforcement) and pricing-strategy (price-setting) skills — this is the policy that those execute against. A good commercial policy: - Makes deal-desk faster (fewer ambiguous cases) - Makes sales reps more autonomous (clearer authority) - Makes legal reviews lighter (most cases already covered) - Reduces concession drift over time - Provides audit-ready governance documentation --- ## When to use this skill | Situation | Skill applies | |-----------|---------------| | Authoring commercial policy from scratch | Yes — start with **policy charter template** + `scripts/commercial_policy_generator.py` | | Refreshing an existing policy (annual) | Yes — see **annual policy review** workflow | | Auditing recent deals for policy compliance | Yes — `scripts/policy_compliance_checker.py` | | Analyzing terms-deviation patterns | Yes — `scripts/terms_deviation_analyzer.py` | | Tailoring policy for new region / vertical | Yes — `scripts/commercial_policy_generator.py --region <X>` | | Drafting sales training on policy | Yes — see **training section** | | Setting prices (not policy on deviations) | Use `business-growth/pricing-strategy` | | Per-deal approval | Use `business-growth/deal-desk` | | Writing the specific contract | Use `business-growth/contract-and-proposal-writer` ...

Details

Author
borghei
Repository
borghei/Claude-Skills
Created
8 months ago
Last Updated
4 weeks ago
Language
HTML
License
NOASSERTION

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

sales-negotiation

Prepare or review a commercial negotiation for a specific sales opportunity. Use when the user must evaluate a discount request, scope trade, payment schedule, contract length, concession, renewal term, walk-away point, or package of deal options. Use sales-objection-handling instead when the immediate task is understanding or answering a value, trust, fit, or timing concern without designing a concrete trade. Do not use for company-wide pricing, packaging, or offer strategy; use pricing or offers skills for those when available.

0 Updated 1 weeks ago
sumitake
AI & Automation Listed

usage-policy-writer

Generate a human-facing AI usage policy with approved tools, data classification, risk model explanations, and exception processes — saved to $HOME/.ai-first-kit/. Produces a policy document for HUMANS (not agents) that explains what AI tools are approved, what data can be used with AI, and the reasoning behind each decision. Use when the user says 'AI usage policy', 'AI handbook', 'what tools are approved', 'data classification for AI', 'AI rules for the team', 'usage guidelines', 'AI policy', 'human AI rules', 'acceptable use policy', or 'what can we use AI for'. Also use when the user describes people unsure what they're allowed to do with AI, different teams having different answers about approved tools, no clear policy about client data and AI, or needing to explain the 'why' behind AI rules — even if they don't use the word 'policy'. This skill MUST be consulted because it produces a structured human-facing policy with risk model reasoning and exception processes; a conversational answer cannot create t

6 Updated today
synaptiai
AI & Automation Listed

policies-validator

Company policy guardrail for every Claude response. Use this skill ALWAYS before answering any question, drafting any output, running any task, or recommending any action that could touch company policy. Triggers include: drafting external or internal communications, handling data of any classification, making decisions about tools or vendors, summarising or forwarding content, content generation of any kind, recommending technical approaches with security implications, and any task or prompt that processes organisational data. If the user asks anything that could implicate the AI use policy, Claude guidelines, Code of Conduct, data classification, acceptable use, or related policies, this skill MUST be consulted first. Applies three enforcement tiers: hard block (T1), required check (T2), soft guidance (T3).

2 Updated 2 days ago
KalastajaM