CtrlK
BlogDocsLog inGet started
Tessl Logo

distribution-channels

When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 body is a well-structured, concise reference of channel types, marketplace categories, listing-optimization practices, and platform-selection guidance with good cross-skill navigation. Its main limitation is workflow clarity: it presents a planning framework rather than an explicitly sequenced workflow with checkpoints.

Suggestions

Add an explicit short workflow (e.g., 1. identify product type, 2. shortlist matching marketplace categories, 3. draft listing per optimization practices, 4. verify against platform requirements) to lift workflow clarity above 3.

Trim the time-sensitive market-sizing stat ('$85B+... by 2028') or move it to a clearly labeled context note, since time-sensitive figures penalize conciseness unless isolated.

Consider tightening or relocating the meta 'When invoking' usage guidance so the body stays focused on substantive distribution content.

DimensionReasoningScore

Conciseness

Dense, table-driven body that assumes Claude's intelligence without over-explaining concepts; minor trimmable padding remains in the '$85B+ by 2028' market stat and the meta 'When invoking' guidance, keeping it just below the lean/efficient anchor at 5.

4 / 5

Actionability

Concrete, specific guidance throughout—named platforms per category and actionable practices ('Free trials, pay-as-you-go, private offers,' 'Optimize for marketplace search; clear descriptions, tags')—with only minor gaps, fitting the mostly-executable anchor adapted to an instruction skill.

4 / 5

Workflow Clarity

Organized as a reference framework with an implied sequence (channel types -> categories -> listing optimization -> platform selection) but no explicit workflow steps or validation checkpoints; no destructive/batch operations trigger the cap, so it sits at the steps-present-but-checkpoints-implicit anchor.

3 / 5

Progressive Disclosure

Self-contained ~60-line body with clear section headers and well-signaled one-level cross-skill navigation ('See pinterest-posts,' 'Related Skills'), with no content inlined that belongs in a separate file, matching the clear-overview anchor.

5 / 5

Total

16

/

20

Passed

Description

90%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 strong: it explicitly covers what and when, lists comprehensive natural trigger terms including platform names, and draws a clear boundary against a sibling skill. The only weak spot is specificity, which names a single action ('plan') rather than enumerating several concrete distribution actions.

DimensionReasoningScore

Specificity

Names the domain ('product distribution via marketplaces, app stores, or third-party platforms') with one concrete action ('plan'), but does not list several specific actions, matching the 1-2 concrete actions anchor rather than the multi-action anchor at 4.

3 / 5

Completeness

Explicitly answers both what ('plan product distribution via marketplaces, app stores, or third-party platforms') and when ('When the user wants to... Also use when the user mentions...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and specific platform names ('distribution channels,' 'marketplace listing,' 'Figma plugin,' 'AWS Marketplace,' 'Shopify app,' 'GPTs store,' 'third-party marketplace'), matching the comprehensive coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (third-party marketplaces/app stores) with distinct platform-specific triggers and an explicit boundary redirect ('For channel mix, use integrated-marketing'), giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
kostja94/marketing-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.