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

How to build a source-cited social research report with Jev Social

Run a read-only research goal across Instagram, TikTok, or LinkedIn and get a cited Markdown report.

  • Top pick
  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Credentials. Jev runs in the Chrome profile you select, so use a separate profile or test account for sensitive research.

Who it is forA market researcher or analyst who needs to understand what people are posting about a topic on one or more social platforms.

The problemManually reading social feeds is slow, and findings are hard to trace back to specific public posts or profiles.

The outcomeA report.md where each accepted finding cites a captured source, plus a history of every operation Jev chose.

What you need first

  • Node 22 or newer
  • Chrome already signed in to Instagram, TikTok, or LinkedIn
  • An OpenRouter API key for the default decision provider
  • A current socai CLI (onboarding can install it on macOS and Windows; on Linux install it first and set it on PATH or SOCAI_BIN)

Steps

  1. Install Node 22 or newer and sign in to Instagram, TikTok, or LinkedIn in Chrome.
  2. npx github:socai-io/jev-social#v0.1.13 onboard
  3. npx github:socai-io/jev-social#v0.1.13
  4. Enter a research goal naming the platform, for example: find handmade art on Instagram.
  5. Open the downloaded report.md and check that each finding links to a captured source.

Prompt for your agent

Use the socai-io/jev-social repo to research <topic> on <platform> in my signed-in Chrome. Expected output: a source-cited report.md. Verify that every finding links to a captured source URL and that any login gate is reported as a partial result, not a success.

Caveat. Login gates and step limits produce partial results, and report synthesis may incur OpenRouter usage unless OPENROUTER_REPORT_MODEL=off is set.

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