neeeophytee/ai-watermarks-reality-check · Archived

audit-metadata-privacy

Audit supported metadata surfaces in images, SVG, PDF, and OOXML assets for privacy signals such as GPS, author, device, software, comments, and timestamps. Use when preparing a public release and metadata exposure must be assessed without altering or invalidating provenance.

First seen Aug 13, 2026

Installation

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

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,908 B
  • docs SUMMARY.md 306 B

History

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

SKILL.md

Audit Metadata Privacy

Find disclosure risks without modifying the file. Report categories and severity; do not print sensitive values by default.

Supported containers: PNG, JPEG (EXIF, XMP, IPTC-IIM, COM), WebP, BMFF (MP4/HEIC/AVIF), TIFF, PDF, SVG, OOXML and ODF.

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

Workflow

  1. Run:

``bash python3 scripts/audit_metadata.py /absolute/path/to/asset ``

  1. Review findings, which contain categories and evidence locations rather than raw values.
  2. Treat HIGH findings such as GPS as requiring deliberate review before publication.

GPS is also read from EXIF IFD1 (the embedded thumbnail), which commonly retains location after the primary IFD has been scrubbed.

  1. If format_supported is false, say so explicitly rather than reporting a clean result.
  2. Before removing anything, verify whether the field belongs to a signed C2PA manifest.
  3. If a sanitized derivative is needed, preserve the original, document the transformation, and re-run provenance verification on the derivative.

Boundaries

  • This skill is audit-only and never rewrites the source.
  • NONE_OBSERVED is not a guarantee; the bounded parser can miss encrypted, proprietary, malformed, unsupported, or remotely stored metadata.
  • Provenance metadata is not automatically a privacy risk.
  • Ordinary metadata removal can invalidate a signed asset.

Read references/privacy-boundaries.md before recommending a mutation workflow.