creator-analytics
Skill7 starsChanged 5 months agoMITView on GitHub
Analyze a creator/account on any supported platform — profile stats, recent post performance, engagement rate, posting cadence, and top content. Use when the user says "analyze this creator/account/channel", "how is @handle doing", "engagement rate", or wants a performance summary for a profile.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tomlen045/media-agent-skillstheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tomlen045/media-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- bulk-data-exportSkill
- comments-analysisSkill
- competitor-analysisSkill
- douyinSkill
- hashtag-researchSkill
- instagramSkill
- social-listeningSkill
- social-media-downloaderSkill
- tikhub-endpoint-discoverySkill
- tikhub-mcpSkill
- tikhub-onboardingSkill
- tikhub-python-sdkSkill
- tikhub-rest-apiSkill
- tiktokSkill
- trend-researchSkill
- twitter-threadsSkill
- xiaohongshuSkill
- youtubeSkill
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
- Very specific: line 36
Use tikhub-find-endpoint "user info" --platform <slug> and "user posts" --platform <slug>, or the platform skill: tiktok, douyin, …
≈ “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.
Files
Creator Analytics
Profile a single account and summarize its performance. For comparing multiple accounts, use
competitor-analysis.
Setup gate
[ -z "${TIKHUB_API_KEY:-}" ] && echo "Set TIKHUB_API_KEY first (see tikhub-onboarding)."Workflow
- Identify platform + handle from the user's input (URL or @handle).
- Resolve the user to the id the API needs (e.g. TikTok/Douyin
sec_user_idviahandler_user_profile; Twitterscreen_name/rest_id; Instagramusername). See the platform skill for the exact endpoint. - Fetch the profile (followers, following, total likes/posts, bio) — the user-info endpoint.
- Fetch recent posts (e.g. last 30–100) via the user's post-list endpoint, paginating with the platform's cursor. Cap the page count and tell the user the cost.
- Compute metrics from the posts:
- Engagement rate ≈ avg(likes + comments + shares) / followers.
- Posting cadence (posts/week from timestamps).
- Top 5 posts by engagement; median vs. top performance.
- Trend over time (rising/declining views).
- Deliver a concise report: headline stats, engagement rate, cadence, top content, and 2–3 observations.
Endpoint pointers (per platform)
Use tikhub-find-endpoint "user info" --platform <slug> and "user posts" --platform <slug>, or
the platform skill: tiktok, douyin, instagram, youtube, twitter-threads, xiaohongshu.
Cost awareness
Profile = 1 call; each page of posts = 1 call. Estimate before running:
GET /api/v1/tikhub/user/calculate_price?endpoint=<path>&request_per_day=<n>. Warn the user
before pulling many pages.
Verification gate
- Profile resolved (non-empty follower/post counts).
- Post list non-empty and timestamps parse.
- Engagement math sanity-checked (rates between 0–100%).
Red flags
- Reporting an engagement rate from too few posts — note the sample size.
- Forgetting to resolve
sec_user_id/numeric id before the post-list call.
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
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.

