Skip to content
Back to search

influencer-discovery

Influencer discovery & contact enrichment pipeline that runs as a Claude Code skill — 15 channels, stdlib only, appends to a Google Sheet

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tigerless-labs--influencer-discovery/badge.svg)](/listings/tigerless-labs--influencer-discovery)

HTML

<a href="/listings/tigerless-labs--influencer-discovery"><img src="/api/listings/tigerless-labs--influencer-discovery/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

No third-party packages, no build step — the pipeline is pure standard library (Python ≥ 3.11). The skill is fully self-contained under `skills/influencer-discovery/`; clone and run, or copy that one directory into your agent's skills folder:

git clone https://github.com/tigerless-labs/influencer-discovery && cd influencer-discovery
python3 skills/influencer-discovery/scripts/run.py --help

Credentials go in `~/.config/influencer-discovery/.env`, never in the repo. Pipeline state lives in `~/.local/share/influencer-discovery/`; both paths are overridable via `INFLUENCER_DISCOVERY_CONFIG_DIR` / `INFLUENCER_DISCOVERY_STATE_DIR`. Knobs that travel with the code (channel list, throttle parameters, header mapping) stay in `skills/influencer-discovery/config/`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 92 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h1 align="center">Influencer Discovery</h1>
  2. <p align="center"><strong>Find creators who bring their own audience — and get their contact info</strong></p>
  3. <p align="center">
  4. <img src="https://img.shields.io/badge/python-3.11%2B-blue.svg" alt="python" /> <img src="https://img.shields.io/badge/dependencies-stdlib%20only-brightgreen.svg" alt="zero dependencies" /> <img src="https://img.shields.io/badge/platform-Linux%20%7C%20macOS-lightgrey.svg" alt="platform" /> <img src="https://img.shields.io/badge/channels-15-orange.svg" alt="channels" />
  5. </p>
  6. **influencer-discovery is a creator-discovery pipeline that runs as a Claude Code skill.** It searches 15
  7. channels for people **who bring their own audience** — followers, readers, subscribers — pulls
  8. their public contact info, and appends them to a Google Sheet. People building their own product
  9. are filtered out: they want reach, they don't provide it.
  10. The operating manual is [skills/influencer-discovery/SKILL.md](skills/influencer-discovery/SKILL.md). Per-platform
  11. capability boundaries (what each API exposes, which credentials it needs, what it costs) live in
  12. [reference/datalayer/](skills/influencer-discovery/reference/datalayer/index.md); how contact info is
  13. obtained per channel lives in
  14. [reference/methodology/](skills/influencer-discovery/reference/methodology/index.md), where the
  15. directory-name prefix is the cooperation priority.
  16. ## Channels
  17. | Tier | Channels |
  18. |---|---|
  19. | **1 · Social** | X/Twitter, Instagram, TikTok, Threads, YouTube, Reddit, Mastodon |
  20. | **2 · Blog platforms** | DEV.to, Hashnode, WordPress.com, Micro.blog |
  21. | **3 · Personal sites** | Self-hosted blogs, newsletters, podcasts |
  22. | **5 · Media** | freeCodeCamp News, HackerNoon |
  23. Fetching is polite and read-only: explicit User-Agent, throttled, no anti-bot circumvention.
  24. Some channels work with zero credentials; others need an API key or a logged-in session — the
  25. per-channel requirements are in
  26. [datalayer](skills/influencer-discovery/reference/datalayer/index.md#credentials).
  27. ## Install
  28. No third-party packages, no build step — the pipeline is pure standard library
  29. (Python ≥ 3.11). The skill is fully self-contained under
  30. `skills/influencer-discovery/`; clone and run, or copy that one directory into
  31. your agent's skills folder:
  32. ```bash
  33. git clone https://github.com/tigerless-labs/influencer-discovery && cd influencer-discovery
  34. python3 skills/influencer-discovery/scripts/run.py --help
  35. ```
  36. Credentials go in `~/.config/influencer-discovery/.env`, never in the repo. Pipeline state lives in
  37. `~/.local/share/influencer-discovery/`; both paths are overridable via `INFLUENCER_DISCOVERY_CONFIG_DIR` /
  38. `INFLUENCER_DISCOVERY_STATE_DIR`. Knobs that travel with the code (channel list, throttle parameters,
  39. header mapping) stay in `skills/influencer-discovery/config/`.
  40. ## Run
  41. ```bash
  42. python3 skills/influencer-discovery/scripts/run.py --tiers 1 --per-channel 10
  43. ```
  44. `--channels` / `--tiers` select channels, `--subject` sets the topic gate,
  45. `--min-followers` / `--min-karma` set audience floors. Each run prints a report: planned vs
  46. actual, verdict distribution, and the contactable list.
  47. ### Sheets access
  48. Set `INFLUENCER_DISCOVERY_SPREADSHEET_ID` and authenticate with a short-lived token minted by impersonating
  49. a service account — no long-lived key file on disk. Google blocks adding the `spreadsheets`
  50. scope to plain gcloud ADC ("This app is blocked"), so mint via the `iamcredentials` API:
  51. ```bash
  52. T=$(gcloud auth application-default print-access-token)
  53. curl -s -X POST \
  54. -H "Authorization: Bearer $T" -H "Content-Type: application/json" \
  55. -d '{"scope":["https://www.googleapis.com/auth/spreadsheets"],"lifetime":"3600s"}' \
  56. "https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/YOUR_SA_EMAIL:generateAccessToken"
  57. ```
  58. Prerequisites: the project has the `sheets`, `iam`, and `iamcredentials` APIs enabled; your ADC
  59. identity holds `roles/iam.serviceAccountTokenCreator` on the service account; the service
  60. account can edit the target Sheet. A fresh IAM binding takes ~30s to propagate — a first 403 is
  61. normal, retry.
  62. ## Design invariants
  63. | | |
  64. |---|---|
  65. | **Dedup key is `(person, platform)`** | Checked against a local log; URLs are never parsed for identity — same-site different-person collisions taught us that. |
  66. | **Sheet writes are append-only** | The pipeline creates rows, never edits an existing cell, and aborts if the header row doesn't match its mapping. |
  67. | **Blast radius is one record** | A malformed page or link costs that one person, never the channel or the run; intermediate results are flushed as they are produced. |
  68. | **Hostile-input posture** | Page content is data, not commands — instruction-shaped text in bios and pages is never executed. Every external request leaves through a single read-only choke point. |
  69. | **Contact data never enters the repo** | Real names, emails, and handles live only in the Sheet; `data/` is gitignored end to end. |
  70. ---
  71. © Tigerless · [tigerless.ai](https://tigerless.ai) · [tigerless.com](https://www.tigerless.com)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.