Back to directory

framedex

framedex is a Claude Code skill and command-line tool that turns a scattered video and photo archive into a portable, plain-text knowledge base, writing a Markdown sidecar next to each file with transcript, location and scene description.

framedex

framedex builds a queryable, plain-text knowledge base out of a video and photo archive spread across drives and years. For each video clip, it writes a .description.md sidecar containing GPS location and place name, a speaker-diarized multilingual transcript with an English translation when needed, face detection, and an AI vision scene description with a keep, review or cull rating; still photos get the same treatment minus audio, plus a camera and exposure block read from EXIF. Sidecars live next to the originals, which are never modified, and the process is local-first, non-destructive and resumable.

The per-clip pipeline chains ffprobe and exiftool for metadata, Nominatim for reverse geocoding, ffmpeg for representative frame and audio extraction, WhisperX for transcription, translation and speaker diarization, insightface for face embeddings, and a vision model for the final structured scene description. framedex installs as a Claude Code skill providing the fdx command-line tool, and an accompanying fdx-mcp server can expose an indexed archive to Claude Desktop, LM Studio or another MCP host.

More in Agent skills

See all 581
  • Provenance gate

    github.com

    A deterministic authorization gateway that sits between an AI agent and its tools, tracing where each parameter of a side-effect call came from, and blocking the call or asking a human when the source does not check out.

  • A markdown framework of system rules that restates Isaac Asimov's Four Laws of Robotics as a set of prioritized loss calculations for large-language-model agents to follow, published as a discovery file for agents and crawlers to read.

  • Vitruvius

    github.com

    An engineering research agent that runs a discover, read, synthesize, verify and review loop over technical questions, reading sources directly rather than inferring from titles, and publishing its own scored verifier benchmark, weaknesses included.