DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to filter out product builders when sourcing creators with Influencer Discovery

Use the topic gate and audience floors to keep only creators who bring their own readers.

Who it is forA partnerships manager who has been getting pitched by founders and needs only creators with real audiences.

The problemMany accounts that look like creators are people promoting their own product, which wastes outreach time.

The outcomeA contactable list limited to people who have followers, readers, or subscribers, with audience floors applied.

What you need first

  • Python 3.11 or newer
  • A clone of the repo or a copy of skills/influencer-discovery/ into your agent's skills folder
  • Credentials for any channel that needs an API key or logged-in session (see the datalayer credentials section)
  • For Google Sheets output: a Google Cloud project with the sheets, iam, and iamcredentials APIs enabled, and a service account that can edit the target Sheet

Steps

  1. Open the operating manual at skills/influencer-discovery/SKILL.md to see how the verdicts are assigned
  2. Run python3 skills/influencer-discovery/scripts/run.py --channels <channel> --subject <topic> --min-followers <n> with your floor (inferred, check the README)
  3. For Reddit or other karma-based channels, add --min-karma <n> as well (inferred, check the README)
  4. Check the verdict distribution in the printed report to see how many were filtered out
  5. Review the contactable rows in the Sheet before reaching out

Prompt for your agent

In the tigerless-labs/influencer-discovery repo, run the pipeline for --subject <topic> with --min-followers <n> and report how many candidates were rejected as product builders versus kept as contactable. Verify that every kept row in the report has an audience-based verdict.

Caveat. The README defines audience-owning creators only in general terms, so the exact filter behavior should be confirmed in SKILL.md before relying on it.

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