agentleFS
xhoantranxhoantran/scrapeio-agent/skills/creator-vetting/SKILL.md

creator-vetting

Skill66 starsChanged 6 days agoMITView on GitHub

Check whether a creator or influencer account is worth paying, by spotting fake followers, bought engagement, inactive audiences and brand-safety issues on TikTok, Instagram and YouTube. Use before a sponsorship, a UGC deal or a partnership. Uses the ScrapeIO API.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    With the scrapeio MCP server: use the named tool when it exists (for example tiktok_profile).

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Creator vetting

Give a clear yes, no or "ask for more data" on one creator, with the evidence.

Steps

  1. Profile: tiktok_profile, instagram_profile or youtube_channel with the handle.
  2. Last 20 to 30 posts: tiktok_profile_videos, instagram_user_posts or youtube_channel_videos. Page once if the first page has fewer than 20.
  3. Compute:
    • median plays and view rate (median plays / followers). Healthy short-video accounts are usually above 5%; under 1% is a red flag.
    • engagement rate (likes + comments) / plays. Very high likes with very few comments suggests bought likes.
    • spread: one viral post and the rest flat means the follower count overstates reach. Report the median, not the mean.
    • posting cadence and the date of the last post.
    • share of posts marked is_ad, if present.
  4. Comment sample: pull comments on 2 recent posts (tiktok_comments, instagram_comments, youtube_comments, by url). Look for generic bot comments ("nice", emoji only, repeated text from many accounts) and for what the audience actually talks about.
  5. Brand safety: skim captions and transcripts of the 5 most viewed posts (tiktok_transcript, instagram_transcript, youtube_transcript) for topics the brand would not want.
  6. Optional, TikTok only: /v1/tiktok/user/audience (handle) returns audience demographics; it costs up to 26 credits, so ask first.

Output

Verdict first (Go, No go, or Ask for their analytics), then a short evidence table: followers, median plays, view rate, engagement rate, comment quality, last post, red flags. Link the posts you looked at.

Cost

About 5 to 8 credits per creator, plus up to 26 for audience demographics.

How to call ScrapeIO

Needs SCRAPEIO_API_KEY. If it is missing, ask the user to get a free key at https://scrapeio.com/login (100 credits, no card). Never print the key.

  • With the scrapeio MCP server: use the named tool when it exists (for example tiktok_profile). For any other path, use call_endpoint with { "path": "/v1/...", "params": { ... } }.
  • Without MCP: curl -s "https://scrapeio.com<path>?<params>" -H "x-api-key: $SCRAPEIO_API_KEY".
  • Answers are in data; lists are data.items with data.cursor and data.has_more. Fields are the same on every platform: handle, followers, plays, likes, comments, shares, created_at, url.
  • 403 (private) and 404 (not found) are free: skip and move on. Retry 502 once. 402 means the user needs credits (https://scrapeio.com/pricing).
  • Watch credits_remaining and tell the user before a step would spend more than they expect.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.