# AI use cases for Influencer Discovery (tigerless-labs/influencer-discovery) Repo: [tigerless-labs/influencer-discovery](https://github.com/tigerless-labs/influencer-discovery) | Use cases: 4 | Page: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/ A Claude Code skill and Python pipeline that searches 15 channels for creators who bring their own audience, pulls their public contact info, and appends them to a Google Sheet. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build a creator shortlist for a topic in one run: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/build-creator-shortlist-for-topic/ - Filter out product builders when sourcing creators: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/find-audience-creators-excluding-founders/ - Source blog writers from tier 2 platforms: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/source-blog-writers-across-tier-2/ - Connect the pipeline to a Google Sheet safely: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/connect-pipeline-to-google-sheet/ ## How to build a creator shortlist for a topic in one run with Influencer Discovery Repo: [tigerless-labs/influencer-discovery](https://github.com/tigerless-labs/influencer-discovery) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Search Tier 1 social channels for creators on a topic and append contactable ones to a Sheet. **Who it is for:** A marketing lead planning a campaign who needs creators with their own audience on a specific subject this week. **The problem:** Finding creators by hand across many platforms is slow, and founders building their own products clutter the results. **The outcome:** A run report with planned vs actual counts, a verdict breakdown, and a contactable list, with new rows appended to the Google Sheet. ### Steps 1. Clone the repo with `git clone https://github.com/tigerless-labs/influencer-discovery && cd influencer-discovery` 2. Confirm the CLI loads with `python3 skills/influencer-discovery/scripts/run.py --help` 3. Put any required credentials in `~/.config/influencer-discovery/.env`, never in the repo 4. Run a first pass with `python3 skills/influencer-discovery/scripts/run.py --tiers 1 --per-channel 10` and add `--subject ` to set the topic gate (inferred, check the README) 5. Read the printed report and review the contactable list before using any contact ### Prompt to paste into your agent ```text Using the repo tigerless-labs/influencer-discovery, run the pipeline with --tiers 1 --per-channel 10 and --subject , then report planned vs actual counts, the verdict distribution, and the contactable list. Verify that the report shows contactable creators and that no row was edited in the Sheet, only appended. ``` ### Caveat Per-channel requirements and costs are in the datalayer reference, so check which channels work with zero credentials before a run. Risk, credentials: Some channels need an API key or logged-in session, so store them only in ~/.config/influencer-discovery/.env and never paste them into an agent prompt. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/build-creator-shortlist-for-topic/ ## How to filter out product builders when sourcing creators with Influencer Discovery Repo: [tigerless-labs/influencer-discovery](https://github.com/tigerless-labs/influencer-discovery) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use the topic gate and audience floors to keep only creators who bring their own readers. **Who it is for:** A partnerships manager who has been getting pitched by founders and needs only creators with real audiences. **The problem:** Many accounts that look like creators are people promoting their own product, which wastes outreach time. **The outcome:** A contactable list limited to people who have followers, readers, or subscribers, with audience floors applied. ### 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 --subject --min-followers ` with your floor (inferred, check the README) 3. For Reddit or other karma-based channels, add `--min-karma ` 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 to paste into your agent ```text In the tigerless-labs/influencer-discovery repo, run the pipeline for --subject with --min-followers 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/find-audience-creators-excluding-founders/ ## How to source blog writers from tier 2 platforms with Influencer Discovery Repo: [tigerless-labs/influencer-discovery](https://github.com/tigerless-labs/influencer-discovery) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Run the pipeline on DEV.to, Hashnode, WordPress.com, and Micro.blog to find writers with readers. **Who it is for:** A content partnerships lead who wants writers who publish on blog platforms rather than social feeds. **The problem:** Blog-based writers are scattered across platforms, and their contact details are not in one place. **The outcome:** A Sheet of blog-platform writers with contact info, appended from a single tier run. ### 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 ` (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 to paste into your agent ```text Using tigerless-labs/influencer-discovery, run the pipeline with --tiers 2 --per-channel 10 --subject 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/source-blog-writers-across-tier-2/ ## How to connect the pipeline to a Google Sheet safely with Influencer Discovery Repo: [tigerless-labs/influencer-discovery](https://github.com/tigerless-labs/influencer-discovery) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Mint a short-lived token by impersonating a service account so no key file sits on disk. **Who it is for:** A developer setting up shared outreach tracking who must avoid a long-lived service account key. **The problem:** Google blocks the spreadsheets scope on plain gcloud ADC, and storing a key file on disk is a risk. **The outcome:** A working Sheets connection that appends rows using a token that expires after an hour. ### Steps 1. Set INFLUENCER_DISCOVERY_SPREADSHEET_ID in the config so the pipeline knows the target Sheet 2. Enable the sheets, iam, and iamcredentials APIs in the Google Cloud project 3. Grant your ADC identity roles/iam.serviceAccountTokenCreator on the service account and confirm the service account can edit the Sheet 4. Run `T=$(gcloud auth application-default print-access-token)` and then the `curl -s -X POST` call to the iamcredentials generateAccessToken endpoint from the README, replacing YOUR_SA_EMAIL 5. If the first call returns 403, wait about 30 seconds and retry, since IAM bindings take time to propagate ### Prompt to paste into your agent ```text Configure tigerless-labs/influencer-discovery to append to a Google Sheet using a short-lived token from the iamcredentials API for . Verify that the header row matches the pipeline's mapping and that a test run appends one row without editing existing cells. ``` ### Caveat The pipeline aborts if the Sheet header row does not match its mapping, so set up the header before the first run. Risk, credentials: The token call uses your ADC identity and a service account, so keep both out of shared logs and chat transcripts. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/tigerless-labs-influencer-discovery/connect-pipeline-to-google-sheet/