CtrlK
BlogDocsLog inGet started
Tessl Logo

press-and-pr

When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.

74

Quality

91%

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

82%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 strong, highly actionable body: templates and tactical rules are copy-paste ready and the content assumes Claude's intelligence. Weaker spots are the distributed (rather than consolidated) workflow sequencing and the total inlining of templates in a 200-line file where reference splitting would improve progressive disclosure.

Suggestions

Consolidate the launch sequence into one explicit stepwise workflow near the top (press kit → press release → embargo/Tier-1 pitches → Tier-2 → launch day → follow-up), with the existing timeline as a summary, so the end-to-end order is not scattered across sections.

Move the full press-release template and press kit checklist into a references/ file (e.g., references/templates.md) and keep one-line pointers in SKILL.md to reduce inline length and improve progressive disclosure.

Trim the "Why Press Still Matters" bullets to a single line (or fold into the intro) since the motivational rationale is largely inferable.

DimensionReasoningScore

Conciseness

Dense, table-driven, and operational with minimal over-explanation; only minor trimmable material like the "Why Press Still Matters" rationale bullets and a few Tier-3 rows that restate inferable context, fitting the "efficient with minor instances of over-explanation" anchor.

4 / 5

Actionability

Provides copy-paste-ready artifacts throughout — press kit checklist, full press-release template, cold-pitch email with a 5-sentence rule, embargo mechanics, day-by-day Product Hunt table, and a fill-in PR plan output format — fully executable for an instruction-only skill.

5 / 5

Workflow Clarity

The T-14 → T+3 timeline, Product Hunt step table, and "follow up once after 5 business days" rule give a clear sequence, but the sequence is distributed across topical sections rather than one explicit end-to-end workflow, and no validation checkpoints are stated.

4 / 5

Progressive Disclosure

Well-sectioned single file with no external references; structure is good, but at ~200 lines the press-release and pitch-email templates are fully inlined where one or two would more naturally live in a references/ file (the under-50-line simple-skill exception does not apply).

4 / 5

Total

17

/

20

Passed

Description

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

The description is exemplary: it states four concrete capabilities, provides an explicit "Use when…" clause with eleven natural trigger phrases including synonyms, and proactively disambiguates against adjacent skills. It directly matches the rubric's good-overall examples.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "writing press releases, pitching journalists, getting on 'best apps' lists, or building an app press kit" — comprehensively covering the app-PR domain; voice is neutral third-person, so no penalty applies.

5 / 5

Completeness

Explicitly answers both "what" (the four concrete actions) and "when" via a literal "Use when the user mentions…" clause with concrete trigger phrases, matching the top anchor's example pattern.

5 / 5

Trigger Term Quality

Includes eleven natural quoted trigger phrases with synonym coverage ("press", "PR", "media coverage", "editorial coverage", "get featured in media", "review from a blogger", "TechCrunch"), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Clear app-press/PR niche with active conflict avoidance — "For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch." — routing adjacent intents to sibling skills.

5 / 5

Total

20

/

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
Eronred/aso-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.