Content distribution as a discipline. Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks), and the channel-fit decisions that distinguish strategic distribution from spam-everywhere. Audience-channel matching, content-channel matching, distribution cadence. Triggers on content distribution, channel strategy for content, owned earned paid channels, content amplification, content promotion, audience-channel matching, content-channel matching, distribution cadence, syndication strategy, organic distribution. Also triggers when content is publishing but reach is low, when the team is distributing on every channel without strategy, or when the content program needs a distribution discipline rather than just publication.
50
55%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/content-distribution/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and clear 'when to use' guidance including both keyword triggers and situational triggers. Its main weakness is that it reads more like a topic overview than a list of concrete actions Claude will perform—it describes the domain rather than specifying what Claude does within it. Adding explicit action verbs (e.g., 'builds distribution plans', 'audits channel-content fit') would strengthen specificity.
Suggestions
Replace conceptual descriptions with concrete action verbs: instead of 'Content distribution as a discipline', say 'Builds content distribution plans, audits channel-content fit, recommends distribution cadence and channel prioritization.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (content distribution) and lists categories of channels (owned, earned, paid) with examples, plus concepts like audience-channel matching and distribution cadence. However, it describes conceptual areas rather than concrete actions Claude would perform (e.g., 'create a distribution plan', 'audit channel performance'). The actions are implied but not explicitly stated. | 2 / 3 |
Completeness | The description answers both 'what' (content distribution discipline across owned/earned/paid channels, audience-channel matching, distribution cadence) and 'when' with explicit trigger terms and situational triggers ('when content is publishing but reach is low', 'when the team is distributing on every channel without strategy'). The 'Triggers on' and 'Also triggers when' clauses serve as clear 'Use when' equivalents. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'content distribution', 'channel strategy', 'content amplification', 'content promotion', 'syndication strategy', 'organic distribution', and situational triggers like 'reach is low' and 'distributing on every channel without strategy'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around content distribution strategy specifically, distinguishing itself from general content creation, social media management, or marketing strategy skills. The emphasis on 'distribution discipline' and channel-fit decisions makes it unlikely to conflict with adjacent skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as an essay or textbook chapter on content distribution rather than an actionable skill for Claude. It is extremely verbose, repeating key themes multiple times and explaining basic concepts Claude already knows. Despite its length (~3000+ words), it lacks any concrete deliverables—no templates, no decision trees, no example distribution plans, no specific output formats. The referenced bundle files don't exist, and the inline content largely duplicates what those files should contain.
Suggestions
Cut the body content by 60-70%: remove explanations of basic concepts (what a newsletter is, what PR is), eliminate repeated framings (hope-and-pray vs spam-everywhere appears 3+ times), and move detailed channel descriptions entirely to reference files.
Add concrete, actionable artifacts: a distribution plan template with specific fields to fill, a channel-fit decision matrix, an example distribution plan for a sample content piece, or a scoring rubric for evaluating channel fit.
Replace the abstract '12 considerations' with a concrete workflow: e.g., 'Step 1: List target audience segments → Step 2: For each segment, identify top 3 channels using [decision criteria] → Step 3: Map content formats to channels using [format-channel matrix] → Step 4: Draft cadence plan using [template]' with validation checkpoints.
Create the referenced bundle files and move detailed content (channel taxonomy, audience maps, cadence patterns, failure modes) into them, keeping only a concise summary and decision-relevant guidance in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~3000+ words. Extensively explains concepts Claude already understands (what owned/earned/paid channels are, what newsletters are, what PR is). Massive redundancy: the hope-and-pray vs spam-everywhere framing is repeated multiple times, the distinction from content-repurposing is stated three times, and the 'distribution is half the work' theme appears in the intro, closing, and throughout. The channel taxonomy section explains basic concepts like 'blog is where pieces persist' and 'newsletter is direct subscriber relationship' that add no value for Claude. | 1 / 3 |
Actionability | Despite its length, the skill provides no concrete, executable guidance. There are no templates, no specific commands, no example outputs, no checklists with actionable steps. The '12 considerations' framework is a list of abstract principles, not actionable steps. The cadence patterns give rough frequency ranges but no actual distribution plan template or decision tree. Everything describes rather than instructs—Claude is told what good distribution looks like but not given concrete tools to produce distribution plans. | 1 / 3 |
Workflow Clarity | The 12-consideration framework provides a reasonable sequence for auditing or designing a distribution program, and the common failure modes section offers diagnostic patterns. However, there are no validation checkpoints, no explicit decision gates, and no feedback loops. The audit steps in audience-channel matching are listed but lack concrete validation criteria for determining if matching is correct. | 2 / 3 |
Progressive Disclosure | The skill references 9 separate reference files with clear descriptions, which is good structure. However, no bundle files are provided, so these references are dead links. More critically, the main SKILL.md contains enormous amounts of content that should be in those reference files—the channel taxonomy, audience-channel matching details, cadence patterns, and failure modes are all extensively covered inline AND referenced to separate files, creating redundancy rather than true progressive disclosure. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
8e70d03
Table of Contents
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.