CtrlK
BlogDocsLog inGet started
Tessl Logo

commercial-policy

Use when designing or revising a company's commercial policy — the rules of engagement governing discounts off list price, approver thresholds, exception flows, and the deal framework that Deal Desk and AEs operate under. Covers discount matrix design (ARR band x term length x payment terms x strategic value), commercial policy design, exception policy, discount governance, approval thresholds, deal framework structure, and policy linting (contradictions, gaps, cliff edges, gaming surfaces). For Head of Commercial, Head of Deal Desk, VP Sales, or RevOps at the policy-design moment — NOT per-deal application (that is deal-desk) and NOT pricing model selection (that is pricing-strategist).

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable commands, a clearly sequenced and validated workflow, and well-structured one-level-deep references to real bundle files. The only lever for improvement is trimming the forcing-question library, which is the densest non-executable section.

DimensionReasoningScore

Conciseness

The body is mostly lean and concrete — script invocations with flags, lint-rule IDs, anti-pattern mappings, and a scripts table all earn their tokens — but the 8-question forcing-question library with per-question recommended answers and canon citations adds length that could be trimmed without losing actionability.

4 / 5

Actionability

Provides copy-paste-ready commands in the Quick examples block and concrete per-step invocations ('scripts/discount_matrix_builder.py --input policy_intake.json --profile {saas|...}') with a scripts table and flag reference, covering the common cases fully.

5 / 5

Workflow Clarity

The 5-step workflow (Audit → Design matrix → Design exception flow → Lint → Publish + quarterly review) is clearly sequenced with an explicit validation gate ('Resolve every BLOCKER before publishing') and a quarterly re-run feedback loop, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

SKILL.md reads as an overview that signals one-level-deep bundle files — three scripts, three reference canons, and one asset template — all of which exist on disk, each described in the References section for easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific, well-triggered, and cleanly disambiguated from sibling skills, with explicit what/when guidance and concrete negative scope. The only minor gap is slightly heavier reliance on persona labels than on the full spread of natural synonyms a user might say.

DimensionReasoningScore

Specificity

Lists multiple concrete coverage areas — 'discount matrix design (ARR band x term length x payment terms x strategic value)', 'exception policy', 'discount governance', 'approval thresholds', 'deal framework structure', and 'policy linting (contradictions, gaps, cliff edges, gaming surfaces)' — giving comprehensive, specific coverage rather than vague abstraction.

5 / 5

Completeness

Opens with an explicit 'Use when designing or revising...' trigger and clearly states the 'what' (rules of engagement governing discounts off list), then reinforces scope with concrete negative triggers ('NOT per-deal application... NOT pricing model selection'), explicitly answering both what and when.

5 / 5

Trigger Term Quality

Strong natural domain terms ('commercial policy', 'discounts off list price', 'Deal Desk', 'approver thresholds', 'exception flows') plus persona triggers, but relies on role names ('Head of Commercial', 'VP Sales') more than the full range of natural user phrasings, leaving a few synonymous terms uncovered.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (discount-policy design) and explicitly disambiguates from adjacent skills ('that is deal-desk', 'that is pricing-strategist'), minimizing the chance of triggering for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.