DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to export all visibility data as JSON or CSV with Open

Pull the whole instance into one JSON file or a folder of CSVs for your own analysis or board material.

Who it is forAn analyst who must put AI visibility figures into a spreadsheet, BI tool or board deck and needs a reproducible copy of the underlying rows.

The problemA metric that goes into a board deck should be recomputable from stored data, but closed tools rarely export it.

The outcomeA complete export of prompts, answers and metrics that can be recomputed outside the tool, optionally limited to recent rows with `--since`.

What you need first

  • macOS or Linux terminal with curl
  • Either a free Limelit Cloud account (sign in with Google) or your own provider API key, such as OpenAI's
  • Your brand domain, category and up to five competitor sites

Steps

  1. Stop at a working instance that has completed at least one run, in the folder that holds the binary.
  2. Run limelit export to write the whole instance as one JSON document or a directory of CSVs.
  3. Use the --since filter to limit the export to rows from a chosen date onward.
  4. Load the output into your spreadsheet or BI tool and recompute one figure from the formulas in the README to confirm it matches the dashboard.

Prompt for your agent

In the limelit-co/open repository, run `limelit export` for the instance in ~/limelit and write the output to <output-path>. Expected output is a JSON document or CSV directory covering all answers. Verify that the row count for <engine-name> matches the dashboard count for that engine.

Caveat. The export contains your prompts and every stored answer, so keep the output file as private as the SQLite database it came from.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page