originality-reviewlisted
Install: claude install-skill sebastian-software/skills.sebastian-software.com
# Originality Review
Compare the delivered work with the complete supplied reference corpus. Treat
the audit as an evidence exercise: exact overlap, distinctive combination,
common grammar, and missing provenance are different findings.
## Workflow
1. Lock the audit boundary:
- audit only, or audit plus authorized fixes;
- current output, history, or both;
- references and categories promised by the brief;
- release decision and risk tolerance owner.
2. Build a source registry. Record every supplied reference, role, path or URL,
date or version when known, ownership or license evidence supplied by the
user, and which categories it can prove. Prefer contemporaneous local
evidence when a live source may have changed.
3. Inventory the current work:
- rendered and hidden text, metadata, labels, names, claims, and numbers;
- images, video, audio, fonts, icons, textures, screenshots, and downloads;
- layout order, distinctive compositions, interaction, motion, and timing;
- source files, built output, asset records, credits, and relevant history.
4. Read [Audit rubric](references/audit-rubric.md). Compare category by category
rather than using one overall visual impression.
5. Read [Provenance and history](references/provenance-and-history.md) when
exact files, transformed media, licenses, deleted material, or repository
history are in scope.
6. Triangulate every finding:
- identify the current artifact and exact location;
- identi