neeeophytee/ai-watermarks-reality-check · Archived

audit-provenance

Answer the five provenance questions for a single asset in one pass - was provenance located, verified, and trusted, was the scan complete, and what remains unknown.

First seen Aug 13, 2026

Installation

$ npx skills add neeeophytee/ai-watermarks-reality-check --skill audit-provenance

Summary

  • Answer the five provenance questions for a single asset in one pass - was provenance located, verified, and trusted, was the scan complete, and what remains unknown.
  • Use when a user asks for an overall provenance verdict on a file and does not want to orchestrate the individual analyzers themselves.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from neeeophytee/ai-watermarks-reality-check.

npx skills add neeeophytee/ai-watermarks-reality-check

Browse all from neeeophytee/ai-watermarks-reality-check

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 12
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,985 B
  • docs SUMMARY.md 324 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 17 installs

SKILL.md

Audit Provenance

The front door. Composes the low-level analyzers and reports one summary. It performs no new analysis of its own and issues no authorship classification.

All paths below are relative to this skill's directory. If you are running from elsewhere, use an absolute path to scripts/audit_provenance.py.

Workflow

  1. Run:

``bash python3 scripts/audit_provenance.py /absolute/path/to/asset \ --c2patool /path/to/c2patool \ --trust-anchors /path/to/policy.pem ``

  1. Report the four answers, then the unknowns. Never collapse them into a

single "verified" claim.

Answer Means
located Whether C2PA structure was found where the specification puts it
verified Whether a conforming verifier cryptographically validated the claim
trusted Whether the signer chained to the trust policy you named
scan_complete Whether the whole asset was inspected
  1. Read unknowns. Each entry states the question, why it is unanswered, and

the next step. Quote these; they are the point of the tool.

  1. Cite components when a reviewer needs to re-run one analyzer directly.

Boundaries

  • Without --c2patool, the cryptographic questions stay UNKNOWN. That is not

a pass.

  • Without --trust-anchors, trusted stays UNKNOWN. Trust is only meaningful

against a named policy.

  • located: NO is a bounded observation about supported carriers, never proof

that content is human-made.

  • This skill does not hide the six analyzers; use them directly for detail.

Read references/five-questions.md before changing how an answer is derived.