CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

press-media-relations

Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline. Not for press-kit assets — use launch-asset-packager; not for follow-up sequence mechanics — use outreach-manager; not for post-launch news-echo monitoring — use launch-monitor. 媒体名单/禁运期pitch/新闻稿/分析师简报

Quality

81%

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

67%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, sequenced, and genuinely actionable instruction skill with strong guardrails (registry authority, no-fabrication red lines, explicit handoffs). Its main costs are repetition of the registry-submission and handoff boilerplate and the absence of worked output examples.

Suggestions

State the 'authorized operation: propose request to registry-events.py' mechanics once (e.g., in the Skill Contract) and refer back to it elsewhere, cutting roughly six repeated phrases.

Consolidate the outreach-manager handoff, which currently appears in the Scope guard, Skill Contract, step 7, and Next Best Skill sections, into a single statement.

Add one worked mini-example — a filled-in Tier-1 contact entry with its angle, or a two-line release skeleton with dateline and lede — so the common case is copy-adaptable rather than reconstructed from the structural spec.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and gives a tight Quick Start, but is noticeably redundant: "via an authorized `operation: propose` request to `registry-events.py`" appears six times, and the outreach-manager handoff plus scope exclusions are restated in four places (Scope guard, Skill Contract, step 7, Next Best Skill). This fits 'mostly efficient but could be tightened' rather than the 4 anchor's 'minor instances'.

3 / 5

Actionability

Guidance is largely executable for an instruction-only skill: a concrete cadence ("T-14 exclusive feeler → T-10 round one → T-7 round two → T-0 lift → T+3 follow-up"), a release formula ("[Product] helps you X" headline, dateline, 2–5 sentence lede), tier sizing rules, and exact memory paths. It stops short of the 5 anchor because no filled-in example artifacts (a sample tier-list entry or a completed release skeleton) are shown; it is well above the 3 anchor's pseudocode-level guidance.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with real checkpoints: "No registry record = flag it as an open loop and route to launch-registry before committing any date to an outsider", claim tracing to the ledger with [needs source], and a Done-when checklist. Missing the explicit validate→fix→retry feedback loops of the 5 anchor, but far exceeds the 3 anchor's implicit checkpoints.

4 / 5

Progressive Disclosure

Sections are well organized and the Reference Materials section lists eight references, each with a one-line description and a stated reason to open it — clearly signaled and one level deep. It is not a 5 because every reference points outside the skill directory (../../../ paths) with no bundled reference/scripts/assets, and shared contract prose is inlined rather than split out; it is clearly above the 3 anchor's buried references.

4 / 5

Total

15

/

20

Passed

Description

92%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: concrete outputs, natural quoted trigger phrases, and explicit negative routing to sibling skills. The only weakness is synonym coverage of trigger terms (e.g., "PR", "public relations", "media outreach").

DimensionReasoningScore

Specificity

The description enumerates the skill's full output set concretely — "produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline" — matching the comprehensive-coverage anchor. It is not a 4 because there are no minor gaps: every major deliverable is named with its structure.

5 / 5

Completeness

Both halves are explicit: an "Use when the user asks to…" clause with concrete trigger phrases, and a precise statement of what the skill produces. This matches the 5 anchor exactly; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Three natural quoted trigger phrases ("build a media list for my launch", "write a launch press release", "pitch press under embargo") are exactly what a user would say, giving good keyword coverage. It falls short of the 5 anchor's comprehensive synonym coverage — common variants like "PR", "public relations", "media outreach", or "press coverage" are absent — but is well above the 3 anchor's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (launch media/analyst motion) and actively disambiguates with "Not for press-kit assets — use launch-asset-packager; not for follow-up sequence mechanics — use outreach-manager; not for post-launch news-echo monitoring — use launch-monitor". Minimal conflict risk; clearly the 5 anchor rather than the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 27 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

launch/mobilize/press-media-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.