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.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, self-contained PR skill: concrete templates and checklists, a clearly sequenced launch timeline, and tight token-efficient organization with no conceptual padding. The only minor tension is that several sizable template blocks could optionally be split into reference files, but they are tightly integrated core instruction and the skill reads coherently as one overview.

DimensionReasoningScore

Conciseness

Lean throughout — tables, checklists, and fill-in templates carry the load with no padding or explanation of concepts Claude already knows (e.g. no 'what is a press release'); every section earns its tokens, matching the score-3 'every token earns its place' anchor.

3 / 3

Actionability

Provides copy-ready artifacts: a full press-release structure, a cold-pitch email template with an 8-word subject example, a press-kit checklist, and a Product Hunt table pinned to '12:01am PST' — fully executable guidance, not pseudocode.

3 / 3

Workflow Clarity

Sequenced T-14 through T+3 timeline in the PR Plan output, explicit rules ('Follow up once after 5 business days — then move on'), a self-test checkpoint ('Test your angle'), and checklists; not a destructive/batch operation so the validate-loop cap does not apply, placing it above the score-2 'checkpoints missing' anchor.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent), so scored against the actual empty bundle: the single SKILL.md is well-organized into clearly-headed sections with tables and signals Related Skills one level deep, avoiding the score-2 'content that should be separate is inline' monolith.

3 / 3

Total

12

/

12

Passed

Description

100%

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 model description: third-person voice, specific enumerated capabilities, an explicit 'Use when...' trigger clause with abundant natural keywords, and clear disambiguation from neighboring skills. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit' — matching the score-3 anchor of several specific concrete actions rather than the score-2 single-domain phrasing.

3 / 3

Completeness

Explicitly answers both what (the enumerated actions) and when via 'Use when the user mentions...' with explicit triggers, matching the score-3 anchor; not the score-2 case where 'when' is only implied.

3 / 3

Trigger Term Quality

Covers natural user phrasing broadly: 'press', 'PR', 'media coverage', 'TechCrunch', 'journalist', 'press release', 'app press kit', 'get featured in media', 'editorial coverage', 'review from a blogger', 'app launch announcement' — well above the score-2 'some relevant keywords' bar.

3 / 3

Distinctiveness Conflict Risk

Clear app-press/PR niche with distinct triggers, plus explicit disambiguation ('For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.') making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

12

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.

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