CtrlK
BlogDocsLog inGet started
Tessl Logo

public-relations

When the user wants to plan PR, write a press release, or manage media relations. Also use when the user mentions "public relations," "PR," "press release," "media relations," "news release," "journalist," "media coverage," "product announcement," or "earned media." For on-site "As Seen In" or logos page, use press-coverage-page-generator.

67

Quality

80%

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

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 lean, well-structured instruction skill with concrete numeric specs and clear output format. Its weakest spots are the absence of a worked example to model press release output against and an implicit (rather than explicit) end-to-end workflow from assessment to draft.

Suggestions

Add one short worked example (a sample headline + lead paragraph) so the output format is modeled, not just specified.

Make the workflow explicit by numbering the end-to-end flow (assess context → choose angle/audience/timing → draft per structure table → deliver in output format).

Trim the "When invoking" paragraph and the ~3% statistic; they add tokens without changing what Claude does.

DimensionReasoningScore

Conciseness

The body is efficient — a compact structure table, short bullet lists, and no concept explanations Claude already knows. Minor trimmable instances remain: the "When invoking" meta paragraph, the "Journalists use ~3% of releases" factoid, and the opening line that restates the description. These are minor enough to sit above the 3 anchor but short of "every token earns its place."

4 / 5

Actionability

Concrete, executable specs throughout: "Under 100 chars; strong action verbs," "50–75 words; all 5 W's (Who, What, When, Where, Why)," "2–3 sentence company description," and an explicit Output Format checklist. For a writing skill the guidance is specific, but there is no worked example (sample headline/lead) to model output against, leaving it just short of fully executable.

4 / 5

Workflow Clarity

A discernible sequence exists — Initial Assessment (news angle, audience, timing) → Press Release Structure → Writing Style → Output Format — and the task is non-destructive so no validation loop is required. However, the sequence is implicit across sections rather than explicitly ordered, and no step ties assessment answers to structural choices. Clearer than the 3 anchor's unconnected steps, short of the 5 anchor's explicit sequencing.

4 / 5

Progressive Disclosure

This is a ~58-line single-file skill with no bundle files, and none are needed — the content fits comfortably in SKILL.md. Sections are well-organized with headers and a table, and the Related Skills section provides outward navigation. Under the simple-skill guideline, well-organized sections with no need for external references score 5.

5 / 5

Total

17

/

20

Passed

Description

82%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 with excellent trigger-term coverage and explicit boundary delegation. Its main weakness is that the capability statement (what the skill does) is implied by when-clauses rather than stated directly, and "PR" carries minor pull-request ambiguity.

Suggestions

Add a direct capability statement before the when-clause, e.g., "Guides PR strategy and writes press releases. Use when..." so the "what" is explicit rather than implied.

Disambiguate the abbreviation collision by scoping it, e.g., "PR (public relations), not pull requests," for contexts where both meanings are live.

Mention the additional capabilities the body covers (embargo handling, media relations cadence, launch-timing coordination) to close the coverage gap.

DimensionReasoningScore

Specificity

"plan PR, write a press release, or manage media relations" lists several concrete actions with specific parameters (e.g., media relations management), but coverage is incomplete — no mention of pitch emails, media lists, or embargo handling that the body actually covers. It exceeds the 1-2 actions of a 3 but lacks the comprehensiveness of a 5.

4 / 5

Completeness

The "when" is explicit and strong ("When the user wants to plan PR... Also use when the user mentions..."), but the "what" is only implied through the when-clause phrasing rather than a standalone capability statement. Both are present and useful, but the what could be more explicit, fitting the 4 anchor.

4 / 5

Trigger Term Quality

The description includes comprehensive natural trigger terms with synonyms: "public relations," "PR," "press release," "media relations," "news release," "journalist," "media coverage," "product announcement," and "earned media." No common natural phrasing a user would say is missing, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The PR/press-release niche is clear and it explicitly delegates boundary cases ("For on-site 'As Seen In' or logos page, use press-coverage-page-generator"), but the bare abbreviation "PR" has real collision risk with pull-request usage in development contexts, keeping it just short of the minimal-conflict anchor.

4 / 5

Total

17

/

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