CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-distribution

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.

Quality

85%

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

71%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 editorial-discipline skill: excellent progressive disclosure with a real, well-organized bundle, concrete cadence numbers and audience maps, and a walkable 12-consideration framework. The main weakness is redundancy — repeated framing between opening and closing, and duplicated reference pointers — which inflates token cost without adding guidance.

Suggestions

Remove the consolidated 'Reference files' section (or the per-section 'Detail in...' lines) — the same 9 pointers appear twice; keeping one form saves ~10 lines of duplication.

State the 90/10 production-distribution ratio and the hope-and-pray/spam-everywhere/channel-fit triad once (either the framing section or the closing, not both), and have the closing reference the framing instead of restating it.

Add a short worked example (one piece -> audience, channels, format-fit decisions, cadence) to make the 12-consideration framework concretely executable end-to-end.

DimensionReasoningScore

Conciseness

Mostly efficient prose, but with noticeable tightening available: the 90/10 production-distribution ratio and the hope-and-pray/spam-everywhere/channel-fit framing each appear twice (opening and closing sections), each of the 9 in-section 'Detail in references/...' pointers is duplicated by a full 'Reference files' section, and 'The voice is the senior editorial leader...' is rhetorical padding. This is several unnecessary repetitions rather than minor trimmings, so below anchor 4.

3 / 5

Actionability

Concrete, specific guidance for an instruction-only skill: named cadence numbers ('Newsletter weekly. Blog 2-4 posts per week. LinkedIn 3-5 posts per week'), specific channels per audience type (B2B technical, executive, developer), a 4-question litmus test, and symptom-to-diagnosis failure modes. Minor gap: no worked example walking a single piece through the framework, which keeps it short of fully covering the common cases.

4 / 5

Workflow Clarity

The 12-consideration framework is a walkable ordered checklist, and the litmus test plus audience/cadcence/measurement audits act as checkpoints; the failure-mode section provides diagnostic flow. No explicit validate-fix-retry feedback loops, so not anchor 5; checkpoints are present and no destructive/batch-operation cap applies, so above anchor 3.

4 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references: every section ends with a 'Detail in references/X.md' pointer, all 9 referenced files exist on disk, and the consolidated Reference files section gives accurate one-line descriptions. Content is appropriately split between the overview and the bundle, making navigation easy.

5 / 5

Total

16

/

20

Passed

Description

95%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 description: comprehensive channel taxonomy with concrete examples, explicit and varied trigger coverage including symptom-based triggers, and clear what/when structure in third-person voice. The only refinement available is converting some topical noun phrases into action verbs for even sharper specificity.

DimensionReasoningScore

Specificity

Lists several specific capabilities with concrete parenthetical examples across owned (newsletter, blog, social), earned (PR, syndication, mentions), and paid (boosted posts, syndication networks) channels, plus matching and cadence activities. Not a 5 because coverage is expressed as topical nouns rather than the concrete action verbs of the anchor-5 example; well above the 1-2-action coverage of anchor 3.

4 / 5

Completeness

Explicitly answers both what ('Owned channels... earned channels... paid channels... audience-channel matching, content-channel matching, distribution cadence') and when ('Triggers on... Also triggers when...') with concrete trigger phrases, matching the anchor-5 structure exactly. Third-person voice throughout, so no voice penalty.

5 / 5

Trigger Term Quality

'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' gives comprehensive natural-term coverage with synonyms, and adds symptom phrasings users would actually say ('content is publishing but reach is low').

5 / 5

Distinctiveness Conflict Risk

Clear niche — channel work distinguished from adjacent content-suite skills (repurposing, strategy, SEO) — with specific, domain-scoped triggers and minimal overlap risk. Phrases like 'content promotion' and 'content amplification' have slight adjacency to other marketing skills but the channel-fit framing keeps the boundary clear.

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.

Validation — 15 / 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

rampstackco/claude-skills

Path

skills/content-distribution/SKILL.md

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.