pr-calendar

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

PR Calendar

PR日历

A PR calendar is the planned half of PR.

newsjack-detector

watches news breaking right now; this skill looks at known upcoming moments and decides which ones this brand should plan around, when pitching should start, and what proof the brand needs before anyone contacts journalists.

The calendar feed is source-backed, but the value is still judgment. Do not dump a list of dates. Most moments should disappear because the brand has no standing, the hook is too generic, or the moment is unsafe to commercialize.

This is a MOLECULE. It reads the brand's monitor profile, queries the calendar API through the CLI, cuts the feed to real candidates, checks what kinds of stories landed around last year's version of those moments, and returns a readable plan. It does not write angles or pitches itself, and it persists nothing.

PR日历是公关工作的主动规划部分。

newsjack-detector

负责监测实时突发新闻；而本技能则着眼于已知的即将到来的节点，判断品牌应该围绕哪些节点做规划、何时开始对外推介，以及在联系记者前需要准备哪些证明材料。

日历源有可靠来源支撑，但核心价值仍在于判断。不要直接输出日期列表。大多数节点都应该被剔除，要么因为品牌缺乏参与资格，要么因为切入点过于通用，要么因为该节点不适合商业化。

这是一个MOLECULE组件。它会读取品牌的监测配置文件，通过CLI查询日历API，筛选出真正有价值的候选节点，查看这些节点去年同期的相关报道情况，最终返回一份易读的规划方案。它不会自行撰写推介角度或文案，也不会保存任何数据。

What this skill will not do

本技能不具备的功能

It will not promise a magical best day or best time to send a pitch. Use windows, not fake precision.
It will not list every observance. A weak or generic hook is not a media plan.
It will not invent dates. Every moment in Act this week, Six-month plan, Watch list, and Avoid must come from the calendar feed or from a date the user explicitly supplied. If an obvious anchor is missing from the feed, mention it only under Gaps & clusters as "missing from the feed; verify separately before planning."
It will not run the detector pipeline, coarse relevance filter, story-origin check, or freshness gate. This is a smaller context problem. One careful LLM pass over the calendar results is enough.

不会承诺发送推介文案的“最佳日期”或“最佳时间”。应使用时间窗口，而非虚假的精确时间。
不会列出所有纪念活动。薄弱或通用的切入点不能构成媒体计划。
不会凭空创造日期。本周行动、六个月规划、观察清单和规避清单中的每个节点都必须来自日历源或用户明确提供的日期。如果某个重要节点未出现在日历源中，仅需在空白期与密集期部分标注“未在日历源中找到；规划前请单独核实”。
不会运行检测器流程、粗略相关性筛选、报道来源核查或新鲜度校验。这是一个较小的上下文问题。仅需对日历结果进行一次严谨的大语言模型处理即可。

Inputs

输入信息

The brand profile. Reuse the existing monitor profile from
```
newsjack-setup
```
or fixture profile JSON. Read company description, topics, search terms, competitors, standing, spokespeople, proof assets, and market. Do not run a new questionnaire unless no profile exists.
The planning window. Default to the next six months from today. Long-lead opportunities can already be opening, so do not use a shorter default.
The calendar feed. Dated opportunities come from
```
newsjack pr-calendar query
```
, which wraps Medialyst's PR calendar API.

If no profile exists, ask only for the four things needed for judgment: what the brand does, what topics it can credibly speak to, what proof or data it can attach, and which market it pitches into.

品牌配置文件：复用
```
newsjack-setup
```
中的现有监测配置文件或固定配置文件JSON。读取公司描述、关注主题、搜索词、竞争对手、参与资格、发言人、证明材料和目标市场。除非没有配置文件，否则无需发起新的问卷调查。
规划时间窗口：默认从今日起未来六个月。由于长期筹备的机会可能已经开启，不要使用更短的默认时间范围。
日历源：带日期的机会来自
```
newsjack pr-calendar query
```
，该命令封装了Medialyst的PR日历API。

如果没有配置文件，仅需询问判断所需的四项信息：品牌业务内容、品牌可可信发言的主题、品牌可提供的证明或数据、品牌推介的目标市场。

Get The Calendar

获取日历数据

Newsjack reaches the PR calendar two ways. Try them in this order and stop at the first one that works:

CLI mode (preferred). Use
```
newsjack pr-calendar query
```
when the CLI is installed and authenticated.
MCP mode (fallback). If the
```
newsjack
```
CLI is not installed or not on PATH but the
```
medialyst
```
MCP server is connected, use the MCP PR calendar query tool. It mirrors
```
POST /api/v1/pr-calendar/query
```
, so the request fields and response shape are the same as the CLI — only the transport differs.

The PR calendar endpoint is free to use. It requires Medialyst login only to prevent abuse. If the live path is unauthenticated, connect Medialyst and retry; do not build a fallback calendar from memory.

Newsjack通过两种方式获取PR日历数据。按以下顺序尝试，成功后即停止：

CLI模式（首选）：当CLI已安装并完成认证时，使用
```
newsjack pr-calendar query
```
。
MCP模式（备选）：如果
```
newsjack
```
CLI未安装或不在PATH中，但已连接
```
medialyst
```
MCP服务器，则使用MCP PR日历查询工具。它镜像了
```
POST /api/v1/pr-calendar/query
```
接口，因此请求字段和响应格式与CLI完全一致——仅传输方式不同。

PR日历端点可免费使用。仅需Medialyst登录以防止滥用。如果实时路径未通过认证，请连接Medialyst并重试；不要从内存中构建备选日历。

CLI mode

CLI模式

Use the repo shim in a source checkout and the installed binary otherwise:

bash

bin/newsjack --version
newsjack --version

If the command is unauthenticated and you have shell access, run:

bash

newsjack login

Tell the user to open the printed Medialyst link and approve

newsjack CLI

, then retry the calendar query.

Then query one broad six-month window per profile:

bash

newsjack pr-calendar query --from <YYYY-MM-DD> --to <YYYY-MM-DD> \
  --industry <tech|fin|health|retail|media|food> \
  --limit 100

Use

--query

only when it helps without over-narrowing. Keep it short and broad, usually one or two words. For a developer-tools or AI-software profile,

--industry tech

is often better than packing the whole topic list into

--query

. Over-specific queries can hide useful conferences and seasonal hooks.

Do not use

--country-code

by default. Add it only when the user explicitly wants a local calendar, because many global events do not carry a country code.

For exact API-shaped requests, use:

bash

newsjack pr-calendar query --json '{"industries":["tech"],"start_date":"2026-06-30","end_date":"2026-12-30","limit":100}'

The response returns

calendar

metadata plus

opportunities

. Important opportunity fields include

title

type

industry

start_date

end_date

pitch_start_at

pitch_deadline_at

lead_time_summary

description

pitch_angles

audiences

coverage

source_urls

tags

, and

confidence

在源码检出环境中使用仓库封装脚本，否则使用已安装的二进制文件：

bash

bin/newsjack --version
newsjack --version

如果命令未通过认证且你拥有Shell访问权限，请运行：

bash

newsjack login

告知用户打开打印出的Medialyst链接并授权

newsjack CLI

，然后重试日历查询。

然后针对每个配置文件查询一个宽泛的六个月时间窗口：

bash

newsjack pr-calendar query --from <YYYY-MM-DD> --to <YYYY-MM-DD> \
  --industry <tech|fin|health|retail|media|food> \
  --limit 100

仅在有帮助且不会过度缩小范围时使用

--query

参数。保持简短宽泛，通常为一到两个词。对于开发工具或AI软件配置文件，

--industry tech

通常比将整个主题列表塞进

--query

更好。过于具体的查询可能会隐藏有用的会议和季节性切入点。

默认不要使用

--country-code

参数。仅当用户明确需要本地日历时才添加，因为许多全球活动没有国家代码。

如需发送精确的API格式请求，请使用：

bash

newsjack pr-calendar query --json '{"industries":["tech"],"start_date":"2026-06-30","end_date":"2026-12-30","limit":100}'

响应会返回

calendar

元数据以及

opportunities

。重要的机会字段包括

title

、

type

、

industry

、

start_date

、

end_date

、

pitch_start_at

、

pitch_deadline_at

、

lead_time_summary

、

description

、

pitch_angles

、

audiences

、

coverage

、

source_urls

、

tags

和

confidence

。

MCP mode

MCP模式

Use this path only when the

newsjack

CLI is unavailable and the

medialyst

MCP server is connected. The MCP tool takes the API request body directly. In most runtimes the tool is named

mcp__medialyst__query_pr_calendar

or similar; if the runtime exposes a different PR calendar tool name, use the one whose description maps to

POST /api/v1/pr-calendar/query

MCP request body:

json

{
  "industries": ["tech"],
  "start_date": "2026-06-30",
  "end_date": "2026-12-30",
  "limit": 100
}

Available request fields mirror the CLI/API:

industries

types

tags

audiences

country_codes

start_date

end_date

pitch_start_before

pitch_deadline_after

limit

, and

cursor

Use MCP results exactly like CLI results:

calendar

metadata plus

opportunities

. If neither CLI nor MCP is available, stop and tell the user to connect Medialyst; do not synthesize a calendar.

仅当

newsjack

CLI不可用且已连接

medialyst

MCP服务器时使用此方式。MCP工具直接接收API请求体。在大多数运行时中，该工具名为

mcp__medialyst__query_pr_calendar

或类似名称；如果运行时暴露的PR日历工具名称不同，请使用描述对应

POST /api/v1/pr-calendar/query

的工具。

MCP请求体：

json

{
  "industries": ["tech"],
  "start_date": "2026-06-30",
  "end_date": "2026-12-30",
  "limit": 100
}

可用请求字段与CLI/API一致：

、

industries

、

types

、

tags

、

audiences

、

country_codes

、

start_date

、

end_date

、

pitch_start_before

、

pitch_deadline_after

、

limit

和

cursor

。

MCP结果的使用方式与CLI结果完全相同：包含

calendar

元数据和

opportunities

。如果CLI和MCP都不可用，请停止操作并告知用户连接Medialyst；不要合成日历数据。

Candidate Review

候选节点审核

Review the returned opportunities once. Assign each opportunity to one of four buckets:

Bucket	Meaning	Output treatment
Pitch-ready	The brand has strong standing and can attach proof, data, a product fact, a customer, or a credible spokesperson.	Put in the plan.
Watch	Plausible but generic. It needs proprietary proof before pitching.	Include only if it helps the user plan, and say what proof would upgrade it.
Avoid	Sensitive, solemn, political, medical, memorial, or otherwise likely to read as opportunistic for this brand.	Put in Avoid with the reason.
Drop	No legitimate media angle for this brand.	Do not list individually unless the user asks for rejects.

Use these gates inside the one pass:

Brand standing. Ask: would a journalist naturally accept this brand as a source on this moment? A developer-tools company at a major developer or enterprise software conference can be strong. A fintech on World Savings Day is usually watch unless it has proprietary savings data. A B2B logistics SaaS on National Pizza Day is drop.

Proof. A pitch-ready moment needs something concrete: usage data, a benchmark, customer access, founder expertise, technical research, product news, or a clear spokesperson. If the profile has no proof, mark watch, not pitch-ready.

Brand safety. Avoid commercializing memorials, disasters, serious illness days, religious solemn observances, and charged political moments unless the brand has genuine standing and a respectful public-interest angle. Follow

skills/ETHICS.md

and

skills/WHY-NOT-SPAM.md

Timing. Use the API's

pitch_start_at

pitch_deadline_at

, and

lead_time_summary

first. Compare those dates with today:

Pitch now means today is between the pitch start and deadline.
Window opens
<date>
means the pitch start is still ahead.
Deadline passed means redirect to shorter-lead outlets or skip.
Event imminent means only reactive commentary, owned content, or very short-lead desks remain.

When useful, explain outlet timing as windows, not exact laws:

Outlet tier	Usual pitch window
Long-lead magazines and trades	3-6 months
National online publications	1-2 months
Weekly magazines	2 weeks-2 months
Daily print	1-2 weeks
Online, blogs, podcasts, regional	1-4 weeks
News desks	Up to the day

Drumbeat. After bucketing, scan the six-month shape once. Note quiet stretches that need evergreen stories and crowded weeks that should be staggered.

对返回的机会进行一次审核。将每个机会分配到以下四个类别之一：

类别	含义	输出处理方式
可立即推介	品牌具备较强参与资格，且可提供证明、数据、产品事实、客户案例或可信发言人。	纳入规划方案。
观察	看似可行但切入点通用。需要专属证明材料才能进行推介。	仅在有助于用户规划时纳入，并说明需要哪些证明材料才能升级为可推介节点。
规避	涉及敏感、严肃、政治、医疗、纪念等内容，对该品牌而言可能显得投机取巧。	纳入规避清单并说明原因。
剔除	对该品牌而言没有合理的媒体切入点。	除非用户要求列出被剔除的节点，否则不单独列出。

在单次审核中使用以下判断标准：

品牌参与资格：提问：记者是否会自然接受该品牌作为该节点的信息来源？例如，开发工具公司在大型开发者或企业软件会议上具备较强资格；金融科技公司在世界储蓄日通常属于观察类别，除非拥有专属储蓄数据；B2B物流SaaS在国家披萨日则应被剔除。

证明材料：可立即推介的节点需要具体内容：使用数据、基准测试、客户访问权限、创始人专业知识、技术研究、产品新闻或明确的发言人。如果配置文件中没有相关证明材料，标记为观察，而非可立即推介。

品牌安全性：避免将纪念活动、灾难、重大疾病日、宗教严肃仪式和敏感政治节点商业化，除非品牌具备真正的参与资格且有尊重公众利益的切入点。遵循

skills/ETHICS.md

和

skills/WHY-NOT-SPAM.md

。

时间安排：优先使用API提供的

pitch_start_at

、

pitch_deadline_at

和

lead_time_summary

。将这些日期与当前日期对比：

立即推介表示当前日期处于推介开始和截止日期之间。
**推介窗口开启于
```
<日期>
```
**表示推介开始日期尚未到来。
已过截止日期表示应转向筹备周期更短的媒体渠道或跳过该节点。
活动即将举行表示仅剩余反应式评论、自有内容或筹备周期极短的媒体渠道可选。

必要时，将媒体渠道的时间安排解释为时间窗口，而非精确规则：

媒体层级	常规推介窗口
长期期刊和行业刊物	3-6个月
全国性在线出版物	1-2个月
周刊	2周-2个月
日报印刷版	1-2周
在线媒体、博客、播客、区域性媒体	1-4周
新闻编辑部	活动当天之前

节奏：分类完成后，扫描六个月的时间范围一次。标注需要填充常青内容的空白期和需要错开安排的密集期。

Prior-Year Coverage

往年报道情况

After you have candidates, use

news-search

to research what actually earned coverage around last year's version of each pitch-ready and useful watch-list moment. This is inspiration and calibration, not a freshness gate.

Keep this bounded:

Research only candidates that survived the standing and safety review.
For a normal six-month calendar, search the top 8-12 candidates at most. If there are more, prioritize pitch-ready moments, open/closing pitch windows, and moments with the clearest brand standing.
Use 1-2 focused searches per candidate. Do not exhaustively research every possible article.

For each candidate, derive a prior-year search window:

Start with the candidate's
```
start_date
```
.
Move it back one year to approximate last year's comparable moment. If the feed or prior coverage clearly gives the exact previous occurrence date, use that instead.
Strip the year from event names when searching recurring events, then search from six months before that prior-year date through six months after it.

Use

news-search

newsjack news search

with

after:

and

before:

terms in the query. If the CLI is missing but Medialyst MCP is connected, call

mcp__medialyst__search_news

with the same query string.

bash

newsjack news search --query "\"<moment name without year>\" after:<prior-year-date-minus-6-months> before:<prior-year-date-plus-6-months>" --limit 10

Examples:

bash

newsjack news search --query "\"Dreamforce\" \"AI agents\" after:2025-03-15 before:2026-03-15" --limit 10
newsjack news search --query "\"Pumpkin Spice\" coffee after:2025-03-01 before:2026-03-01" --limit 10
newsjack news search --query "\"Black Friday\" \"coffee subscription\" after:2025-05-27 before:2026-05-27" --limit 10

Read the results like a PR strategist:

What format landed: trend piece, service journalism, data story, founder analysis, gift guide, event preview, expert reaction, local angle, product roundup, or trade recap.
What proof made it publishable: proprietary data, expert access, customer example, research, product news, survey, price data, local presence, or cultural timing.
Which outlets and desks covered it.
Whether the coverage was actually about the moment or only loosely adjacent.

Use that pattern to improve the plan's angle seeds. If last year's coverage was mostly gift guides, do not pitch a generic thought-leadership essay; suggest gift-guide assets and deadlines. If last year's coverage was analyst/expert reaction, suggest a tight expert POV with the right spokesperson. If coverage was thin or SEO-heavy, lower confidence or keep the moment on watch.

筛选出候选节点后，使用

news-search

研究每个可立即推介和有价值的观察节点去年同期的实际报道情况。这是为了获取灵感和校准方向，而非新鲜度校验。

控制研究范围：

仅研究通过参与资格和安全性审核的候选节点。
对于常规的六个月日历，最多研究排名前8-12的候选节点。如果数量更多，优先选择可立即推介的节点、已开启/即将关闭的推介窗口、以及品牌参与资格最明确的节点。
每个候选节点仅进行1-2次针对性搜索。无需全面研究所有可能的文章。

为每个候选节点确定往年搜索窗口：

以候选节点的
```
start_date
```
为基础。
将年份减一，得到去年同期的近似节点日期。如果日历源或往年报道明确给出了去年的具体日期，则使用该日期。
搜索周期性活动时，去掉活动名称中的年份，然后搜索该往年日期前后六个月的范围。

使用

news-search

newsjack news search

，并在查询中加入

after:

和

before:

参数。如果CLI不可用但已连接Medialyst MCP，则调用

mcp__medialyst__search_news

并使用相同的查询字符串。

bash

newsjack news search --query "\"<去掉年份的节点名称>\" after:<往年日期减6个月> before:<往年日期加6个月>" --limit 10

示例：

bash

newsjack news search --query "\"Dreamforce\" \"AI agents\" after:2025-03-15 before:2026-03-15" --limit 10
newsjack news search --query "\"Pumpkin Spice\" coffee after:2025-03-01 before:2026-03-01" --limit 10
newsjack news search --query "\"Black Friday\" \"coffee subscription\" after:2025-05-27 before:2026-05-27" --limit 10

以公关策略师的视角解读结果：

哪些报道形式获得了发布：趋势文章、服务类新闻、数据报道、创始人分析、礼品指南、活动预告、专家反应、本地视角、产品综述或行业回顾。
哪些证明材料使其得以发布：专属数据、专家访问权限、客户案例、研究成果、产品新闻、调查数据、价格数据、本地存在或文化时机。
哪些媒体渠道和编辑部进行了报道。
报道内容是否真正围绕该节点，还是仅松散相关。

利用这些模式优化规划方案中的角度雏形。如果去年的报道主要是礼品指南，不要推介通用的思想领导力文章；建议准备礼品指南相关素材并注意截止日期。如果去年的报道主要是分析师/专家反应，建议提供简洁的专家观点并安排合适的发言人。如果报道量少或偏重SEO，则降低信心等级或将该节点留在观察清单中。

Multiple Profiles

多配置文件处理

For one profile, do one calendar query and one review pass.

For multiple profiles, do not mix them in one giant review. Run each profile independently. If your runtime supports subagents, spawn one subagent per profile with the profile JSON and the same six-month window. Each subagent returns the calendar command it ran, selected moments, prior-year coverage searches, coverage patterns, avoid items, and gaps or clusters. Merge the profile-level outputs only after those independent reviews are complete.

对于单个配置文件，执行一次日历查询和一次审核。

对于多个配置文件，不要将它们混合在一次大规模审核中。独立运行每个配置文件的处理流程。如果运行时支持子代理，为每个配置文件生成一个子代理，传入配置文件JSON和相同的六个月时间窗口。每个子代理返回其执行的日历命令、筛选出的节点、往年报道搜索内容、报道模式、规避项以及空白期或密集期。仅在所有独立审核完成后，再合并各配置文件的输出结果。

Output

输出格式

Write readable markdown in this order:

Act this week. Moments whose pitch window is open, closing, or already missed. Put the user's next action first.

Six-month plan. Keep this table tight:

Date	Moment	Standing	Angle seed	Pitch window	Status	Evidence

Use one-line angle seeds. They are prompts for

angle-generator

, not finished angles. Evidence should include one source URL or API prior-coverage anchor plus, when researched, one short prior-year coverage pattern such as "2025 coverage was mostly gift guides" or "trade coverage favored expert reaction."

Watch list. Optional. Include only plausible moments that need a stronger proof asset.

Avoid. Sensitive or unsafe moments with a one-line reason.

Gaps & clusters. Quiet weeks to fill and crowded weeks to stagger. If a marquee moment for the brand appears to be missing from the feed, call it out here only. Do not place it in the plan unless the user supplied the date or you run a separate live query/source check that verifies it.

Coverage patterns. Briefly summarize what prior-year coverage taught you for the selected moments. Keep this to bullets, not a second report.

Command trail. List the exact

newsjack pr-calendar query

command(s) or Medialyst MCP tool call(s), the profile file(s), whether login was already configured or had to be completed before retrying, and the

newsjack news search

mcp__medialyst__search_news

queries used for prior-year coverage.

按以下顺序撰写易读的Markdown内容：

本周行动：推介窗口已开启、即将关闭或已过期的节点。将用户的下一步行动放在最前面。

六个月规划：保持表格简洁：

日期	节点	参与资格	角度雏形	推介窗口	状态	依据

角度雏形使用单行内容。它们是

angle-generator

的提示词，而非完整的推介角度。依据应包含一个来源URL或API往年报道锚点，以及（如果进行了研究）一条简短的往年报道模式，例如“2025年报道主要为礼品指南”或“行业报道偏好专家反应”。

观察清单：可选。仅纳入看似可行但需要更强证明材料的节点。

规避清单：敏感或不安全的节点，并附上一行原因说明。

空白期与密集期：需要填充内容的安静周和需要错开安排的密集周。如果品牌的重要节点未出现在日历源中，仅在此部分标注。除非用户提供了该日期或你进行了单独的实时查询/来源核查并确认其存在，否则不要将其纳入规划方案。

报道模式：简要总结从筛选出的节点的往年报道中获得的经验。使用项目符号列表，而非单独的报告。

命令记录：列出执行的精确

newsjack pr-calendar query

命令（或Medialyst MCP工具调用）、配置文件、登录是否已预先配置或需要完成后重试，以及用于往年报道搜索的

newsjack news search

mcp__medialyst__search_news

查询语句。

Handoff

交接流程

When the user picks a moment, hand it down the existing chain. Do not duplicate that work here:

```
angle-generator
```
- the calendar moment is the news peg.
```
find-journalists
```
- build the journalist list for the selected angle.
Drafting, then
```
fact-check
```
, then
```
voice-extractor
```
before anything is sent.

Provide a compact machine handoff as a secondary block:

json

{
  "moment": "<name>",
  "date": "<YYYY-MM-DD>",
  "news_peg": "<one-line peg>",
  "standing": "strong",
  "proof": ["<data/customer/spokesperson the brand can attach>"],
  "pitch_window": {
    "start": "<YYYY-MM-DD>",
    "deadline": "<YYYY-MM-DD>"
  },
  "source_urls": ["<url>"]
}

当用户选择某个节点时，将其传入现有工作流。不要在此处重复后续工作：

```
angle-generator
```
- 日历节点作为新闻切入点。
```
find-journalists
```
- 为选定的角度构建记者名单。
撰写文案，然后进行
```
fact-check
```
，再使用
```
voice-extractor
```
处理后发送。

提供一个紧凑的机器可读交接内容作为次要模块：

json

{
  "moment": "<名称>",
  "date": "<YYYY-MM-DD>",
  "news_peg": "<单行切入点>",
  "standing": "strong",
  "proof": ["<品牌可提供的数据/客户/发言人>"],
  "pitch_window": {
    "start": "<YYYY-MM-DD>",
    "deadline": "<YYYY-MM-DD>"
  },
  "source_urls": ["<url>"]
}

Boundaries

边界划分

CLI/API owns the data: dated opportunities, source URLs, prior coverage, tags, event type, and API pitch-window fields.
News-search owns coverage evidence: dated, attributed prior-year articles used to see what landed before.
This skill owns the judgment: standing, proof needs, brand safety, lead-time interpretation, coverage-pattern interpretation, drumbeat shaping, and the readable plan.
Downstream skills own execution: angles, journalist lists, drafts, fact-checking, and voice matching.
Stateless by default: do not save a calendar, seen-store, or inferred preferences unless the user explicitly asks to promote them into a profile or brief.

CLI/API负责数据：带日期的机会、来源URL、往年报道、标签、活动类型和API推介窗口字段。
News-search负责报道依据：带日期、有来源的往年文章，用于了解过往成功案例。
本技能负责判断：参与资格、证明材料需求、品牌安全性、前置准备时间解读、报道模式解读、节奏调整和易读的规划方案。
下游技能负责执行：推介角度、记者名单、文案撰写、事实核查和语气匹配。
默认无状态：除非用户明确要求将其保存到配置文件或简报中，否则不要保存日历数据、已查看记录或推断的偏好设置。