CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

public-relations

When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 strategy skill: the body stays a lean overview with excellent progressive disclosure into four real, substantive reference files, and concrete checklists make the guidance actionable. The main gaps are mild redundancy in the reference pointers, a few directional passages, and the absence of follow-up/error-recovery loops in the workflows.

Suggestions

Consolidate the reference pointers: The PR Mix and Common Workflows sections both link the same three files — let the workflows section carry the links and keep The PR Mix to one-line descriptions (helps conciseness).

Add a brief follow-up protocol to journalist-pitching workflows (e.g., one polite bump after N days, then close the loop), since real pitching workflows fail on the no-reply path (helps workflow_clarity).

Make the 'What's worth pitching this week?' workflow concrete by summarizing or linking the newsworthiness scoring rubric from references/newsjacking.md in the body (helps actionability).

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no 'what is PR' priming) and delivers opinionated, non-obvious guidance, but the Common Workflows section repeats reference pointers already given in The PR Mix ('newsjacking.md,' 'journalist-pitching.md,' 'press-platforms.md' each linked twice), and editorial asides like 'Most companies do this in an afternoon and forget about it for a year — that's fine' could be trimmed. Efficient with minor over-explanation, fitting anchor 4 rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable specifics abound: the quality bar sets hard thresholds ('Is the pitch under 150 words?', 'Check their last 5 articles,' banned-word list), the press-page section is a copy-ready checklist, and workflows name steps and files. A few spots stay directional ('Combine: recent product milestones + active news cycles + any data you've collected') without a concrete scoring procedure in the body, so anchor 4 rather than 5.

4 / 5

Workflow Clarity

Workflows are sequenced with named steps ('Go to newsjacking.md, run the scoring rubric, draft 2–3 angles, pick the best, draft the pitch') and the quality-bar checklist acts as an explicit pre-send validation gate ('If any answer is no, don't send'). However, there are no follow-up/iteration loops (e.g., what to do when a pitch gets no reply) and some workflows are looser than others, leaving minor validation gaps at anchor 4 rather than anchor 5's feedback loops.

4 / 5

Progressive Disclosure

The ~125-line body is a genuine overview — philosophy, mode-selection table, owned-mode checklist, quality bar, measurement — with four clearly signaled, purpose-labeled one-level-deep references (newsjacking, journalist-pitching, press-platforms, media-outlets), all verified to exist and contain substantive content (188–368 lines each). Content is appropriately split and navigation is easy, matching anchor 5.

5 / 5

Total

17

/

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.

An exemplary description: explicit what-and-when with an extensive set of natural trigger phrases, careful PR-vs-pull-request disambiguation, and explicit routing to sibling skills. The only weakness is that the owned-mode work (press page / media kit) covered in the body is absent from the capability list.

DimensionReasoningScore

Specificity

The description lists four concrete actions ('finding journalists, pitching stories, newsjacking, and responding to press requests'), but the owned mode (press page / media kit) that the skill body covers is not mentioned, leaving a minor coverage gap. It exceeds anchor 3 (only 1-2 actions) but falls short of anchor 5's comprehensive coverage.

4 / 5

Completeness

Both 'what' ('help with public relations, earned media, press coverage, journalist outreach, or media strategy' plus 'finding journalists, pitching stories, newsjacking, and responding to press requests') and 'when' ('When the user wants help with...' and 'Also use when the user mentions...') are explicitly stated with concrete trigger phrases, matching the anchor 5 example.

5 / 5

Trigger Term Quality

Roughly 26 natural trigger phrases including synonyms ('newsjacking' / 'news hijack'), platform names ('HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter'), brand names ('TechCrunch,' 'tech press'), and colloquial user phrasings ('how do I get press,' 'get featured'). Comprehensive coverage of natural terms including synonyms, matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

It carves a clear earned-media niche, explicitly disambiguates the 'PR' abbreviation ('not pull requests'), and routes adjacent intents to other skills (directory-submissions, launch, social, cold-email). Clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

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

joshmanders/dotfiles

Path

claude/skills/public-relations/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.