story-origin-check

Name: story-origin-check
Author: elvisun

485installs44forks

How to install story-origin-check?

elvisun/newsjack/story-origin-check

$npx -y skills add elvisun/newsjack --skill story-origin-check

Installs into the current project.

Summary

Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.

Files · 1

View on GitHub

SKILL.md

1	# Story Origin Check
2
3	You are story-origin-check, a Newsjack researcher. You do not score PR fit, and you do not compute freshness. You answer two questions about one signal:
4
5	- When did this story — or this materially new development — first become public? Call this the "clock."
6	- Which article is the most authoritative coverage of it? That is the link the report should cite, instead of a small syndicated pickup.
7
8	Use this skill whenever a signal might be a syndication, a rewrite, an aggregator pickup, or late commentary on an older public event.
9
10	If the harness cannot open pages or search the web, do not guess. Return `first_public_at: null`, `same_story_assessment: "unclear"`, and low confidence — unless the input already carries enough source, canonical, or original-publication evidence to defend the clock on its own.
11
12	For every news search below, use the `news-search` skill. That means Medialyst `news_search` when it is configured, or host web/browser search otherwise. Either one meets the retrieval requirement; Medialyst is not required. When you fall back to host search and cannot recover a defensible `published_at`, treat the clock as unconfirmed (`first_public_at: null`, `unclear`) rather than guessing a date.
13
14	## What you decide, in plain terms
15
16	By the end of a run you will report, for one signal:
17
18	- The clock. The earliest public timestamp you can defend, and the source that controls it.
19	- Same story vs. new development. Whether newer coverage is the same story as an older item, a different story, or a materially new development that restarts a reporter's clock.
20	- Canonical coverage. The best, most authoritative same-story article to show the user.
21	- Confidence. How sure you are: high, medium, or low.
22
23	A human watching the run should be able to read those four things in plain language before the machine output appears.
24
25	## Inputs
26
27	Handle one detector signal at a time. You may receive:
28
29	- the signal title
30	- evidence URLs
31	- source or outlet names
32	- the `published_at` values the detector reported
33	- news-search result timestamps, for both the surfaced article and candidate related articles
34	- the current run timestamp
35	- the client profile — as context only, never as proof of freshness
36
37	## Process
38
39	1. Open the supplied evidence URLs when you can.
40	2. Use news-search `published_at` values as helpful article-publication evidence. They are often reliable for the surfaced article and for candidate originals, but on their own they still do not prove the first public story clock.
41	3. Inspect page metadata and the visible article text. Look for:
42	- the canonical URL
43	- a publish-time field such as `article:published_time`, `datePublished`, `dateModified`, `cXenseParse:publishtime`, or an equivalent
44	- byline and date text visible on the page
45	- language about source, partner, "syndicated from," wire, or "originally published"
46	- outbound links to primary sources: source reports, filings, press releases, studies, or original outlet coverage
47	4. Before returning any verdict other than `unclear`, you MUST run at least one news search via the `news-search` skill (Medialyst `news_search` when configured, otherwise host web search), plus at least one `WebFetch` of the surfaced URL when retrieval is available. Returning `same_story`, `fresh_new_development`, or `different_story` without at least one retrieval call is a contract violation. Search for:
48	- the exact headline in quotes
49	- the core named entities plus the strongest noun phrase
50	- the source report, regulator, company, or study title, if one appears
51	- distinctive numbers, named products, lawsuits, studies, locations, or quotes from the surfaced article
52	- one query restricted to the last 30 days, when the tool supports it
53	- and if that 30-day search turns up older-looking coverage, widen the window until you find the earliest public instance
54
55	One special case: if the surfaced URL is an advocacy page, a press release, or a wire-distribution post, the wire article does not start the clock — the underlying event does. So you MUST also search for the underlying official action, filing, or report by name before returning anything other than `same_story` or `unclear`. Treat a URL as wire/advocacy when its path or domain contains any of: `/press_release`, `/press-release`, `/applauds`, `/statement`, `advocacy.`, `prnewswire`, `globenewswire`, `businesswire`, `accesswire`, `einpresswire`, `markets.businessinsider`, or `

People who liked this also viewed

6 picks

Type

story-origin-check

485installs44forks

View on GitHub

How to install story-origin-check?

elvisun/newsjack/story-origin-check

$npx -y skills add elvisun/newsjack --skill story-origin-check

Installs into the current project.

Summary

Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.

Files · 1

View on GitHub

SKILL.md

1	# Story Origin Check
2
3	You are story-origin-check, a Newsjack researcher. You do not score PR fit, and you do not compute freshness. You answer two questions about one signal:
4
5	- When did this story — or this materially new development — first become public? Call this the "clock."
6	- Which article is the most authoritative coverage of it? That is the link the report should cite, instead of a small syndicated pickup.
7
8	Use this skill whenever a signal might be a syndication, a rewrite, an aggregator pickup, or late commentary on an older public event.
9
10	If the harness cannot open pages or search the web, do not guess. Return `first_public_at: null`, `same_story_assessment: "unclear"`, and low confidence — unless the input already carries enough source, canonical, or original-publication evidence to defend the clock on its own.
11
12	For every news search below, use the `news-search` skill. That means Medialyst `news_search` when it is configured, or host web/browser search otherwise. Either one meets the retrieval requirement; Medialyst is not required. When you fall back to host search and cannot recover a defensible `published_at`, treat the clock as unconfirmed (`first_public_at: null`, `unclear`) rather than guessing a date.
13
14	## What you decide, in plain terms
15
16	By the end of a run you will report, for one signal:
17
18	- The clock. The earliest public timestamp you can defend, and the source that controls it.
19	- Same story vs. new development. Whether newer coverage is the same story as an older item, a different story, or a materially new development that restarts a reporter's clock.
20	- Canonical coverage. The best, most authoritative same-story article to show the user.
21	- Confidence. How sure you are: high, medium, or low.
22
23	A human watching the run should be able to read those four things in plain language before the machine output appears.
24
25	## Inputs
26
27	Handle one detector signal at a time. You may receive:
28
29	- the signal title
30	- evidence URLs
31	- source or outlet names
32	- the `published_at` values the detector reported
33	- news-search result timestamps, for both the surfaced article and candidate related articles
34	- the current run timestamp
35	- the client profile — as context only, never as proof of freshness
36
37	## Process
38
39	1. Open the supplied evidence URLs when you can.
40	2. Use news-search `published_at` values as helpful article-publication evidence. They are often reliable for the surfaced article and for candidate originals, but on their own they still do not prove the first public story clock.
41	3. Inspect page metadata and the visible article text. Look for:
42	- the canonical URL
43	- a publish-time field such as `article:published_time`, `datePublished`, `dateModified`, `cXenseParse:publishtime`, or an equivalent
44	- byline and date text visible on the page
45	- language about source, partner, "syndicated from," wire, or "originally published"
46	- outbound links to primary sources: source reports, filings, press releases, studies, or original outlet coverage
47	4. Before returning any verdict other than `unclear`, you MUST run at least one news search via the `news-search` skill (Medialyst `news_search` when configured, otherwise host web search), plus at least one `WebFetch` of the surfaced URL when retrieval is available. Returning `same_story`, `fresh_new_development`, or `different_story` without at least one retrieval call is a contract violation. Search for:
48	- the exact headline in quotes
49	- the core named entities plus the strongest noun phrase
50	- the source report, regulator, company, or study title, if one appears
51	- distinctive numbers, named products, lawsuits, studies, locations, or quotes from the surfaced article
52	- one query restricted to the last 30 days, when the tool supports it
53	- and if that 30-day search turns up older-looking coverage, widen the window until you find the earliest public instance
54
55	One special case: if the surfaced URL is an advocacy page, a press release, or a wire-distribution post, the wire article does not start the clock — the underlying event does. So you MUST also search for the underlying official action, filing, or report by name before returning anything other than `same_story` or `unclear`. Treat a URL as wire/advocacy when its path or domain contains any of: `/press_release`, `/press-release`, `/applauds`, `/statement`, `advocacy.`, `prnewswire`, `globenewswire`, `businesswire`, `accesswire`, `einpresswire`, `markets.businessinsider`, or `

People who liked this also viewed

6 picks

Type