Token导航 LogoToken导航

Agent Skill · 待分类

media-relations(媒体关系)

media-relations 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

media-relations 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 4,459。

总安装 737周安装 31GitHub Stars 3下载 258核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:media-relations(媒体关系)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/media-relations
安装命令:
npx skills add https://github.com/oldwinter/skills --skill media-relations
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill media-relations

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

media-relations 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态或协作事项进行整理。适用于需要可视化项目结构、流程或变更场景的 Agent 宿主环境。

通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/media-relations

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill media-relations;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

media-relations 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill media-relations。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

media-relations 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

media-relations 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

media-relations 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

media-relations 用的人多吗?

公开数据是累计安装 737 次,近一周安装 31 次,下载 258 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

media-relations 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
media-relations

媒体关系 · 本页

7373只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Media Relations

Scope

Covers

  • Turning an announcement into a newsworthy angle (“what’s new” + “why now” + proof)
  • Building a targeted media list (outlets + reporters + freelancers) with tiers and pitch angles
  • Designing an exclusive/embargo strategy (staggered outreach, clear offer, fallback plan)
  • Preparing a lightweight pitch kit (email templates, press materials checklist, media FAQ)
  • Running an outreach + follow-up cadence with a tracker
  • Managing interview scheduling + spokesperson prep and post-coverage follow-up

When to use

  • “Build a media list and pitch journalists for our launch/announcement.”
  • “We want to offer an exclusive (or embargo). Help us plan and execute outreach.”
  • “Write press pitch emails and a follow-up cadence.”
  • “Prep our spokesperson for a reporter interview and create a media FAQ.”

When NOT to use

  • You’re handling crisis comms, reputational incidents, or legal emergencies (use a crisis-comms workflow with legal/PR lead).
  • You don’t have a real “news peg” yet (first do positioning/messaging or an announcement brief).
  • You want guaranteed coverage, placements, or paid distribution (this is earned media; outcomes aren’t guaranteed).
  • You need regulated claims review (medical/legal/financial) and can’t provide an approval path.

Inputs

Minimum required

  • What’s happening: announcement type + what’s new (2–5 bullets)
  • Timing: desired publish window, embargo constraints (if any)
  • Audience: who you want to reach and where they get information
  • Proof: metrics, customer examples, demo links, screenshots, credible specifics (or placeholders)
  • Spokesperson: who can talk + availability constraints
  • Guardrails: what cannot be shared publicly; any legal/compliance requirements

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md (3–5 at a time), then proceed.
  • If proof is missing, use placeholders and output an “evidence to collect” list (do not invent facts).
  • If you can’t share sensitive details, accept redacted versions and write pitches at a higher level.

Outputs (deliverables)

Produce a Media Relations Pack (Markdown in-chat; or as files if requested) in this order:

  1. Context snapshot (what, who, timing, constraints, success definition)
  2. Newsworthiness brief (“what’s new”, “why now”, angle options, proof/evidence)
  3. Media list + tiering (targets, beats, rationale, pitch angle per target)
  4. Exclusive/embargo plan (sequencing, offer, timeline, fallback)
  5. Pitch kit (email templates + subject lines + follow-up cadence)
  6. Press materials checklist + drafts outline (press release/blog PR alternative, media FAQ, bio, assets)
  7. Outreach tracker spec (table + statuses + next actions)
  8. Interview prep (talking points, do/don’t, sensitive topics, bridging)
  9. Risks / Open questions / Next steps (always included)

Templates and checklists:

Workflow (8 steps)

1) Intake + success definition

  • Inputs: User prompt; references/INTAKE.md.
  • Actions: Confirm the announcement, primary audience, desired window, and what success means (e.g., “2–4 tier-1/2 hits” or “reach X niche audience”). Capture constraints and approvals.
  • Outputs: Context snapshot + assumptions/TBDs list.
  • Checks: You can answer in one sentence: “The goal of this outreach is _____ by _____.”

2) Create the newsworthiness brief (prep)

  • Inputs: What’s new, why now, proof, audience.
  • Actions: Draft 2–3 angles. Define the “new information” and the credible specifics you can share. Decide if an exclusive or embargo is appropriate.
  • Outputs: Newsworthiness brief + angle shortlist.
  • Checks: Each angle has (a) a clear “new” claim, (b) a why-now reason, (c) at least one proof point (or “to validate”).

3) Build the target list (who to pitch)

  • Inputs: Angle shortlist; target geos; competitor/adjacent coverage examples (if any).
  • Actions: Create a tiered media list: Tier 1 (dream), Tier 2 (likely), Tier 3 (long tail). Map each target to a beat and a specific hook.
  • Outputs: Media list table (tiered) + selection rationale.
  • Checks: Every target has a personalized hook; no “spray and pray” list of generic outlets.

4) Design exclusive/embargo + sequencing (stagger it)

  • Inputs: Tier 1–2 list; timeline; spokesperson availability; approval constraints.
  • Actions: If using an exclusive, pick 1–3 best-fit targets and define: what they get, when they get it, and how you’ll follow up. Plan staggered outreach and a fallback path if the exclusive fails.
  • Outputs: Exclusive/embargo plan (timeline + decision points).
  • Checks: The exclusive offer is explicit; the fallback path is defined; timing is realistic for reporter cycles.

5) Prepare the pitch kit + press materials

  • Inputs: Newsworthiness brief + target list.
  • Actions: Draft subject lines and pitch emails (exclusive + standard). Create a media FAQ and a press materials checklist; outline a press release or announcement blog post and assemble links/assets.
  • Outputs: Pitch kit + materials outline/checklist.
  • Checks: Pitch is short, specific, and reporter-centric (no hype); every “big claim” has proof or a placeholder.

6) Execute outreach + track responses

  • Inputs: Pitch kit; outreach tracker template.
  • Actions: Send outreach in waves (exclusive first if applicable). Track status, schedule follow-ups, and capture relationship notes. Handle declines gracefully and ask for the right redirect (“who covers this?”).
  • Outputs: Populated outreach tracker + next-action list.
  • Checks: Follow-up cadence is respectful; tracking is up to date; no duplicate/conflicting pitches.

7) Manage interviews + follow through

  • Inputs: Interested replies; spokesperson; media FAQ; constraints.
  • Actions: Schedule interviews, prep the spokesperson, and provide supporting assets. After the interview, send a concise follow-up with links and clarifications. If factual errors occur, request corrections politely and precisely.
  • Outputs: Interview prep doc + follow-up note templates.
  • Checks: Spokesperson is aligned on 3 key messages; sensitive topics have safe responses; logistics are confirmed.

8) Post-coverage: amplify + maintain relationships + quality gate

  • Inputs: Coverage links; tracker; references/CHECKLISTS.md and references/RUBRIC.md.
  • Actions: Log coverage, send thank-yous, amplify appropriately, and update relationship notes. Score the pack with the rubric and include Risks/Open questions/Next steps.
  • Outputs: Final Media Relations Pack + post-mortem notes (what worked/what to change).
  • Checks: You can re-run the outreach loop next time using the tracker and templates with minimal rework.

Quality gate (required)

Examples

Example 1 (Launch): “Use media-relations. We’re launching for on. Goal: 10 high-quality mentions in niche publications. We can offer 1 exclusive. Provide a Media Relations Pack with a media list, exclusive plan, pitch emails, and an outreach tracker.” Expected: tiered media list + exclusive timeline, pitch templates, tracker table, and interview prep.

Example 2 (Funding/announcement): “Use media-relations to plan press outreach for our Series A announcement. Audience: founders and operators. Constraints: no revenue numbers. Create angles, target reporters, and a pitch kit.” Expected: angle options that work without sensitive metrics, media list with hooks, and templates for embargo outreach.

Boundary example: “Blast 500 journalists and guarantee TechCrunch will cover us.” Response: refuse guarantee/spray-and-pray; propose a targeted list + staggered outreach + realistic success metrics.

平台分布

Codex

35.89%
按下载量换算93

Claude

31.15%
按下载量换算80

Cursor

19.3%
按下载量换算50

Gemini CLI

9.79%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills