CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

podcast-marketing

When the user wants to plan, create, or market a podcast. Also use when the user mentions "podcast," "podcast strategy," "podcast SEO," "show notes," "podcast distribution," "Spotify podcast," "Apple Podcasts," "podcast discoverability," "PodcastEpisode schema," or "podcast repurposing." For show notes, use article-content.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/content/podcast/SKILL.md
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.

A well-organized, token-efficient overview that avoids padding and covers strategy, distribution, SEO, cross-promotion, and repurposing in compact tables. It is weakest on actionability and workflow clarity: the guidance stays at the guideline level for its central SEO/discoverability challenge (no examples or templates) and never sequences the assessment into an explicit procedure.

Suggestions

Add one worked example each for the core SEO outputs — a sample optimized episode title (≤60 chars), a sample episode description with natural keyword placement, and a short show-notes template — to make the central guidance concrete rather than parameter-only.

Tighten vague guideline rows ('engaging language', 'Sticky, unique, valuable content') into specific instructions, e.g., 'front-load the primary keyword in the first 60 characters' or 'place the CTA after the main content, before the outro.'

Make the workflow explicit by connecting the Initial Assessment to action: e.g., 'If stage = launching, produce the Launch checklist; if stage = growing, prioritize Cross-Promotion and Repurposing sections' — turning the reference structure into a sequenced procedure.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no padding or explanation of concepts Claude already knows; statistics like '3M+ active shows, 500M+ listeners' and the discovery-channel percentages are decision-relevant context rather than filler. The single motivating sentence 'Search engines cannot listen to audio' earns its place by justifying the SEO section, matching anchor 5 'every token earns its place.'

5 / 5

Actionability

There are real specifics ("≤60 chars", "PodcastEpisode and PodcastSeries", "TikTok, YouTube Shorts, X", channel-share percentages, a defined Output Format), but the skill's central claimed challenge — discoverability/SEO — provides parameters with no examples or templates (no sample optimized title, description, or show-notes structure), and several guideline rows are vague ('engaging language', 'Sticky, unique, valuable content'). This matches anchor 3 'some concrete guidance but incomplete; missing key details' rather than anchor 4, where gaps would be minor.

3 / 5

Workflow Clarity

An implicit flow exists (Initial Assessment of stage/format/niche/goals → topic sections → Output Format), but the body reads as a topical reference rather than a sequenced procedure; nothing explicitly ties assessment findings to which sections or outputs to apply. Anchor 3 ('sequence present but checkpoints missing or implicit') fits; it is not 4 because the assessment-to-output sequence is never made explicit.

3 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ are absent) and none are needed: the ~80-line body is compact, well-sectioned with clear headers, and self-contained — nothing clearly warrants splitting into separate files. Per the rubric's simple-skill guidance, well-organized sections with no external-reference needs match the top anchor's 'easy navigation' and 'content appropriately split.'

5 / 5

Total

16

/

20

Passed

Description

72%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 trigger-rich, well-bounded description with excellent keyword coverage and explicit conflict resolution for show notes. Its main weakness is the missing explicit capability statement — the 'what' is only implied by the when-clause, and the named actions (plan, create, market) are generic categories rather than concrete capabilities.

Suggestions

Add an explicit third-person capability sentence before the trigger clause, e.g., 'Guides podcast strategy, content creation, distribution, and SEO' — this would raise both specificity and completeness by stating the 'what' directly.

Replace or supplement the generic verbs 'plan, create, or market' with more concrete capabilities such as 'define listener personas, build launch checklists, optimize show notes and titles for search, and plan cross-platform repurposing.'

Consider adding one or two additional natural triggers users say, such as 'launch a podcast' or 'grow podcast downloads,' to broaden recall without sacrificing distinctiveness.

DimensionReasoningScore

Specificity

Names the domain and actions ("plan, create, or market a podcast") but all three are broad category verbs rather than concrete operations, matching anchor 3 ('names domain and 1-2 concrete actions, not comprehensive'). It falls short of anchor 4 because it lacks several specific concrete actions like 'extracts text, fills forms, converts pages' in the PDF example.

3 / 5

Completeness

The 'when' is explicit and rich, but the description opens with a when-clause ("When the user wants to plan, create, or market a podcast") and never states a explicit capability sentence — the 'what' is only implied through the trigger phrasing. Per the guideline to score only what is explicitly stated, it does not reach anchor 4 (both what and when); it sits above anchor 2 because the when-clause does enumerate the supported activities, landing at anchor 3's 'weakly implied' territory for the missing half.

3 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms, platform names, and a schema name: "podcast," "podcast strategy," "podcast SEO," "show notes," "podcast distribution," "Spotify podcast," "Apple Podcasts," "podcast discoverability," "PodcastEpisode schema," "podcast repurposing." These are exactly the phrases a user would naturally say, matching the anchor 5 'comprehensive coverage of natural terms.'

5 / 5

Distinctiveness Conflict Risk

Clear podcast niche with distinct platform- and task-specific triggers, and it explicitly resolves the one obvious overlap ("For show notes, use article-content"), matching anchor 5 'clear niche with distinct triggers; minimal conflict risk.'

5 / 5

Total

16

/

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

Path

skills/content/podcast/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.