agentleFS
TikHubTikHub/tikhub-plugin/skills/social-listening/SKILL.md

social-listening

Skill7 starsChanged 5 months agoMITView on GitHub

Monitor what people say about a brand, product, person, or keyword across platforms — collect mentions, classify sentiment, cluster themes, and deliver a cited digest. Use when the user says "what are people saying about X", "monitor mentions", "brand sentiment", "track this keyword", or wants social listening.

  • Reads credentials

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-prep.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every theme/claim in the digest cites a real source URL.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Social Listening

Collect mentions of a brand/keyword across platforms, then analyze sentiment and themes.

Setup gate

[ -z "${TIKHUB_API_KEY:-}" ] && echo "Set TIKHUB_API_KEY first (see tikhub-onboarding)."

Workflow

  1. Define the query: brand/keyword(s), platforms to cover, time window, target volume (e.g. ~100 mentions).
  2. Search each platform using its search endpoint (one query → paginate to the target volume):
    • TikTok app/v3/fetch_video_search_result, Douyin search/fetch_general_search_v2 (POST body), Instagram v2/general_search, Twitter web/fetch_search_timeline, YouTube web_v2/get_general_search, Xiaohongshu app_v2/search_notes.
    • Find exact paths via tikhub-find-endpoint "search" --platform <slug>.
  3. Collect posts/comments into one list (author, text, platform, url, timestamp, engagement).
  4. Classify sentiment (positive / neutral / negative) per mention — reason over the text.
  5. Cluster themes (recurring topics, complaints, praise) and pull representative quotes.
  6. Deliver a digest: volume, sentiment breakdown, top themes with cited example posts (link each claim to a source URL), and 2–3 recommendations.

Cost awareness — IMPORTANT

This is the most call-heavy skill: every search page on every platform is a billed call. State an estimated call count and cost before running (GET /api/v1/tikhub/user/calculate_price?endpoint=<path>&request_per_day=<pages>), cap pages per platform, and check balance with get_user_daily_usage.

Verification gate

  1. Mentions actually match the query (filter false positives).
  2. Every theme/claim in the digest cites a real source URL.
  3. Sentiment labels are justified by the quoted text.

Red flags

  • Unbounded multi-platform pagination — runs up credits fast; always cap and warn.
  • Reporting sentiment without citations.
  • Counting unrelated keyword collisions as mentions.

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.