channel-economics

Use when reviewing or rebalancing direct vs. partner-led channel economics — computing fully-loaded cost-to-serve per channel, channel ROI with cash / LTV / marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection (e.g., 'which channel actually makes money — direct or partner?').

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

86%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.

A well-structured, highly actionable skill body with a clear sequenced workflow and excellent progressive disclosure via real one-level references. The main opportunity is tightening the inlined forcing-question library and removing the 'Do not use for'/'Distinct from' overlap to improve conciseness.

Suggestions

Move the forcing-question library (questions 1–7 with canon citations) into a dedicated reference file and keep only a one-line pointer in SKILL.md to reduce body length and improve conciseness.

Merge the 'Do not use for' and 'Distinct from' sections — they overlap heavily — into a single consolidated boundary section.

Add an explicit validate-then-proceed checkpoint between workflow steps (e.g., 'confirm cost-to-serve report flagged no double-counting before running the ROI analyzer') to strengthen workflow_clarity toward a 5.

Dimension	Reasoning	Score
Conciseness	Content is mostly specialized domain knowledge (anti-patterns, canon citations, ratios like 'MDF < 5:1') rather than basics Claude already knows, but the ~157-line body carries an elaborate inlined forcing-question library and overlap between 'Do not use for' and 'Distinct from' that could be trimmed.	4 / 5
Actionability	Fully executable guidance: concrete commands with real flags ('scripts/cost_to_serve_calculator.py --input channel.json --output markdown', '--profile {saas,api,enterprise-software,marketplace,hardware}', '--sample'), a copy-paste quick example, and expected outputs per step covering the common cases.	5 / 5
Workflow Clarity	A clear 5-step sequence (Intake → cost-to-serve → ROI → mix → Decide) with described data handoffs and built-in script validation (overhead-consistency check, double-counting flags), but it lacks explicit validate→fix→retry feedback loops in the narrative; the non-destructive analytical nature means the batch/destructive cap-at-3 does not apply.	4 / 5
Progressive Disclosure	The body is an overview pointing to one-level-deep, clearly signaled references that all exist — 3 reference canons, 3 scripts, and the channel_data_template — with easy navigation, matching the clear-overview anchor.	5 / 5
	Total	18 / 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.

A strong, specific description that answers what and when with concrete outputs and natural trigger terms for its commercial audience. Its only weakness is verbosity — it is long and somewhat editorialized ('nobody actually knows which channel makes money'), though verbosity is not a penalized dimension here.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'computing fully-loaded cost-to-serve per channel, channel ROI with cash / LTV / marginal lenses, and optimal channel mix' plus outputs 'cost to serve, channel ROI verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection' — giving comprehensive coverage with no gaps.	5 / 5
Completeness	Explicitly answers both: what (compute cost-to-serve, 3-lens ROI, optimal mix; emit verdicts, mix recommendation, inflection) and when ('Use when reviewing or rebalancing…' plus the 'For Head of Commercial, RevOps, and VP Sales doing quarterly channel review…' trigger), matching the anchor that requires concrete trigger phrases.	5 / 5
Trigger Term Quality	Uses natural phrases a Head of Commercial / RevOps would actually say — 'quarterly channel review', 'channel economics', 'cost-to-serve', 'channel ROI', 'direct vs. partner-led', 'which channel actually makes money' — with synonyms, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear narrow niche — direct-vs-partner channel economics — with distinctive triggers, so conflict with adjacent skills is minimal; matches the 'clear niche with distinct triggers' anchor.	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: commercial/skills/channel-economics/SKILL.md
Commit: 19392f7

Reviewed: ~3 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.