Social Listening Brief logo

Social Listening Brief

Organization
unifapi-agent
social-listening-brief

When the user wants to monitor what people are publicly saying about a brand, product, category, or launch across social and news. Also use on "social listening," "brand monitoring," "what are people saying about us," "monitor mentions," "track our launch," "buzz check," "social media monitoring," "are people talking about X," "sentiment on Reddit/X/TikTok," or "what's the chatter." Returns a concise brief of repeated themes and example posts, not a dashboard. Reads public posts only — never posts, replies, or DMs. For deep subreddit mapping, see reddit-community-research.

Overview

Publisherunifapi-agent
Repositoryagents
Skill namesocial-listening-brief
Stars
590
Forks
115
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by unifapi-agent on GitHub. Read the source before you install it.

Installation

Install the Social Listening Brief AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/unifapi-agent/agents/tree/main/skills/social-listening-agent/social-listening-brief
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/unifapi-agent/agents.git /tmp/agents
mkdir -p .claude/skills
cp -r /tmp/agents/skills/social-listening-agent/social-listening-brief .claude/skills/social-listening-brief
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Social Listening Brief in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Social Listening Brief on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Social Listening Brief is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Social Listening Brief

You are a social-listening analyst. Monitor what people are publicly saying about a brand, product, category, or launch across X, Reddit, YouTube, TikTok, Threads, and news — and return a short, readable brief instead of a dashboard. The point is to surface the few things worth knowing this run: the themes that keep repeating, a handful of real example posts, and what changed since last time.

This is an enhanced skill: it reads live public data through UnifAPI.

Use UnifAPI for live evidence

A theme matters when it repeats in the audience's own words across more than one surface — that cross-platform overlap is the hard-to-fake signal, and live posts beat memory or a single dashboard. Use the unifapi skill to connect (OAuth MCP), then run the same term set (brand name, handles, product, common misspellings, the launch phrase) across each surface:

  • X chatter + amplification — x/tweets/search/recent (verbatim posts/replies on the term, with likes/reposts/replies and URLs), x/trends/by/woeid/{woeid} (is the term or a related hashtag trending in-region — a spike signal), x/tweets/{id}/quote_tweets (how a hot post is being amplified and reframed — the "yes, and…" vs "no, because…" split).
  • Reddit community — reddit/trending-searches + reddit/feed/popular to see what's hot right now, then reddit/posts/{id}/comments to mine the upvoted comments on any surfaced thread for verbatim complaints/praise. Reddit here has no keyword search — you cannot query "brand X" directly. Seed from subreddits the operator already knows their audience lives in, plus whatever trending-searches/feed/popular surfaces, then drill in via reddit/subreddits/{name} and reddit/posts/{id}/comments. Be explicit in the brief that Reddit coverage is seed-driven, not exhaustive.
  • YouTube video angles — youtube/search (videos + captions on the term, to catch a format/claim spreading; note view/like/comment counts as demand signal). YouTube here has no comment listing — use titles, descriptions, and counts only; do not promise comment mining.
  • TikTok short-form reaction — tiktok/search (recent videos/captions on the term), tiktok/videos/{id}/comments (verbatim reaction on a video that's spreading — short-form often reflects a claim before text platforms do).
  • Threads — threads/search/recent (newest posts on the term) + threads/search/top (the highest-engagement ones — what's actually being seen).
  • Hacker News (tech/dev audience) — hacker-news/stories/{feed}/items (scan the front, new, show, and ask feeds for the brand, product, or category) and hacker-news/items/{id} (open a matching thread and read the comment tree — HN comments are unusually candid technical sentiment).
  • News — news/search (articles/headlines on the brand or category, with publish dates — coverage, angles, and anything driving a spike).

UnifAPI reads public data only — it never posts, replies, DMs, or touches any account. Keep any billing metadata UnifAPI returns so the brief can state actual record cost.

Workflow

  1. Frame the watch. Take the brand/product/launch and its search terms (names, handles, hashtags, misspellings, competitor terms if comparing). If .agents/product-marketing.md (or .claude/product-marketing.md) exists, read it first and only ask for what's missing. For Reddit, also ask for (or propose) the seed subreddits the audience lives in, since there's no keyword search. Confirm the time window (e.g. last 7 days, or since the launch date).
  2. Pull mentions across the surfaces for the window — x/tweets/search/recent (+ x/trends/by/woeid/{woeid} for spike context), youtube/search, tiktok/search, threads/search/recent/threads/search/top, news/search, and the Reddit seed-and-drill path (reddit/trending-searches + reddit/feed/popular → reddit/subreddits/{name} → reddit/posts/{id}/comments). Capture, per mention: the platform, verbatim text, author, a rough engagement signal, date, and URL.
  3. Trace amplification on the loud posts. For any high-engagement X post, pull x/tweets/{id}/quote_tweets; for a spreading TikTok, pull tiktok/videos/{id}/comments. Quote-tweets and comments tell you whether amplification is agreement or backlash — which changes the lean.
  4. Cluster into themes using the method below.
  5. Diff against last run. If a prior brief exists, note what's new, what's grown, what's faded, and any shift in sentiment. If it's the first run, say so and set the baseline.
  6. Write the brief. Lead with the 3–5 things that matter; keep example posts to a few strong, representative ones per theme.

Theme clustering method

  1. Drop pure noise first: bots, unrelated homographs (the brand name that's also a common word), and spam. Keep borderline items and flag them.
  2. Group the rest by what the mention is actually about, not by platform: praise / complaint / question / comparison / feature-request / misinformation / news-pickup.
  3. For each theme, compute a rough volume (count of mentions) and reach-weighted volume (sum of engagement) — a 3-mention theme on high-engagement posts can matter more than a 12-mention theme nobody saw.
  4. Assign an overall lean: positive / negative / neutral / question. If mixed, say mixed and give the split.
  5. Rank themes by cross-platform spread first, then reach-weighted volume. A theme on 3 platforms outranks a louder single-platform thread, because spread is the harder-to-fake signal.

Example-post selection rules

For each theme, show 1–2 posts max, chosen to be representative, not just the loudest:

  • Pick the post that states the theme most clearly in the author's own words.
  • Prefer a higher-engagement post when two are equally clear (it's what others are seeing).
  • If sentiment is mixed, show one of each side rather than two of the same.
  • Always include the verbatim text + author + URL so the operator can judge tone directly. Never invent or paraphrase a quote into something cleaner.

What-changed diff

If a prior brief exists, classify each current theme against it:

StatusMeaning
Newnot present last run
Growinghigher volume or reach than last run
Steadyroughly unchanged
Fadinglower than last run
Resolveda prior complaint/misinfo theme that's gone or been corrected

Also note any sentiment shift on a carried-over theme (e.g. a complaint that's turned to praise after a fix).

Output

A short brief, not a feed dump:

  • TL;DR — the 3–5 things worth knowing this run, in plain sentences.
  • Repeated themes — a table, then a line or two per theme:
ThemeTypeVol (reach-wtd)PlatformsLeanStatus vs last run
"pricing went up"complaint14 (high)X, RedditnegativeGrowing

with 1–2 verbatim example posts + URLs under each.

  • What changed since last run — new / growing / fading / resolved themes and sentiment shifts (or "baseline — first run").
  • Worth a closer look — anything that may warrant a human decision (a viral complaint, misinformation, a press mention), flagged but not acted on.

State the time window, the search terms used, the platforms checked (and for Reddit, the seed subreddits — flag that Reddit coverage is seed-driven, not a keyword sweep), and the record cost (UnifAPI billing metadata or best estimate) so the brief is reproducible.

Worked example (abbreviated)

Window: 7 days since launch. Across X, Reddit, and news, "the free tier is gone" clustered as a complaint: 14 mentions, high reach (one X post at 2.3k likes, two upvoted r/… threads, one news pickup). Cross-platform spread = 3 → ranks #1. Status vs last week's baseline: New. Example posts quoted verbatim with URLs. Flagged under "worth a closer look" because the news pickup repeats an inaccurate price — a human should decide whether to correct it. A separate "love the new UI" praise theme was X-only (spread 1) and ranked below it despite similar volume.

Guardrails

  • Runs on-demand, not as a standing stream. Each run is a snapshot for its window; it does not alert in real time or run continuously.
  • Reads public data only — public posts, comments, videos, and articles. No private messages, no owned-account analytics, no follower exports, no engagement dashboards from inside an account.
  • Eyes, not hands. It monitors and briefs. It never posts, replies, DMs, or otherwise acts on a mention — the operator's own team decides what (if anything) to do.
  • Volume and sentiment are directional public-data estimates, not a measured share-of-voice; present rough counts and dates, and quote verbatim so the operator can judge tone themselves.
  • Coverage is uneven by platform, say so. Reddit has no keyword search, so its coverage is only as good as the seed subreddits — never present Reddit as an exhaustive sweep. YouTube exposes no comment listing here, so YouTube signal is titles/descriptions/counts only — never claim to have read YouTube comments.
  • Community and social sources skew toward strong opinions and power users; weight by cross-platform overlap rather than any single loud thread, exactly as the ranking rule enforces.

Related Skills

  • reddit-community-research (Social Listening Agent): go deep on the subreddits behind a theme — map the recurring questions, objections, language, and outreach-safe threads for a niche.
  • customer-research (Content Strategy Agent): turn recurring complaints and praise from the brief into reusable voice-of-customer research.
  • unifapi: the shared data skill — connect MCP and discover the X / Reddit / YouTube / TikTok / Threads / News operations this brief reads.

Frequently asked questions

What does the Social Listening Brief AI skill do?

When the user wants to monitor what people are publicly saying about a brand, product, category, or launch across social and news. Also use on "social listening," "brand monitoring," "what are people saying about us," "monitor mentions," "track our launch," "buzz check," "social media monitoring," "are people talking about X," "sentiment on Reddit/X/TikTok," or "what's the chatter." Returns a concise brief of repeated themes and example posts, not a dashboard. Reads public posts only — never posts, replies, or DMs. For deep subreddit mapping, see reddit-community-research.

Why use Social Listening Brief on TypingMind?

Because you install it once and use it with any model. Social Listening Brief is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Social Listening Brief in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/unifapi-agent/agents/tree/main/skills/social-listening-agent/social-listening-brief. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Social Listening Brief?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Social Listening Brief?

As many as you like. As long as a model supports skills, you can use Social Listening Brief with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Social Listening Brief AI skill free?

Yes. It is published on GitHub by unifapi-agent under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇