mention-monitor
Skill17 starsChanged 7 months agoMITView on GitHub
Monitor brand mentions across all platforms, reply within 2-4 hours, categorize by sentiment and priority, and log unanswered mentions for follow-up.
- Reads credentials
In this repository40 other files it gives its agents.
- ab-test-analyzeSkill
- metrics-trackSkill
- performance-reportSkill
- caption-draftSkill
- cta-craftSkill
- hook-writeSkill
- post-createSkill
- thread-createSkill
- apology-draftSkill
- crisis-respondSkill
- impersonator-monitorSkill
- comment-replySkill
- dm-respondSkill
- engagement-pollSkill
- influencer-outreachSkill
- cadence-timingSkill
- content-calendarSkill
- presence-refreshSkill
- profile-auditSkill
- cross-post-adaptSkill
- draft-reviewSkill
- schedule-queueSkill
- thread-structureSkill
- blog-to-threadSkill
- newsletter-to-postsSkill
- podcast-to-clipsSkill
- competitor-content-auditSkill
- prospect-social-auditSkill
- social-profile-discoverSkill
- brand-voice-systemSkill
- content-pillarsSkill
- crm-social-bridgeSkill
- positioning-statementSkill
- news-responseSkill
- trending-briefingSkill
- trend-monitorSkill
- asset-formatSkill
- image-promptSkill
- meme-createSkill
- visual-planSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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 30
After a high-performing post goes out (mention volume spikes)
- Distinctive: line 60
Check all direct @mentions
- Distinctive: line 61
Search for untagged brand name references
- Distinctive: line 103
All direct @mentions are categorized and replied to
- Distinctive: line 111
Only monitoring @tags and missing untagged references
- Distinctive: line 114
Not noticing a complaint until it's viral
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Mention Monitor
Track every time the brand is mentioned across platforms and ensure nothing goes unanswered. A thanked mention builds community. An ignored mention signals the brand doesn't care.
Purpose
Brand mentions are free attention. Ignoring them is leaving social capital on the table. This skill ensures every mention is seen, categorized, and responded to within the appropriate timeframe.
When to Use
- Daily monitoring routine
- After a high-performing post goes out (mention volume spikes)
- Post-launch or campaign period
- Weekly mention audit
Inputs Required
- Brand handle(s) and keywords to monitor
- Access to each platform's notification/mention feed
- Response time targets
Quick Reference
| Mention Type | Priority | Response Time | Action |
| Direct tag/shoutout | High | Within 2 hours | Thank + add value |
| Question about product | Critical | Within 1 hour | Answer directly |
| Complaint / negative | Critical | Within 1 hour | Acknowledge, route if needed |
| Share / repost | Medium | Within 4 hours | Thank individually |
| Casual reference (untagged) | Low | Within 24 hours | Engage if natural |
| Competitor comparison | Medium | Within 4 hours | Monitor; engage only if factual correction needed |
Procedure
- Set up mention detection:
- X: @handle tags + brand name keyword searches
- LinkedIn: @company mentions + post tags
- Instagram: @handle tags in captions, comments, stories
- TikTok: @handle tags + brand name in video text/captions
- Daily sweep (morning + afternoon):
- Check all direct @mentions
- Search for untagged brand name references
- Check quote tweets
- Review story mentions (IG/TikTok)
- Categorize each mention using the Quick Reference table.
- Draft responses:
- Shoutout: "Appreciate you sharing this [name/context]" + follow-up thought
- Question: answer thoroughly, link to resource if available
- Complaint: acknowledge, express willingness to help, route to appropriate channel
- Share: "Thanks for spreading the word" + reference something specific about their share
- Track mention metrics:
- Total mentions per day
- Positive/neutral/negative ratio
- Response rate (within target time)
- Unanswered mentions
Output Format
# Mention Monitor: [Date]
## Mentions Today
| Time | Platform | User | Type | Content (truncated) | Priority | Response | Status |
|------|----------|------|------|--------------------|----------|----------|--------|
| 9:15 | X | @user | Shoutout | "[text]" | High | "[reply]" | Replied |
...
## Unanswered (Flagged)
[Any that couldn't be resolved — why?]
## Weekly Summary
- Total mentions: [N] | Response rate: [N]%
- Avg response time: [N] hours
- Sentiment: Positive [N]% / Neutral [N]% / Negative [N]%
- Top mentioners: @handle1, @handle2...Done Criteria
The skill is complete when:
- All direct @mentions are categorized and replied to
- Untagged references are noted (engagement decision made)
- High-priority mentions responded within target time
- Unanswered mentions flagged with reason
- Weekly summary compiled (if end of week)
Pitfalls
- Only monitoring @tags and missing untagged references
- Generic "thanks!" replies to every mention
- Engaging with competitor negative comparisons
- Not noticing a complaint until it's viral
- Responding to a 3-day-old mention (looks like catching up)
Verification
Are there mentions from the last 24 hours that went unanswered? Is the response rate above 90% for high-priority? If not, adjust monitoring frequency or templates.
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.

