Agent skill

Commercial Policy

by borghei in borghei/Claude-Skills

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval.

MITAuto-check passedMarketing & SEO

Install Commercial Policy

skills CLI
$ npx skills add borghei/Claude-Skills --skill commercial-policy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills commercial-policy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-growth/commercial-policy .claude/skills/commercial-policy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commercial-policy
GitHub stars
891
Token cost
~3.9k tokens
SKILL.md length
1,048 words
Files
7 (incl. scripts, references)
Skills in repo
354
Repo updated
First seen
Licence
MIT

At a glance

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval.

  • Works in 10 steps: Assemble policy committee — CRO + CFO +… → Inventory current deals — what terms… → Identify policy gaps — areas where… → …
  • Authoring a policy charter
  • SKILL.md covers When to use this skill, What commercial policy covers, Commercial policy charter… and Discount and terms policy…, plus 7 more sections
  • Runs Python scripts from its folder

What it does

Commercial Policy is an agent skill from borghei/Claude-Skills. 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.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/commercial-policy-charter.md`, `references/contract-and-commercial-guardrails.md` and `references/discount-and-terms-policy.md`).

It sits in Marketing & SEO. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Authoring a policy charter
  • Defining discount/payment/liability rules
  • Generating a regional policy

Example prompts

  • “/commercial-policy”

Requirements

  • Python 3

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Assemble policy committee — CRO + CFO + GC sponsors + Deal Desk Lead + Sales Operations
  2. Inventory current deals — what terms have been offered? What's been ad-hoc?
  3. Identify policy gaps — areas where ad-hoc behavior is hurting (concession drift, customer surprises)
  4. Draft charter using template; one section per domain
  5. Internal review — Sales VP, Eng VP, CISO, Customer Success VP, Finance for revenue recognition
  6. Pilot with sales managers for 30 days — collect feedback
  7. Final approval — CRO + CFO + GC sign-off; board awareness
  8. Sales training — workshop + recorded session + quick-reference cards
  9. Publish to sales wiki / partner portal / customer-facing communications team
  10. Quarterly review thereafter

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commercial Policy loads about 3.9k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 1,048 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,048 words, ~3,880 tokens.

Download SKILL.mdSave it as .claude/skills/commercial-policy/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
commercial-policy
description
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.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
commercial
metadata.domain
business-growth
metadata.updated
2026-05-27
metadata.tags
commercial-policy, governance, contract-policy, pricing-policy, sales-governance, deal-policy, gtm

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

SituationSkill applies
Authoring commercial policy from scratchYes — 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 complianceYes — scripts/policy_compliance_checker.py
Analyzing terms-deviation patternsYes — scripts/terms_deviation_analyzer.py
Tailoring policy for new region / verticalYes — scripts/commercial_policy_generator.py --region <X>
Drafting sales training on policyYes — see training section
Setting prices (not policy on deviations)Use business-growth/pricing-strategy
Per-deal approvalUse business-growth/deal-desk
Writing the specific contractUse business-growth/contract-and-proposal-writer

What commercial policy covers

Standard scope:

DomainPolicy area
PricingStandard pricing, discount thresholds, MFN, rebates, custom-bundle pricing
ContractStandard term length, payment terms, renewal terms, termination, customer audit rights
LegalAcceptable MSA modifications, liability cap, indemnification, jurisdiction, IP
OperationalSLA tiers, custom SLAs, security commitments, dedicated infrastructure
Customer commitmentsReference / case study / press release obligations
ChannelPartner discount tiers, channel-conflict rules, deal-registration
Special termsPerformance-based payment, acceptance criteria, ramp deals

What it doesn't cover:

  • Day-to-day pricing decisions (that's pricing strategy)
  • Per-deal approval mechanics (that's deal-desk operations)
  • Sales targets / quota (that's compensation policy)
  • Customer success / churn-prevention tactics

Commercial policy charter (template)

The foundational document. Every company that does $5M+ ARR needs one. Use this template:

markdown
# Commercial Policy Charter

## Purpose
This Commercial Policy defines the rules that govern commercial terms
offered to customers. It is binding on all customer-facing functions
(Sales, Customer Success, Partner / Channel) and is enforced by Deal Desk.

## Scope
Applies to:
- All new customer agreements
- All renewals (with material change)
- All partner-mediated deals
- All custom / non-standard agreements

Does not apply to:
- Self-serve / PLG transactions per standard published terms
- Auto-renewals at standard terms

## Owners and Approvers
- Policy owner: CRO + CFO + General Counsel (jointly)
- Operational enforcement: Deal Desk
- Updates: quarterly review by policy owners
- Material changes: board awareness

## Pricing Policy

### Standard pricing
- All new customers offered at published list pricing
- Published price is canonical; deviations require approval per matrix

### Discount approval matrix
[Per the deal-desk approval matrix — see business-growth/deal-desk]

### Maximum allowed discount
- Standard maximum: 50%
- Beyond 50%: CEO + Board awareness required
- Discount > 60%: only with explicit strategic-rationale documented and CEO sign-off

### Most Favored Nation (MFN)
- Not granted by default
- Granted only with: strategic-tier customer + CRO + CFO + GC approval
- Always scoped narrowly: same product, same volume, same term length, same geography
- Disclosure-only (never automatic price-match)

### Rebates
- Performance-based rebates allowed per partner-program tier
- Customer-tier rebates: discouraged; if granted, time-bounded and explicit

## Contract Policy

### Standard term
- 12-month contract with annual prepay
- Auto-renew unless 90-day notice

### Term flexibility
- < 12 months: requires Director approval
- 24-36 months: Director approval
- > 36 months: VP Sales approval
- Multi-year discounts: per discount matrix

### Payment terms
- Standard: Net 30, annual prepay
- Net 45-60: Director approval
- Net 90+: CFO approval
- Custom milestone-based: CFO approval; revenue recognition impact reviewed

### Renewal
- Standard: auto-renew, same terms, same price (or per published renewal pricing)
- Renewal expansion > 20%: deal-desk review
- Renewal contraction > 10%: deal-desk review + customer success consultation

### Termination
- Standard: termination for convenience requires 90-day notice
- Termination for cause: 30-day cure period
- Customer-requested termination flexibility: Director approval
- Mid-term termination rights: VP Sales approval

## Legal Policy

### MSA modifications
- Pre-approved modifications: tracked list in approved-modifications appendix
- Custom modifications: General Counsel approval required
- Customer-supplied MSA: full GC review; default to push back to our MSA

### Liability cap
- Standard: 1x annual fees
- 2x annual fees: GC + CFO approval
- > 2x annual fees: CEO sign-off
- Carve-outs: IP infringement, gross negligence, willful misconduct — always uncapped

### Indemnification
- Standard mutual indemnification per template
- Customer-favorable indemnification: GC approval
- Defense / settlement control: vendor by default; customer-controlled needs CEO

### Jurisdiction and governing law
- Standard: vendor's jurisdiction
- Customer jurisdiction: GC approval
- Arbitration vs litigation: per template; deviations need GC

### IP
- Standard: each party retains pre-existing; joint inventions per default
- Customer-favorable IP terms: GC approval
- Source code escrow: only for OEM / strategic; never standard customer

## Operational Policy

### SLA tiers
- Standard published SLA (99.5%)
- Enhanced SLA (99.9%): per published pricing
- Custom SLA: Customer Success + Engineering approval; pricing premium per agreement
- Custom SLA with penalties: CRO + CCO + Engineering approval

### Security commitments
- Standard SOC 2 / ISO 27001 commitments per template
- Custom security: CISO + GC approval
- Customer audit rights: GC approval (limited to annual, with notice, third-party auditor)

### Dedicated infrastructure
- Not standard; available only with CTO + GC approval
- Premium pricing required

## Customer Commitments

### Reference / case study requests
- Standard: requested but not required
- Discounted deals (> 15%): case study or reference required as condition
- Strategic logos: explicit case study + press release commitment

## Channel Policy

### Partner-mediated deals
- Per Partner Agreement; discount per tier
- Deal registration governs conflict
- Direct rep authority same as direct deals on partner-led opportunities

## Special Terms

### Performance-based payment
- Payment-on-acceptance / acceptance criteria: CFO + GC approval
- Milestone payments: CFO approval

### Ramp deals
- ≤ 3 months: Sales Manager
- 3-12 months: Director
- > 12 months: VP Sales

### Source code escrow (for customer)
- Not standard; available only with CTO + GC approval

## Documentation Requirements

Every non-standard deal documented per Deal Desk packet template:
- Deviation explicitly listed
- Justification documented
- Approver identified
- Customer commitments (if any) explicit
- Expiration / conditions clear

## Annual Review

This policy is reviewed annually by CRO + CFO + GC.
Material changes communicated to sales with training.

## Effective Date
<date>
## Last Updated
<date>
## Approved By
- CRO: <signature>
- CFO: <signature>
- GC: <signature>
- Board (acknowledgement): <date>

See references/commercial-policy-charter.md for the full annotated charter with notes on each section's typical contentious issues.


Discount and terms policy details

See references/discount-and-terms-policy.md for deeper guidance on:

  • Discount-percentage policy by ACV bracket
  • MFN clause design (when to allow, how to scope)
  • Performance-based rebate structures
  • Multi-year discount mechanics
  • Payment-term flexibility and revenue-recognition implications
  • Renewal pricing policy (escalators, holds, contraction)

Contract and commercial guardrails

See references/contract-and-commercial-guardrails.md for deeper guidance on:

  • Acceptable MSA modifications (a list-based, not case-by-case approach)
  • Liability cap negotiation
  • Termination rights design
  • IP and joint-development clauses
  • Customer audit rights
  • Cross-jurisdictional terms (EU vs US vs APAC)

Clarify First

Before generating the policy, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Company stage + ARR scale — drives whether a full charter is warranted and how tight thresholds should be
  • Approver structure — who owns the policy and sits in the chain (CRO/CFO/GC, VP Sales, Director) (populates Owners/Approvers and every approval line)
  • Region / jurisdiction — US / EU / APAC (changes payment norms, governing law, and triggers a regional overlay)
  • Max discount + liability risk appetite — the discount ceiling and liability-cap tolerance (drives the Pricing and Legal policy sections)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the policy.

End-to-end workflows

Workflow: Author commercial policy from scratch
  1. Assemble policy committee — CRO + CFO + GC sponsors + Deal Desk Lead + Sales Operations
  2. Inventory current deals — what terms have been offered? What's been ad-hoc?
  3. Identify policy gaps — areas where ad-hoc behavior is hurting (concession drift, customer surprises)
  4. Draft charter using template; one section per domain
  5. Internal review — Sales VP, Eng VP, CISO, Customer Success VP, Finance for revenue recognition
  6. Pilot with sales managers for 30 days — collect feedback
  7. Final approval — CRO + CFO + GC sign-off; board awareness
  8. Sales training — workshop + recorded session + quick-reference cards
  9. Publish to sales wiki / partner portal / customer-facing communications team
  10. Quarterly review thereafter
Show full SKILL.md (452 more words)Show less
Workflow: Refresh existing policy (annual)
  1. Pull deal data for past 12 months: discount distribution, terms deviations, approvals
  2. Identify drift — what's the deviation rate by policy category?
  3. Survey sales managers — what's working / what's blocking
  4. Survey customers — what terms have been requested but declined?
  5. Identify market shifts — competitive landscape, customer expectations
  6. Draft amendments — specific policy changes with rationale
  7. Approve with CRO + CFO + GC
  8. Communicate changes to sales with training
  9. Update charter + effective date
Workflow: Audit deal compliance
  1. Export deals from CRM for the period
  2. Run compliance checker — scripts/policy_compliance_checker.py --deals deals.csv --policy policy.yaml
  3. Review non-compliant deals — investigate each: was the deviation approved? was it documented?
  4. Categorize:
    • Compliant with approved deviation: OK
    • Non-compliant unapproved: investigate; corrective action
    • Compliant but suggests policy gap: amend policy
  5. Report to policy committee; track corrective actions
Workflow: Generate region-specific policy
  1. Identify region-specific requirements — currency, jurisdiction, payment norms, regulatory
  2. Run scripts/commercial_policy_generator.py --base policy.yaml --region <region> to get base + regional overlay
  3. Tailor further with local team (regional VP Sales, regional GC, regional CFO)
  4. Approve through standard governance
  5. Communicate to regional sales

Anti-patterns

  • Policy without enforcement. Written policy + ad-hoc execution = policy is theater.
  • Policy that's never updated. Markets shift; competitive landscape changes; policy goes stale.
  • Policy with no compliance audit. Without measurement, you can't tell if policy is followed.
  • Policy too restrictive. When sales bypasses constantly, the policy is wrong; tighten or loosen.
  • Policy too lax. When everyone "complies" but margin still erodes, policy doesn't constrain enough.
  • Policy authored without sales input. Reps see it as imposed; comply minimally.
  • Policy with no training. Reps don't know what they can offer; default to over-asking deal desk.
  • Policy that's a contract appendix. Buried in legal docs; never read.
  • Same policy across regions when market conditions differ substantially.
  • Policy reviewed only after a customer complaint. Reactive only.

Tooling outputs

ScriptInputOutput
scripts/policy_compliance_checker.pyDeal CSV + policy YAMLPer-deal: compliant / non-compliant with policy violation listing; aggregate compliance metrics
scripts/terms_deviation_analyzer.pyDeal CSVDeviation patterns: which terms most often deviate? from which standard? by what magnitude?
scripts/commercial_policy_generator.pyBase policy YAML + optional region overlayGenerated policy document (markdown), tailored to company stage, ICP, region

All scripts: stdlib only, argparse CLI, JSON or markdown output.


References


  • business-growth/deal-desk — operational enforcement of policy
  • business-growth/pricing-strategy — sets prices that policy governs deviations from
  • business-growth/contract-and-proposal-writer — drafts contracts respecting policy
  • business-growth/channel-economics — channel deals subject to policy (with overlay for partners)
  • business-growth/partnerships-architect — partnership terms subject to commercial-policy oversight
  • c-level-advisor/cs-cro-advisor — CRO is co-owner of policy
  • c-level-advisor/cs-cfo-advisor — CFO is co-owner of policy
  • ra-qm-team/soc2-compliance-expert — policy compliance is audit-relevant evidence

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in business-growth/commercial-policy of borghei/Claude-Skills.

  • SKILL.md
  • references/commercial-policy-charter.md
  • references/contract-and-commercial-guardrails.md
  • references/discount-and-terms-policy.md
  • scripts/commercial_policy_generator.py
  • scripts/policy_compliance_checker.py
  • scripts/terms_deviation_analyzer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Commercial Policy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commercial Policy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commercial Policy this skillborghei/Claude-Skills891—~3.9kAutomated safety check: PassMIT
Geo Fundamentalswasp-lang/wasp19k9 repos~861Automated safety check: PassMIT
Ab Testingcoreyhaines31/marketingskills54k3 repos~3.1kAutomated safety check: PassMIT
Hreflang and International SEOAgriciDaniel/claude-seo19k5 repos~3.4kAutomated safety check: PassMIT
Referralscoreyhaines31/marketingskills54k2 repos~2.6kAutomated safety check: PassMIT
SEO GeoReScienceLab/opc-skills1.8k4 repos~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Geo Fundamentals

    wasp-lang/wasp

    Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

    19k GitHub starsUsed in 9 repos~861 tokens
    Marketing & SEOAuto-check passed
  • Ab Testing

    coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    54k GitHub starsUsed in 3 repos~3.1k tokens
    Marketing & SEOAuto-check passed
  • Hreflang and International SEO

    AgriciDaniel/claude-seo

    Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.

    19k GitHub starsUsed in 5 repos~3.4k tokens
    Marketing & SEOAuto-check passed
  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.6k tokens
    Marketing & SEOAuto-check passed
  • SEO Geo

    ReScienceLab/opc-skills

    SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub starsUsed in 4 repos~2.1k tokens
    Marketing & SEOAuto-check passed
  • Ad Creative

    LeoYeAI/openclaw-marketing-skills

    When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.

    1k GitHub starsUsed in 8 repos~3.4k tokens
    Marketing & SEOAuto-check passed

More from borghei/Claude-Skills

All 354 skills in this repo
  • Agent Harness

    borghei/Claude-Skills

    Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.

    891 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    891 GitHub stars~4.2k tokensUpdated 2 days ago
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    891 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    891 GitHub stars~3.6k tokensUpdated 2 days ago
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    891 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    891 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Commercial Policy

What does Commercial Policy do?

Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Commercial Policy is an agent skill from borghei/Claude-Skills. Commercial policy: the governance framework defining what terms sales can offer and what triggers approval.

When should I use Commercial Policy?

Commercial Policy fits situations like: authoring a policy charter; defining discount/payment/liability rules; generating a regional policy.

How do I install Commercial Policy in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill commercial-policy -a claude-code`. Or copy the skill folder (business-growth/commercial-policy in borghei/Claude-Skills) into .claude/skills/commercial-policy in your project. Claude Code loads it when a task matches its description.

How do I install Commercial Policy in Codex?

Run `npx skills add borghei/Claude-Skills --skill commercial-policy -a codex`. Or copy the skill folder (business-growth/commercial-policy in borghei/Claude-Skills) into .agents/skills/commercial-policy in your project. Codex loads it when a task matches its description.

Can I use Commercial Policy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill commercial-policy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commercial-policy, .gemini/skills/commercial-policy, .github/skills/commercial-policy and .opencode/skills/commercial-policy in your project.

What does Commercial Policy need to run?

Going by SKILL.md and its folder, Commercial Policy needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Commercial Policy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Commercial Policy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Commercial Policy use?

Commercial Policy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commercial Policy use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.8k tokens, read only when the agent opens those files.

What are the alternatives to Commercial Policy?

Skills that share tags, products or a category with Commercial Policy: Geo Fundamentals (wasp-lang/wasp, 19k stars), Ab Testing (coreyhaines31/marketingskills, 54k stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 19k stars) and Referrals (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commercial Policy?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.