impersonator-monitor
Skill17 starsChanged 7 months agoMITView on GitHub
Monitor for brand impersonators, fake accounts, and phishing attempts — draft platform report copy and escalation guidance for takedown requests.
- 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
- comment-replySkill
- dm-respondSkill
- engagement-pollSkill
- influencer-outreachSkill
- mention-monitorSkill
- 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
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 33
After viral post (impersonator activity spikes)
- Distinctive: line 55
Search for brand name variations across all platforms
- Distinctive: line 57
Check recent "is this you?" DMs
- Distinctive: line 72
Use impersonation/trademark violation form
- Distinctive: line 74
Follow up if no action after 72 hours for high/critical cases
- Distinctive: line 120
Not doing routine sweeps (only find impersonators after damage done)
- Distinctive: line 122
Not warning audience when active impersonation happening
- Distinctive: line 123
Not following up on platform reports
- Distinctive: line 127
Search for "[brand]" plus "official" / "support" / "help" on each platform.
≈ “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
Impersonator Monitor
Detect and respond to brand impersonation, fake accounts, and phishing attempts. Impersonators erode trust and confuse customers. Fast detection and reporting are critical.
Purpose
Impersonator accounts are inevitable once a brand has any visibility. This skill makes detection systematic — weekly sweeps, customer report intake, and platform takedown procedures — so impersonators are caught before they cause real damage.
When to Use
- Routine weekly sweep for fake accounts
- Customer reports suspicious account
- Spike in "is this you?" DMs
- After viral post (impersonator activity spikes)
- Phishing DMs detected
Inputs Required
- Official brand handles per platform
- Customer contact channels (for reports)
- Platform support contacts
Quick Reference
| Impersonator Type | Risk | Detection | Response |
| Exact handle clone | High | Search for similar handles | Immediate platform report |
| Lookalike account | High | Manual search, follower reports | Report + warn audience if active |
| DM phishing | Critical | Audience reports, inbox monitoring | Report + public warning if widespread |
| Parody/satire | Low-Medium | Platform search | Monitor unless confusing consumers |
| Fake support account | Critical | Customer complaints | Immediate report + legal if needed |
Procedure
- Weekly sweep:
- Search for brand name variations across all platforms
- Google Alerts for "[brand] fake" and "[brand] scam"
- Check recent "is this you?" DMs
- Document each impersonator:
- Platform, handle, URL
- Activity level (dormant, active, scamming)
- Followers count
- Evidence (screenshots)
- Assess severity:
- Low: dormant, no followers. Report and move on.
- Medium: active but distinguishable. Report + monitor.
- High: actively impersonating or messaging customers. Report immediately + public warning.
- Critical: running scams or causing financial harm. Report + warning + legal.
- Draft platform report:
- Use impersonation/trademark violation form
- Provide evidence (screenshots, handle comparison)
- Follow up if no action after 72 hours for high/critical cases
- Post public warning if warranted:
- "Our only official accounts are: [list]. We never DM asking for payment."
- Pin warning for duration of impersonation activity
Output Format
# Impersonator Monitor: [Date]
## Detected
**Platform:** [X / LinkedIn / IG / TikTok]
**Handle:** [Fake handle]
**Severity:** [Low / Medium / High / Critical]
**Activity:** [Dormant / Active / Scamming]
**Followers:** [N]
## Action
- [ ] Platform report filed ([date])
- [ ] Public warning posted ([date/link])
- [ ] Follow-up scheduled (72h for high+)
**Status:** [Reported — awaiting takedown / Resolved / Ongoing]
## Impersonation Log
| Date | Platform | Handle | Severity | Reported | Resolved |
|------|----------|--------|----------|----------|----------|
...
## Patterns
- Most active platform: [Platform]
- Recurrence triggers: [After viral / During launches]Done Criteria
The skill is complete when:
- Weekly sweep is conducted across all active platforms
- Each impersonator is documented (handle, severity, activity)
- Platform reports are filed for high+ severity
- Audience warning posted if impersonator is active
- Impersonation log is updated
Pitfalls
- Not doing routine sweeps (only find impersonators after damage done)
- Engaging directly with impersonators (report, don't argue)
- Not warning audience when active impersonation happening
- Not following up on platform reports
Verification
Search for "[brand]" plus "official" / "support" / "help" on each platform. Any results that aren't yours? Check "is this you?" DMs from last 30 days — any accounts people are confused about?
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.

