Agent skill · Audited from source
story-origin-check
skill · elvisun/newsjackMIT licenceAudited 13 Nov 2026 · source 6759e995ad1e
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 6759e995ad1e and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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.
Cite
Cite this page
ModelsAtlas. “story-origin-check (elvisun/newsjack)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/elvisun/story-origin-check
Trust audit
Audit 0.4.1 · source read 13 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 6759e995ad1e · 13 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherelvisun GitHub userOwner of the repository this skill is read from
- Source folderelvisun/newsjack/skills/story-origin-checkThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict6759e995ad1eA new audit runs when the source changes
- Repository statusNot archivedLast push 1 day ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: 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.
--- name: story-origin-check description: "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." when_to_use: "Use before deterministic freshness gating, before sending beta cron output, or whenever evidence comes from aggregators, syndication partners, copied wire articles, rewritten secondary coverage, or search results with suspiciously recent timestamps." metadata: category: Detect --- # Story Origin Check 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: - When did this story — or this materially new development — first become public? Call this the "clock." - Which article is the most authoritative coverage of it? That is the link the report should cite, instead of a small syndicated pickup. Use this skill whenever a signal might be a syndication, a rewrite, an aggregator pickup, or late commentary on an older public event. 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. 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. ## What you decide, in plain terms By the end of a run you will report, for one signal: - **The clock.** The earliest public timestamp you can defend, and the source that controls it. - **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. - **Canonical coverage.** The best, most authoritative same-story article to show the user. - **Confidence.** How sure you are: high, medium, or low. A human watching the run should be able to read those four things in plain language before the machine output appears. ## Inputs Handle one detector signal at a time. You may receive: - the signal title - evidence URLs - source or outlet names - the `published_at` values the detector reported - news-search result timestamps, for both the surfaced article and candidate related articles - the current run timestamp - the client profile — as context only, never as proof of freshness ## Process 1. Open the supplied evidence URLs when you can. 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. 3. Inspect page metadata and the visible article text. Look for: - the canonical URL - a publish-time field such as `article:published_time`, `datePublished`, `dateModified`, `cXenseParse:publishtime`, or an equivalent - byline and date text visible on the page - language about source, partner, "syndicated from," wire, or "originally published" - outbound links to primary sources: source reports, filings, press releases, studies, or original outlet coverage 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: - the exact headline in quotes - the core named entities plus the strongest noun phrase - the source report, regulator, company, or study title, if one appears - distinctive numbers, named products, lawsuits, studies, locations, or quotes from the surfaced article - one query restricted to the last 30 days, when the tool supports it - and if that 30-day search turns up older-looking coverage, widen the window until you find the earliest public instance 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 `stocktitan`. Do not contradict your own evidence. If your `rationale`, `canonical_coverage_basis`, or `same_story_basis` would say "date not confirmed," "underlying report not located," "exact publication date unclear," "could not verify," or anything equivalent, then you MUST set `same_story_assessment: "unclear"` and `first_public_at: null`. 5. Collect two sets of candidates: - **Timestamp candidates** — the earliest public items that might start the clock: official releases, filings, reports, source studies, wires, or first outlet stories. - **Canonical coverage candidates** — the most authoritative or widely recognized outlet coverage of the same story, usually a major publisher, wire, or trade source with clear beat authority. 6. Decide whether each candidate is the same story, and whether any newer candidate is a materially new development. ## Same-Story Judgment You — the LLM — make this call. Do not lean on title similarity alone. Treat
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 6759e99
git clone https://github.com/elvisun/newsjack git -C newsjack checkout 6759e995ad1e
The author documents no install command, so this uses the repository directly. Our verdict covers commit 6759e995ad1e only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
6759e995ad1e
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/elvisun/story-origin-check/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
elvisun/newsjack
Capture a user's real writing voice from 5-20 prior samples, store a local voice.yaml fingerprint, and enforce it on newsjack drafts so AI tells disappear. Measures voice with named stylometry lenses (Burrows's Delta…
elvisun/newsjack
Triage inbound journalist source queries and draft a response only when the user's expertise is a real fit. Runs each query through proven source-request lenses (4-gate fit triage, credential-standing test, deadline…
elvisun/newsjack
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitor_only, or reject — never ranks, writes angles,…
elvisun/newsjack
Score whether a news event is worth newsjacking, or whether a user's pitch idea is actually newsworthy to journalists. Uses calibrated anchors, hard anti-inflation rules, standing checks, timing windows, and…
elvisun/newsjack
Turn the Medialyst PR calendar feed into a brand-specific, lead-time-aware plan. Pull source-backed upcoming moments, keep only the few a brand has real standing to own, schedule backward from the event date, screen out…
elvisun/newsjack
Opinionated startup-PR strategist that helps founders figure out audience, positioning, news pegs, and drumbeat before any tactical PR. Refuses outlet-naming-before-audience, mass blasts, vanity metrics, and premature…
Add this badge to your README
[](https://modelsatlas.com/skills/elvisun/story-origin-check/)
<a href="https://modelsatlas.com/skills/elvisun/story-origin-check/"><img src="https://modelsatlas.com/skills/elvisun/story-origin-check/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about story-origin-check
What does the story-origin-check skill do?
Is story-origin-check safe to install?
What can story-origin-check access on my machine?
How current is this page?
Sources
- github.com/elvisun/newsjack/tree/main/skills/story-origin-check — the audited source at commit 6759e995ad1e and every finding aboveObserved · 13 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the story-origin-check skill do?
- Is story-origin-check safe to install?
- What can story-origin-check access on my machine?