Create Gety Connector

Prerequisites

• git — to clone the sample repo.
• deno — the sample builds, tests, and runs entirely via deno task (no Node needed). Often not pre-installed; check deno --version and point the user to https://deno.com if missing.
• Gety desktop app installed with CLI integration enabled — not required to build or test the connector, only to install it and verify with gety search / gety doc.

Check these early; if git or deno is missing, ask the user to install before coding.

Workflow

1. Inspect the connector repo before editing.
   • New connectors must start from https://github.com/gety-ai/gety-sample-connector; do not hand-create a connector skeleton.
   • If there is no sample-derived repo, clone the sample repo into the user's requested folder, then adapt it.
   • If the current repo is not a clone/fork of gety-sample-connector, ask the user to switch to or clone a sample-based repo before coding.
   • Read references/gety-custom-connector-contract.md before changing manifest shape, SDK lifecycle, doc_link, metadata, state, file/download behavior, or validation commands.