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,' 'press,' 'press release,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'reporter request,' 'tech press,' 'TechCrunch,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'podcast guest,' 'prep me for this podcast,' 'how do I get press,' 'PR crisis,' 'crisis communications,' 'respond to backlash,' 'we got hacked,' 'data breach statement,' or 'holding statement.' Also covers crisis response when something goes wrong. 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.

72

Quality

90%

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

86%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 overview skill: opinionated domain guidance, hard quality gates, and clean routing to a complete set of one-level-deep reference files, all of which exist. The main improvement opportunities are consolidating the duplicated reference routing between 'The PR Mix' and 'Common Workflows' and making the fix-and-recheck loop after the pitch quality bar explicit.

Suggestions

Consolidate the duplicated reference pointers: 'The PR Mix' and 'Common Workflows' both route to newsjacking.md, journalist-pitching.md, story-angles.md, press-platforms.md, and podcast-guest-prep.md — either merge the routing into one section or make the PR Mix table link directly and drop the repeated 'For the X — see Y' lines.

Close the feedback loop on the pitch quality bar: after 'If any answer is no, don't send', add the recovery step (e.g., 'Revise the pitch against the failed check and re-run the full checklist before sending') so validation cycles back instead of just halting.

Tighten the first-60-minutes crisis checklist in the body into a numbered sequence (or point to the exact checklist section in crisis-communications.md) so the 'When Something Goes Wrong' workflow reads as an ordered runbook rather than a prose summary.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it teaches PR strategy judgments ('AVE ... is a vanity metric PR firms invented', 'Speed beats polish on reactive PR') rather than generic concepts, and uses tables and checklists instead of prose. However, 'The PR Mix' section and 'Common Workflows' section both route to the same five reference files (newsjacking.md, journalist-pitching.md, story-angles.md, press-platforms.md, podcast-guest-prep.md are each cited twice), a minor redundancy that could be consolidated. This sits between anchors 4 and 5, closer to 4: efficient with minor trimmable instances, not 'every token earns its place.'

4 / 5

Actionability

Guidance is directly executable for an instruction-only skill: the 7-item pitch quality bar with hard thresholds ('Is the pitch under 150 words?', 'Check their last 5 articles.', banned-word list, 'If any answer is no, don't send'), the 9-item press page checklist, the HARO rule ('keep it under 200 words'), the 24-hour response commitment, and the measurement table. Specific procedures cover the common cases for each workflow, matching anchor 5; there are no gaps that force guessing.

5 / 5

Workflow Clarity

Each workflow is clearly sequenced ('run the scoring rubric, draft 2–3 angles, pick the best, draft the pitch'; crisis: 'assign a severity tier, then run the first-60-minutes checklist: confirm facts, designate one spokesperson, publish a holding statement, set the next update time') and includes validation checkpoints ('If any answer is no, don't send', 'loop in legal counsel before admitting fault or publishing'). However, the error-recovery half of the loop is implicit — the quality bar says don't send but never says revise-and-recheck — which keeps it at anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5 ('feedback loops for error recovery').

4 / 5

Progressive Disclosure

The body is a genuine overview: all 8 bundle files in references/ are cited with a one-line purpose ('For the reactive newsjacking workflow — see references/newsjacking.md'), every cited path exists on disk, and links are one level deep with only lateral sibling cross-links (e.g., crisis-communications.md ↔ statement-templates.md), which aid navigation rather than bury content. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; easy navigation').

5 / 5

Total

18

/

20

Passed

Description

90%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, trigger-rich description that explicitly covers both what the skill does and when to use it, with excellent disambiguation against 'pull request' confusion and neighboring skills. The only weakness is that the capability statement stays at domain level rather than naming the concrete deliverables it produces.

DimensionReasoningScore

Specificity

The description states 'help with public relations, earned media, press coverage, journalist outreach, or media strategy' and 'Also covers crisis response' — domain-level scope with a couple of concrete activity areas, but it never states concrete actions (e.g., draft pitches, build media lists, write holding statements). This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is below anchor 4 because the verbs remain generic ('help with', 'covers') and specific deliverables appear only as user trigger phrases, not stated capabilities.

3 / 5

Completeness

Both questions are explicitly answered: what ('help with public relations, earned media, press coverage, journalist outreach, or media strategy' plus 'crisis response') and when ('When the user wants help with...' and 'Also use when the user mentions' followed by a long list of concrete trigger phrases). This matches anchor 5 ('clearly and explicitly answers both what AND when with concrete trigger phrases'); the 'when' clause could not be more explicit, ruling out anchor 4.

5 / 5

Trigger Term Quality

The trigger list is exhaustive and natural: 'PR,' 'press,' 'press release,' 'pitch a journalist,' 'get featured,' 'media kit,' 'newsjacking,' 'HARO,' 'Qwoted,' 'TechCrunch,' 'prep me for this podcast,' 'how do I get press,' 'we got hacked,' 'data breach statement' — covering synonyms, platform names, and phrases users would actually say. This clearly matches anchor 5 ('comprehensive coverage of natural terms including synonyms'); no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

It proactively disambiguates the highest-risk collision — 'PR' ... '(not pull requests)' — and routes adjacent intents to sibling skills ('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.'). This is a clear niche with distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

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

coreyhaines31/marketingskills

Path

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.