spytrend-webmaster-overview
Skill30 starsChanged 3 months agoMITView on GitHub
Profile the advertising network behind a domain or a group of ads with SpyTrend MCP data: connected domains, advertiser pages, identifiers tying ads to one operator, target countries and the creatives that operation reuses most, from a database of 1B+ tracked Meta ads. Use when the user wants to know who is behind a set of ads, see everything one operator or competitor runs across pages and domains, or check whether identical ads on different pages belong to one player. Triggers: "ads spy across pages", "who is behind these ads", "everything this operator runs", "the whole operation", "network behind a landing domain"; RU «кто стоит за рекламой этого домена», «какие ещё домены у этого рекламодателя», «вся связка страниц оператора». Not for ranking advertiser pages in a market (use spytrend-advertiser-overview) and not for a website's traffic review (use spytrend-website-review).
In this repository6 other files it gives its agents.
- llms.txtllms.txt
- spytrend-advertiser-overviewSkill
- spytrend-keyword-searchSkill
- spytrend-shop-discoverySkill
- spytrend-vertical-intelSkill
- spytrend-website-reviewSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Read references/spytrend-contract.md before making any data call.
- Very specific: line 26
Call get_usage and disclose the planned depth and media choice.
- Very specific: line 27
If the input is not already a canonical id, call search_webmasters by exact domain or query with a small limit.
- Very specific: line 30
Read market size from pagination.total only with its status.
- Very specific: line 32
Call get_webmaster with the chosen canonical id.
- Very specific: line 43
Call search_creatives with webmaster_id, optional category and sort_by=total_ads for the exact global network slice.
- Very specific: line 47
Call search_ads with webmaster_id, the selected categories and countries, country_match=any, status_today=active, sort_by=date, dedupe=true …
- Distinctive: line 52
If the card contains a network-specific creative slice, use its slice order for "most reused by this network".
- Very specific: line 65
Use references/report-template.md or the packaged renderer with references/report-template.html.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
SpyTrend advertising network overview
Read references/spytrend-contract.md before making any data call. The skill
name preserves the MCP entity name for routing; user-facing output says
"advertising network" or "network".
Resolve one network
- Call
get_usageand disclose the planned depth and media choice. - If the input is not already a canonical id, call
search_webmastersby exact domain or query with a small limit. Show ambiguous candidates and ask the user to choose rather than merging them. - Read market size from
pagination.totalonly with its status. Never read a top-level total and never promise a complete list from a capped response. - Call
get_webmasterwith the chosen canonical id. Ifanalytics_pending=true, treat counters as pending, not zero.
Bounded profile
- Render the returned domains, advertiser pages, the identifiers that tie ads to one operator, and countries with their returned counts, caps and statuses. A missing inventory is unavailable, not proof that no identifier exists.
- Present attribution edges as evidence of observed combinations. A small edge does not prove common ownership, and inherited identifiers do not describe current operation by themselves.
- Call
search_creativeswithwebmaster_id, optional category andsort_by=total_adsfor the exact global network slice. Do not addcountry: the current read path cannot preserve the exact network slice together with that filter. Use returned geo fields as context, not as a country ranking. - Call
search_adswithwebmaster_id, the selectedcategoriesandcountries,country_match=any,status_today=active,sort_by=date,dedupe=trueand a small explicit limit for fresh examples. This means the selected country is present in the ad's known geographies; it does not mean that country is dominant. Label dates according to the returned date axis. - If the card contains a network-specific creative slice, use its slice order for "most reused by this network". Keep market-wide family size as separate context; do not use it to reorder the network slice.
- With confirmation, retrieve media for only the chosen rows. A representative ad is a cheaper placement example; a creative fetch represents the material family. State which path was used.
Report
Include resolution evidence, current/pending status, returned identifier coverage, country activity, creative rankings, fresh examples, period labels and spend. Say "processed N of M" whenever a bounded cap is used.
Use references/report-template.md or the packaged renderer with
references/report-template.html; otherwise return the same report in chat.
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.

