project-photos

Generate deterministic provenance manifests mapping scanned photo captures to published names.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/rjwalters/bucket-brigade --skill project-photos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-photos
Source: https://github.com/rjwalters/bucket-brigade/tree/main/.anvil/skills/project-photos
Command: npx skills add https://github.com/rjwalters/bucket-brigade --skill project-photos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Digitized physical photo archives require a stable, machine-readable map linking original capture files to their published names, associated physical archive items, and rotation metadata, but manually creating and maintaining this mapping is error-prone and inconsistent across team members and sessions.

Core Features & Use Cases

  • Human-authoritative input parsing: Accepts human-authored numbering documents in markdown pipe table or CSV format, with case-insensitive column matching so document structure can vary without breaking the workflow.
  • Automatic metadata derivation: Derives the multi-item flag directly from stable output names (e.g., names ending in -multi set multi_item to true) and normalizes free-text rotation hints to canonical clockwise degree values, eliminating manual mapping errors.
  • Strict read-only safety: Never modifies, opens, or processes the bytes of source capture files, only reading directory listings to detect missing captures, ensuring original archive assets remain untouched.
  • Use Case: An archivist working with a collection of phone-captured scanned photos uses this skill to turn their handwritten numbering table into a consistent, version-controllable manifest that downstream image processing and publication tools can consume reliably.

Quick Start

Use the project-photos skill to generate a deterministic provenance manifest for your scanned photo archive using your human-authored numbering document and directory of original capture files.

Frequently Asked Questions about project-photos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a provenance manifest for digitized photo archives?▼

Yes, the provenance manifest generator accepts markdown pipe tables and CSV formats with case-insensitive column matching, allowing your numbering document structure to vary without breaking the digitized archive workflow.

Does the provenance manifest generator work with CSV numbering documents?▼

Yes, the provenance manifest generator accepts markdown pipe tables and CSV formats with case-insensitive column matching, allowing your numbering document structure to vary without breaking the digitized archive workflow.

Can I generate a manifest without modifying the original scanned capture files?▼

Strict read-only safety ensures original capture files remain untouched by only reading directory listings to detect missing captures, guaranteeing byte-identical deterministic output across identical inputs.

When do I need a deterministic manifest for photo archive digitization?▼

A deterministic manifest is required when a digitized physical photo archive needs a stable, machine-readable map linking capture files to published names, archive item IDs, and rotation metadata, preventing manual mapping inconsistencies.