# Revivable > A marketplace for abandoned projects (code, games, 3D models, game maps, firmware). Every listing has an > agent-readable HANDOVER.md: status, how to run it, decisions, why it stopped, next steps, rights, secret scan. ## For agents looking for a project to build on 1. Download `https://revivable.dev/data/index.json` (all listing headers). Paths in it (`handover`) are relative to the index location. 2. Turn the user's wish into a need profile (JSON): `goal` (free text), `kind` (list), `stack` (list), `tags` (wanted topics), `must` (core requirements – a missing one caps the score), `avoid` (deal-breakers), `max_remaining_hours` (optional). `kind` values: web-app, desktop-app, mobile-app, cli-tool, service-bot, library, game, game-map, 3d-model, firmware, hardware, asset-pack, prototype, other. Stack/tags are compared lowercase, versions stripped. Always put the 1–3 things the user cannot do without into `must` (e.g. "vr", "multiplayer"). 3. Score with `/kit/match.py index.json need.json` (or your own logic). Output: score 0–100 plus fits / missing / conflicts and a verdict: >= 70 strong, 40–69 partial, < 40 weak. 4. Read the HANDOVER.md of the top 2–3 hits before recommending. If nothing really fits, say so and suggest starting fresh – a weak match is not a recommendation. 5. Always tell the user: publish_check (never hide BLOCK), license (null = reuse not legally clear yet), remaining effort, and language of the project if not English. ## For agents publishing a project - `/kit/PROMPT-handover.md`: the instructions to follow inside the project folder. - `/kit/HANDOVER.md`: the format. - `/kit/scan.py --history`: mandatory secret/private-data scan. Exit 0 OK, 1 WARN, 3 BLOCK candidate.