crawlora-org/crawlora-skills

tiktok-creator-research

Vet public TikTok creators through live profile, post, video, comment, and user-search endpoints in Crawlora.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/crawlora-org/crawlora-skills --skill tiktok-creator-research

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

TikTok creator research

Build a current, evidence-backed view of public TikTok creators. Keep identity, content fit, posting activity, and engagement observations separate from claims about audience demographics, authenticity, or partnership history.

Setup and requests

Set CRAWLORA_API_KEY to a key from crawlora.net, then run the helper bundled with this skill. It sends x-api-key to https://api.crawlora.net/api/v1; keep the key in the environment. Read `reference/endpoints.md` for exact parameters.

sh
Set `CRAWLORA_API_KEY` in the environment before running the helper.
scripts/crawlora.sh /tiktok/profile/username | jq '.'
scripts/crawlora.sh /tiktok/search/user keyword="running coach" | jq '.'

Check both the Crawlora envelope and any nested upstream application code before using a response. Keep the key only in CRAWLORA_API_KEY.

Workflow

  1. Translate the brief into topic, geography, follower range if available,

creator count, recency window, content-fit criteria, and any disqualifiers. Ask only for missing details that would change the shortlist.

  1. Discover handles with /tiktok/search/user when needed. Search results are

candidate evidence, not a verified identity or complete creator directory.

  1. Refresh each candidate with /tiktok/profile/{handler} using the handle

without @. Capture the returned stable user id, uniqueId, nickname, verification flag, bio, secUid, follower count, heart count, and video count. A missing/deleted/banned handle is not a successful refresh.

  1. For recent or popular content, pass the profile's returned user.secUid

exactly to /tiktok/posts. Do not substitute the numeric user id, nickname, or handle. Use sort_type=0 for latest, 1 for popular, or 2 for oldest; take a bounded, consistent sample and follow its cursor only as needed.

  1. Use /tiktok/post/{id} to enrich selected videos. Use /tiktok/comments

with the video's aweme_id to sample top-level comments when engagement quality matters. Comments are a sample, not a complete sentiment census.

  1. Rank candidates only against the user's stated criteria. Deduplicate by

stable creator or video id and preserve the refresh time for every row.

Interpretation

  • A profile's follower count, likes, views, and verification status are public

profile signals. None proves audience authenticity, demographic composition, location of followers, or conversion potential.

  • Bio keywords and a small post sample show candidate content fit, not sustained

niche ownership. Record sample size and dates before describing cadence or consistency.

  • If calculating engagement, state the formula, numerator fields, denominator,

sample size, and dates. Do not replace unavailable metrics with zero or rank creators on incomparable windows.

  • Public contacts may be unavailable. Do not guess email addresses or hidden

contact information; do not send outreach unless the user separately asks.

  • Link identities across platforms only when a public profile link or other

direct evidence establishes the match. Similar handles are not proof.

  • If a live refresh fails, a candidate can remain in a clearly labeled

unrefreshed/candidate state; it must not silently become a current observation.

Output and reliability

Return the requested shortlist with handle, stable creator id, profile URL, topic-fit evidence, follower/video counts, verification status, refresh time, sampled video URLs, metric definitions, and unknowns. Include a brief reason for each inclusion and disclose the discovery and sampling limits.

Use bounded profile, post, detail, and comment calls. On 429, back off; retry one transient 5xx when useful. Stop on 401/403 and report the access limitation. Preserve a partial shortlist when only some refreshes succeed, and inspect application-level code before treating data as valid.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
crawlora-org
커뮤니티

amazon-jobs-research

Researches Amazon.jobs postings via the Crawlora API — search Amazon's public careers site by keyword and/or job category, then pull any single posting's full description and qualifications by job id — returning clean JSON. Use when the user wants to search Amazon job openings, browse a specific Amazon job category, or fetch the detail for one Amazon job posting.

설치 수
1
GitHub Stars
0
업데이트
9월 26일
crawlora-org
커뮤니티

amazon-research

Researches products, prices, availability, and search suggestions on Amazon (amazon.com) using the Crawlora API, returning clean JSON. Use when the user asks to find a product on Amazon, look up an ASIN's price/details, or pull Amazon autocomplete/keyword suggestions — instead of scraping Amazon pages.

설치 수
1
GitHub Stars
0
업데이트
9월 26일
crawlora-org
커뮤니티

anime-manga-research

Researches anime and manga titles via the Crawlora API — search, title detail, characters, staff, recommendations, rankings, and airing schedules — returning clean JSON. Use when the user wants an anime/manga's details, cast/staff, similar titles, seasonal rankings, or what's currently airing.

설치 수
1
GitHub Stars
0
업데이트
9월 26일
crawlora-org
커뮤니티

app-market-opportunity-research

Research app-market opportunities using Crawlora app catalogs, historical charts, live store listings, release notes, reviews, and Google Trends. Use for app niche assessments, competitor maps, chart-movement analysis, and evidence-backed unmet-need hypotheses.

설치 수
1
GitHub Stars
0
업데이트
9월 26일