CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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, actionable editorial playbook with clear progressive disclosure to 9 real reference files and a sequenced 12-consideration framework. Its one weakness is conciseness: the keystone framing and the 90/10 ratio are repeated across the intro, body, and closing, adding length that could be trimmed.

Suggestions

Consolidate the repeated spam-everywhere / hope-and-pray / 90-10 production-vs-distribution framing: state it once in the keystone section and have later sections reference it rather than re-deriving it, to tighten the body toward a 3 on conciseness.

The 'Closing: distribution is half the work' section restates the opening's 90/10 argument and the channel-fit summary; consider trimming it to a brief callback or folding it into the framework summary.

A few taxonomy entries appear both inline and in the reference summaries (e.g., channel sub-types, failure modes); ensure inline lists are short enough to motivate the reference rather than duplicating it.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but at ~307 lines it restates the spam-everywhere / hope-and-pray framing and the 90/10 production-distribution ratio multiple times (intro, taxonomy, closing), and the closing largely rehashes the opening. It could be tightened without losing clarity, so it sits at the 2-anchor rather than 3.

2 / 3

Actionability

Provides concrete, specific guidance: named channel sub-types, common audience-channel maps per audience type, cadence patterns with explicit frequencies ('Newsletter weekly. Blog 2-4 posts per week'), and a 12-consideration framework. As an instruction-only skill, the absence of executable code is not penalized, and the guidance is actionable and copy-ready.

3 / 3

Workflow Clarity

The '12 considerations for content distribution' section is a clearly sequenced audit/design checklist, complemented by the litmus test ('which audience is this piece for...'), per-section 'mismatch failure' diagnostics, and a dedicated failure-modes section. This matches the 3-anchor for a clear sequenced process with checkpoints; no destructive/batch operation requires validation gates here.

3 / 3

Progressive Disclosure

SKILL.md is an overview that summarizes each topic inline and signals one-level-deep references via 'Detail in [`references/...`]', with a consolidated 'Reference files' section listing all 9 bundles with descriptions. All referenced files exist in ./references/, references are exactly one level deep, and navigation is easy.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, complete, and clearly distinctive from sibling content-suite skills. It names concrete channels and actions, gives explicit 'triggers on' guidance, and carves out a non-overlapping niche. No significant weaknesses; verbosity is the only minor note.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and channels: 'Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks)' plus 'Audience-channel matching, content-channel matching, distribution cadence.' Matches the 3-anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Content distribution as a discipline... channel-fit decisions') and when ('Triggers on content distribution...', 'Also triggers when content is publishing but reach is low...'). Matches the 3-anchor requiring explicit 'Use when' trigger guidance.

3 / 3

Trigger Term Quality

Includes natural terms users would say: 'content distribution', 'content amplification', 'content promotion', 'syndication strategy', 'organic distribution', 'owned earned paid channels'. Good coverage of common variations; not jargon-only.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche and explicitly distinguishes from sibling skills (content-repurposing, paid-media-strategy, email-sequences, seo-aeo-geo) and gives distinct triggers, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 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
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.