spytrend-website-review
Skill30 starsChanged 3 months agoMITView on GitHub
Review one website or store domain with SpyTrend MCP data: monthly traffic estimate, advertising footprint over time, which advertiser pages run ads to it and its leading creatives, from a database of 1B+ tracked Meta ads. Use when the user gives a domain or URL and wants its traffic, whether and since when it runs ads, who sends paid traffic to it, or how its ad volume changed month by month. Triggers: "store spy", "does this site run ads", "how much traffic does this store get", "check this domain: traffic, ads, creatives", "competitor website traffic"; RU «крутит ли домен рекламу», «сколько трафика у сайта», «спай магазина». Use this instead of guessing about a specific site's ads or traffic. Not for discovering new stores (use spytrend-shop-discovery), whole niches (use spytrend-vertical-intel) or the operation behind the ads (use spytrend-webmaster-overview).
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-webmaster-overviewSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
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. State explicit seed limits, profile cap, media count and worst-case spend.
- Distinctive: line 28
Default media to off. Do not download or inspect the website itself.
- Very specific: line 32
Call search_shops with the domain, optional selected country and a small explicit limit.
- Very specific: line 35
Call get_shop for the primary returned surface.
- Very specific: line 45
Call search_webmasters by exact domain with optional selected countries and a small limit.
- Very specific: line 48
Call one bounded search_ads seed page per selected surface with landing_domain_exact=true and optional selected country.
- Distinctive: line 72
Keep Markdown and HTML sections equivalent: website snapshot, traffic period and quality, advertising volume, advertisers, networks, …
- Very specific: line 77
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 website advertising review
Read references/spytrend-contract.md before making any data call.
Normalize and preflight
- Accept one domain, remove scheme, path and leading
www, and preserve the user's exact input as context. Reject credentials and IP-literal targets. - Call
get_usage. State explicit seed limits, profile cap, media count and worst-case spend. - Default media to off. Do not download or inspect the website itself.
Workflow
- Call
search_shopswith the domain, optional selectedcountryand a small explicit limit. Match the exact host or registrable root deliberately and state which scope was selected. - Call
get_shopfor the primary returned surface. Extract only bounded public fields. Traffic history is a monthly estimate for its stated month. - Label
ads_monthlyas ads first discovered by SpyTrend. It is not a Facebook launch series. Mark the open current month incomplete. - For a closed launch window, call
search_adswithlanding_domain,landing_domain_exact=true, optional selectedcountry, concrete dates and a one-row limit, then usepagination.totalonly with its date-axis and total status. If launch-period analytics are unavailable, say so; do not substitute the discovery series. - Call
search_webmastersby exact domain with optional selectedcountriesand a small limit; present matches as observed advertising-network attribution, not ownership. - Call one bounded
search_adsseed page per selected surface withlanding_domain_exact=trueand optional selectedcountry. Use its total for volume and its returned rows only to discover advertiser candidates. Cap advertiser cards, callget_advertiserfor only those unique ids, and report processed-versus-seen coverage. A card without acard_statusfield is complete;card_status=buildingmeans the card is a placeholder whose counters are unavailable, not zero. - For website-scoped creative reuse, call
search_adsagain with the exact domain/country/date filters andsort_by=most_reused_creative, using a small selection: on a high-volume domain this ranking exceeds the analytics deadline and returns a timeout instead of rows. Always pair it with a concrete date window, and add the selected country when the domain is large; widen only if the bounded call returned rows. Report the bound you used. Also treat the two reuse counters as separate measurements: whensame_creative_ads_in_selectionexceedssame_creative_ads_lifetime, report both as returned and do not present the pair as a subset relation. explicit limit. Its representative ads and selection reuse counts are the website-scoped ranking. Do not substitute a country-globalsearch_creativespage or re-sort a bounded lifetime list. - With confirmation, retrieve media once for the selected representative ad ids and reuse it in every report section.
Report
Keep Markdown and HTML sections equivalent: website snapshot, traffic period and quality, advertising volume, advertisers, networks, creative leaders, coverage, period-axis notes and spend. A different landing domain is a returned fact, not proof that businesses are unrelated.
Use references/report-template.md or the packaged renderer with
references/report-template.html; otherwise provide the full 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.

