Name: commercial-skills
Rating: 68 (1 reviews)
Author: alirezarezvani

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 execution) and c-level-advisor/cro-advisor (strategic CRO judgment).

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is commercial-skills in alirezarezvani/claude-skills

Quality

Content

65%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 well-structured and largely actionable with a clear deterministic routing workflow, but it is somewhat verbose through repeated routing discipline and its progressive disclosure is undermined by references to a `references/` directory that contains no actual files.

Suggestions

Consolidate the routing discipline so it appears once; the symptom table, signal table, and anti-patterns overlap and could be trimmed to reduce token cost (lowest-scoring conciseness).

Create real files under `references/` for the cited canon (Tunguz, Skok, Bessemer, Monetizing Innovation) or convert the inline name-drops into concrete links so progressive disclosure is grounded.

Add an explicit validation/verify checkpoint in Step 5 (e.g., confirm sub-skill returned the expected artifact files and citations) to lift workflow_clarity to a 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the body pads several sections with explanatory prose, repetition between the symptom table, signal table, forcing-question library, and anti-patterns that restates the same routing discipline multiple times.	3 / 5
Actionability	Provides concrete routing tables, a forcing-question template with worked examples, and per-lane recommended answers with canon citations; minor gaps are that several sub-skill invocations are described abstractly rather than as executable commands.	4 / 5
Workflow Clarity	The five-step workflow is clearly sequenced with explicit 'route silently', forcing-question, decision-tree walk, fork, and digest stages, plus confirmation gates before chaining; missing an explicit validation/verify step on returned digests, so it stops short of a 5.	4 / 5
Progressive Disclosure	Structure is sectioned and references a `references/` canon and a path-B build doc, but no bundle files actually exist in the workspace and the canonical citations (Tunguz, Skok, etc.) are name-dropped inline rather than linked to real, one-level-deep files.	3 / 5
	Total	14 / 20 Passed

Description

100%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 a strong, comprehensive trigger-and-capability statement: it names concrete actions, lists natural user triggers, clarifies both what and when, and explicitly distinguishes the skill from adjacent ones. It is dense but not padded with fluff.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — reviewing, approving, designing pricing models, deal review, discount approval, partnership economics, channel mix, commercial policy, RFP/RFI response, bookings forecast — plus seven named sub-skills, a fork-and-digest behavior, and explicit distinctions from sibling skills.	5 / 5
Completeness	Explicitly answers both 'what' (per-deal economics and packaging orchestration that forks context, routes to seven sub-skills, returns a digest) and 'when' (a 'Use when...' clause enumerating concrete trigger scenarios).	5 / 5
Trigger Term Quality	Includes natural user phrasings as explicit triggers ('review this deal', 'should we discount', 'pricing model', 'partner economics', 'RFP response', 'bookings forecast', 'channel mix') with broad synonym coverage across the commercial domain.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (per-deal commercial economics) and explicitly differentiates from business-growth, c-level-advisor/cro-advisor, reducing wrong-skill triggering risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/commercial-skills/SKILL.md
Commit: 19392f7

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

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.