菜单
Set up a lightweight Google Alerts-style coverage tracker for any number of keywords. Creates a tracker config with each keyword and what it actually means, then hands recurrence to the user's agent harness.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/elvisun/newsjack --skill coverage-tracker-setup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | coverage-tracker-setup |
| description | Set up a lightweight Google Alerts-style coverage tracker for any number of keywords. Creates a tracker config with each keyword and what it actually means, then hands recurrence to the user's agent harness. |
| when_to_use | User wants to create, configure, or update coverage alerts, brand/company mention tracking, Google Alert-style monitoring, or keyword coverage tracking. Use this instead of newsjack-monitor-setup when the job is to track coverage of the user's own keywords rather than find newsjacking opportunities. |
This sets up a simple keyword tracker that the coverage-tracker skill runs for you. Think of it like a Google Alert: it watches for new coverage of the keywords you care about and tells you when something real shows up.
It is deliberately a different job from setting up newsjack monitoring. A coverage tracker answers "did my keyword get real coverage?" Newsjack monitoring (newsjack-monitor-setup) answers a bigger question: "can my company jump into a broader news story?" If the user wants the second one, use that skill instead.
Two situations, and they change what you can finish here:
newsjack is installed. It ships as a prebuilt, bundled binary — you do not need Go, a compiler, or any build/install step. Never look for a Go toolchain or tell the user they need a "Go environment" without checking first: run ; if that's not on , try the bundled location and use that full path everywhere if it works. The bundled binary is almost always already installed — verify, don't assume it's missing.newsjack --versionPATH~/.newsjack/bin/newsjack --versionOnly ask for what you don't already know:
Don't ask about company standing, spokespeople, competitors, proof assets, news feeds, target reporters, or story angles. All of that is for newsjacking, not for tracking coverage of your own keywords.
Write the tracker config. This is a small file that the coverage-tracker skill reads back every time it runs, so keep its shape exactly as shown:
{
"name": "Profound",
"lookback_days": 2,
"keywords": [
{
"keyword": "profound",
"means": "Profound, the AI search analytics company.",
"exclude_hints": ["generic adjective uses"]
}
]
}
You can list as many keywords as you want. The means line for each one matters: make it specific (which company, product, or person) so the tracker can later throw out mentions of the wrong thing or generic uses of the word.
If you're in a plain chat window, stop here. Hand the user this config plus the schedule prompt from step 3, and tell them to finish in a setup that can save and run things. Don't claim it was saved or scheduled.
Save the config with this command (replace <slug> with a short name for the tracker):
newsjack coverage init <slug> --config tracker.json
Working inside a copy of the project source, use bin/newsjack from the project root instead. Only add --force if the user clearly wants to overwrite a tracker that already exists.
Schedule the recurring check through your agent, not your computer's built-in scheduler. If your agent has a way to schedule prompts, schedule this one:
Use the coverage-tracker skill for <slug>.
If your agent can't schedule things itself, tell the user exactly which prompt to set up on a schedule in Claude, Codex, Hermes, OpenClaw, or whatever they use. Do not set up system-level schedulers (cron, launchd, systemd timers, or similar) on the user's machine.
Run it once right away if the user wanted a working setup, or if you're doing the whole setup end to end. Use the coverage-tracker skill for the new slug and tell the user what the first run found.
First, look up where the config lives:
newsjack coverage status <slug>
That shows a config_path. Open the config file there, make your edits, then save it again with:
newsjack coverage init <slug> --config tracker.json --force
Only change the keywords or their meaning notes. The record of what's already been seen and alerted on is kept separately by coverage-tracker (in its own database) — don't edit that by hand.
Wrap up by giving them: