Install
$ agentstack add skill-kdr-overcast-overcast-provenance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
overcast-provenance
Use this skill to answer "is this clip real / where did it come from?": given a suspect video, find the oldest copy and who posted it first. It is the inverse of overcast-copycat-sweep — searching backward toward the origin rather than forward for rips — and reuses its geometry-gating and verdict conventions. This skill answers WHERE a clip came from (origin / earliest copy); for whether it was ALTERED (manipulation/authenticity — C2PA, EXIF re-save, ELA overlays, a shadow check) use the complementary overcast-verify-media. Origin and authenticity are distinct, non-overlapping questions — the leading verify/exif pass below establishes provenance signals, not a fakery verdict. Use the broad overcast skill and overcast/reference/verbs.md for exact flags.
Workflow
- Check embedded provenance FIRST, then fingerprint the suspect clip. C2PA
Content Credentials (verify) and EXIF capture metadata (exif) are the most direct origin evidence when present — a signed manifest names the creator + edit history. They're often stripped on re-upload, so also fingerprint distinctive frames (which survive the re-encodes, crops, and watermarks that defeat exact hashes AND that strip metadata):
overcast doctor --sources --json
overcast case init --json
overcast verify ./suspect.mp4 --json # C2PA / Content Credentials: signer + edit manifest (needs c2patool)
overcast exif ./suspect.mp4 --json # capture device/time, editing software, GPS (needs exiftool)
overcast watch ./suspect.mp4 --json # content + transcript into memory
overcast index create origin --type image-ransac --local --json
overcast image add ./distinctive-frame.png --index --json
- Reverse-image-search the frames and sweep sources with topic keywords — crucially
with NO --since floor, since older results sit closer to the origin:
overcast source add "lens:./distinctive-frame.png" --json
overcast source add "x:video:" --json
overcast source add "youtube:search:" --json
overcast source add "web:" --json
overcast scan --limit 20 --json
- Triage on metadata alone: sort candidate hits by
publishedASC — the earliest
dates are your origin candidates; carry author + URL forward.
- Capture the oldest few and confirm they are the SAME content (not a look-alike) —
frame match plus transcript:
overcast capture --json
overcast image match --index --draw --json # --draw writes the RANSAC overlay proof
overcast listen --json
- Record the origin verdict.
--reftheimage matchrecord so its overlay rides
into the brief; ALWAYS leave a tldr note with the date chain — even "undetermined":
overcast finding create "origin: earliest confirmed copy is @ (frame match 88 inliers, transcript identical); the viral post is a re-upload" --ref --confidence high --json
overcast note "swept lens + x + youtube + web (no recency floor); candidates; earliest confirmed by @; verdict: re-upload" --tag tldr --json
# Wait for the note result before exporting, so the TL;DR is included.
overcast brief --export ./provenance.html --json
Output
An origin verdict — original / re-upload-of- / undetermined — with the date chain, the earliest confirmed poster and URL, which layers agreed (frame + transcript), and the strongest record.id + media.at citations. "Undetermined" is honest when the earliest copy can't be confirmed as the same content.
Caveats
The earliest date you FIND is a floor, not proof of origin — deleted posts and platforms you didn't search may predate it; say so. Confirm same-content with the gated image match (a high inlier count on a degenerate homography is the main false positive — eyeball the --draw overlay) plus transcript; a shared topic or a look-alike frame is not the same clip. Face similarity is 0–100; image match is an inlier count + a 0–1 ratio, never a 0–100 score. Apify sources bill per result. lens ignores --since.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kdr
- Source: kdr/overcast
- License: Apache-2.0
- Homepage: https://overcast.video
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.