Press & Media Relations
Build a launch-ready media and analyst motion with tiered targets, embargo timing, press copy, and briefing structure.
The skill shows least-privilege behavior through scoped writes, user confirmation before saving, authorized operation: propose requests, prohibition on direct registry edits, and treatment of pasted lists and fetched content as untrusted. It also forbids fabricated quotes and numbers. Eight points are deducted because handling of sensitive journalist/analyst relationship data is not specific, rollback or revocation of commitments is undefined, and handoff to outreach-manager may lead to external communications without a fully specified confirmation boundary.
The evidence shows clear triggers, inputs, outputs, done conditions, missing-registry handling, scope boundaries, and termination rules, with internally consistent instructions. Twelve points are deducted because this is a static review with no skill-specific tests or reproduced key paths; the workflow depends on shared registries, memory files, other skills, and optional connectors, while diagnostic behavior for unavailable dependencies is limited.
The evidence clearly identifies audiences, scenarios, argument hints, three output classes, non-fit areas, and boundaries with outreach-manager and launch-monitor, while declaring keyless paths. Five points are deducted because geo-relevance is marked low, Chinese support is limited to labels and summary text, mainland-China reachability and Chinese media-discovery quality are unverified, and triggering still depends on supplied launch context and supporting artifacts.
The evidence shows a consistent Skill Contract layout with Quick Start, read/write scope, completion criteria, handoff, data sources, procedure, save rules, references, and next-skill guidance; it also declares version 18.0.0, Apache-2.0 licensing, and compatibility. Five points are deducted because the skill lacks an FAQ, troubleshooting section, changelog, named maintenance responsibility, or explicit update path, and its installation guidance does not fully explain behavior when referenced files are unavailable.
The evidence defines directly usable outputs: a tiered media list, per-contact angles, embargo timing, press-release draft, analyst briefing, and handoff summary, with claims-ledger controls for factual statements. Nine points are deducted because static review cannot verify list quality, angle relevance, release completeness, or real PR outcomes; outputs also depend on user-provided relationships, verticals, message-house material, and claims records, while execution and monitoring are delegated to other skills.
The evidence provides internal traceability to the launch registry, claims ledger, event streams, shared protocols, connectors, and security guidance. Six points are deducted because there are no external sources, representative outputs, skill-specific tests, or third-party execution records; the internal references are auditable but do not independently validate conclusions or outcomes.
- Do not commit dates, invent product numbers, or release media materials when the launch registry, message house, or claims ledger is missing; flag an open loop or [needs source].
- Journalist and analyst lists, relationship states, and replies may contain personal or commercially sensitive data; confirm access scope, retention, and deletion or revocation procedures before saving or handing off.
- This skill plans and drafts but does not execute outreach or monitor results; Chinese-language media coverage and connector reachability should be validated separately for mainland-China use.
What does this skill do, and when should you use it?
Press & Media Relations is the Mobilize-phase media skill in Aaron Marketing Skills’ launch workflow. It builds a three-tier media and analyst plan around the authoritative launch date held by launch-registry. It also drafts an embargo pitch skeleton, a standard-structure press release, and an analyst briefing outline while enforcing claims traceability. It fits launch teams that need focused media activation without conflating press strategy with asset production, outreach execution, or post-launch monitoring.
Reads the launch tier and authoritative date or stage, the message house, the claims ledger, target verticals, and user-provided journalist or analyst relationships. It may use the brand-monitor GDELT connector for outlet discovery. It produces Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters, contact-specific angles, an Estimated embargo cadence, written embargo terms, a structured press release, an analyst briefing outline, and a handoff summary for outreach-manager. With authorization, it submits launch commitments and unsupported-claim events through registry-events.py.
- A product team needs a right-sized press and analyst list for a Tier 1 or Tier 2 launch.
- A PR lead is choosing between an exclusive feeler and a broader embargo sequence.
- A founder needs a factual launch press release without invented quotes or figures.
- A marketing team is preparing an analyst briefing covering category context, product position, roadmap themes, and evidence.
- A launch owner needs media commitments aligned to the authoritative date in launch-registry.
What are this skill's strengths and limitations?
- Clear scope covering media tiers, angles, embargo timing, press-release drafting, and analyst briefing structure.
- Explicit handoffs separate media planning from press-kit production, outreach execution, and post-launch monitoring.
- Claims discipline prohibits fabricated quotes or numbers and requires ledger support or [needs source].
- Tiered targeting and launch-size guidance discourage spray-and-pray pitching.
- Does not build the press kit or asset manifest; use launch-asset-packager.
- Does not execute multi-touch follow-up, negotiation, or pipeline mechanics; use outreach-manager.
- Does not monitor the post-launch news echo; use launch-monitor.
- The suggested pitch cadence is Estimated common PR practice, not a guaranteed media rule.
- The supplied source does not provide an independent test suite or detailed platform-validation results for this skill.
How do you install this skill?
Install the collection with git clone https://github.com/aaron-he-zhu/aaron-marketing-skills. In Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, followed by /plugin install aaron-marketing@aaron. The README does not document a dedicated single-skill installation command for this skill; the repository is described as compatible with Claude Code and compatible Agent Skills hosts.
How do you use this skill?
Example trigger: Build a media and analyst list for launching [product] in [vertical]. Launch tier: [T1/T2/T3]. Date: [from launch-registry]. You can also ask it to draft a launch press release or plan an embargoed pitch sequence. If no launch-registry record exists, it should flag an open loop and route the date decision to launch-registry before making an external commitment.
How does this skill compare with similar options?
Compared with launch-asset-packager, this skill owns media strategy, embargoes, angles, releases, and analyst briefings rather than press-kit assets. Compared with outreach-manager, it prepares the pitch package but does not own sending, follow-up, or negotiation. Compared with launch-monitor, it handles pre-launch media mobilization rather than post-launch coverage monitoring.