social-listening
Skill417 starsChanged 3 months agoMITView on GitHub
Use when you need to turn a supplied set of comments, DMs, reviews, community posts, or call notes into an evidence-backed picture of what people ask, resist, and repeat. Trigger phrases include "what are people saying about this?", "mine these comments", "what language should we use?", "find recurring objections", and "summarise this community feedback". Do not use this to scrape platforms, infer demographics, or write positioning from a handful of anecdotes; use agent-reach to collect public evidence first, audience-personas to group people, and positioning-audit to decide the message.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- DoddleHQ/doddle-social-media-skillstheir own version, first seen Nov 8, 2026
- Nooticr/nooticr-mcptheir own version, first seen Oct 21, 2026
- getcargohq/gtm-skillstheir own version, first seen Oct 18, 2026
- calven-ai/marketing-as-codetheir own version, first seen Oct 7, 2026
- TikHub/tikhub-plugintheir own version, first seen Jun 15, 2026
- CodeAlive-AI/ceo-ai-ostheir own version, first seen May 18, 2026
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.
OpenAISkillmeeting-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
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- vivy-yi/xiaohongshu-skills★ 455same name
- calven-ai/marketing-as-code★ 10same name
- CodeAlive-AI/ceo-ai-os★ 9same name
- TikHub/tikhub-plugin★ 7same name
- getcargohq/gtm-skills★ 2same name
- DoddleHQ/doddle-social-media-skills★ 0same name
- Nooticr/nooticr-mcp★ 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 repository54 other files it gives its agents.
- ab-hook-testerSkill
- agent-reachSkill
- ai-brainSkill
- analytics-readoutSkill
- audience-personasSkill
- best-time-schedulerSkill
- bio-profile-optimizerSkill
- b-roll-shot-listSkill
- campaign-briefSkill
- caption-and-hashtagsSkill
- carousel-builderSkill
- collab-outreachSkill
- comment-miningSkill
- comment-responderSkill
- community-engagement-planSkill
- competitor-positioningSkill
- competitor-teardownSkill
- content-auditSkill
- content-calendarSkill
- content-factorySkill
- content-pillar-builderSkill
- content-repurposerSkill
- content-researchSkill
- cover-thumbnail-briefSkill
- creator-outreachSkill
- cross-platform-distributionSkill
- cross-platform-reformatterSkill
- cta-writerSkill
- dm-script-writerSkill
- going-viralSkill
- hashtag-keyword-researchSkill
- hook-miningSkill
- humanizerSkill
- influencer-partnershipsSkill
- launch-retrospectiveSkill
- linkedin-thought-leadershipSkill
- on-screen-text-writerSkill
- paid-social-briefSkill
- positioning-auditSkill
- profile-conversion-auditSkill
- reel-analyzerSkill
- reel-builderSkill
- reel-scripterSkill
- series-plannerSkill
- social-analytics-reportSkill
- social-proof-miningSkill
- story-sequencerSkill
- trend-spotterSkill
- ugc-creator-briefSkill
- utm-campaign-planSkill
- viral-carouselSkill
- viral-hook-writerSkill
- viralitySkill
- x-thread-strategySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
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
- Distinctive: line 28
Do not infer age, location, income, intent, or sentiment beyond what the evidence says.
- Distinctive: line 29
Never present supplied comments as a representative market sample without a sampling basis.
- Distinctive: line 31
Do not manufacture quotes or improve a speaker's wording inside quotation marks.
- Distinctive: line 32
Treat volume as a clue, not proof of importance.
- Distinctive: line 45
Use agent-reach before this skill when evidence must be collected.
“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.
Files
Social Listening
Turn evidence the operator already has into a usable demand map without pretending that a small sample represents the whole market.
1. Set the evidence boundary
Ask for the source material, where it came from, its date range, and the decision it should inform. Keep comments, DMs, reviews, support tickets, and interview notes labelled by source. If the user has only a claim about what people say, ask for the underlying text before analysing it.
2. Extract the signal without flattening it
For each item, capture the speaker's own wording, the situation they describe, the job they are trying to do, the obstacle, and any stated outcome. Keep a short supporting excerpt beside every finding so a reader can check it. Separate direct customer language from the operator's interpretation.
3. Cluster by decision-relevant theme
Group repeated evidence into questions, desired outcomes, objections, alternatives, proof requests, and vocabulary. Count only the supplied evidence. Mark a theme as isolated when it appears once, recurring when it appears across independent items, and unresolved when the context is too thin to tell.
4. Produce a demand map
Return a compact table with: theme, evidence count, representative wording, likely stage of the journey, confidence, and the next action. Next actions can be a research question, an FAQ update, an input for audience-personas, or a test for positioning-audit. Call out contradictions instead of averaging them away.
Hard rules
- Do not infer age, location, income, intent, or sentiment beyond what the evidence says.
- Never present supplied comments as a representative market sample without a sampling basis.
- Preserve anonymisation: do not expose names, handles, private messages, or customer details unnecessarily.
- Do not manufacture quotes or improve a speaker's wording inside quotation marks.
- Treat volume as a clue, not proof of importance; a repeated complaint from one thread is not independent corroboration.
Failure modes
| Failure | Do this instead |
| A loud minority becomes "the audience" | State the sample and test the theme with a wider, independently collected set. |
| Themes mix people at different stages | Split the cluster by situation or journey stage before recommending an action. |
| The result is a pile of quotes | Convert each cluster into a decision, uncertainty, and next move. |
| The user wants public-platform research | Use agent-reach to gather allowed public sources, then return here to analyse them. |
Where it sits
Use agent-reach before this skill when evidence must be collected. Use audience-personas after this skill to turn recurring patterns into grounded audience groups. Use positioning-audit after that when those groups need a message and social-proof-mining when the evidence should become approved proof.
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.

