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

How to source blog writers from tier 2 platforms with Influencer Discovery

Run the pipeline on DEV.to, Hashnode, WordPress.com, and Micro.blog to find writers with readers.

Who it is forA content partnerships lead who wants writers who publish on blog platforms rather than social feeds.

The problemBlog-based writers are scattered across platforms, and their contact details are not in one place.

The outcomeA Sheet of blog-platform writers with contact info, appended from a single tier run.

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. Clone the repo and run python3 skills/influencer-discovery/scripts/run.py --help to confirm setup
  2. Check reference/datalayer for which tier 2 channels need credentials
  3. Run python3 skills/influencer-discovery/scripts/run.py --tiers 2 --per-channel 10 --subject <topic> (inferred, check the README)
  4. Read the run report for planned vs actual counts per channel
  5. Confirm the new rows in the Sheet and skip any with missing contact fields

Prompt for your agent

Using tigerless-labs/influencer-discovery, run the pipeline with --tiers 2 --per-channel 10 --subject <topic> and report the planned vs actual counts and the contactable list. Verify that the run only touched tier 2 channels.

Caveat. Tier 2 coverage depends on each platform's public contact data, so some writers will appear without a usable contact.

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