serp-monitor
Skill20 starsChanged 4 days agoMITView on GitHub
Мониторить запросы, CTR и средние позиции сайта в Яндексе через данные Вебмастера; при наличии отдельного SERP-инструмента делать точечные снимки выдачи и конкурентов. Использовать для динамики позиций, сниппетов и поисковых запросов.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-markers-removeSkill
- article-reviserSkill
- article-writerSkill
- avito-adsSkill
- avito-businessSkill
- demand-researchSkill
- export-ad-reportsSkill
- human-editorial-polishSkill
- lidfly-connection-doctorSkill
- lidfly-knowledge-maintainerSkill
- lidfly-page-migrationSkill
- lidfly-site-commerceSkill
- lidfly-support-escalationSkill
- max-postingSkill
- mcp-v3-provider-contextSkill
- restaurant-yandexSkill
- semantic-coreSkill
- seo-optimizerSkill
- serp-monitorSkill
- telegram-postingSkill
- video-article-writerSkill
- vk-ads-campaign-builderSkill
- vk-social-communitySkill
- workspace-project-managerSkill
- yandex-direct-campaign-builderSkill
- yandex-edaSkill
- yandex-metrikaSkill
- yandex-productsSkill
- yandex-webmasterSkill
- youtube-video-seoSkill
- ai-markers-removeSkill
- article-reviserSkill
- article-writerSkill
- avito-adsSkill
- avito-businessSkill
- demand-researchSkill
- export-ad-reportsSkill
- human-editorial-polishSkill
- lidfly-connection-doctorSkill
- lidfly-knowledge-maintainerSkill
- lidfly-page-migrationSkill
- lidfly-site-commerceSkill
- lidfly-support-escalationSkill
- max-postingSkill
- mcp-v3-provider-contextSkill
- restaurant-yandexSkill
- semantic-coreSkill
- seo-optimizerSkill
- telegram-postingSkill
- video-article-writerSkill
- vk-ads-campaign-builderSkill
- vk-social-communitySkill
- workspace-project-managerSkill
- yandex-direct-campaign-builderSkill
- yandex-edaSkill
- yandex-metrikaSkill
- yandex-productsSkill
- yandex-webmasterSkill
- youtube-video-seoSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use for checking a site's Yandex queries, CTR, average positions, snippets, and movement over time.
- Very specific: line 13
Use $yandex-webmaster: start with webmaster_get_hosts, select the exact host_id, then read webmaster_get_popular_queries, …
- Distinctive: line 14
Treat Webmaster positions as aggregated search-performance data, not a point-in-time rank checker.
- Distinctive: line 23
Do not claim stable ranking from one snapshot or average position.
- Distinctive: line 24
Do not infer advertising blocks from Yandex XML/Webmaster organic data.
- Distinctive: line 25
Do not mix organic and paid positions.
≈ “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
SERP Monitor
Use for checking a site's Yandex queries, CTR, average positions, snippets, and movement over time.
Workflow
- Clarify target domain, queries, period, comparison period, and region when the source supports it.
- Use
$yandex-webmaster: start withwebmaster_get_hosts, select the exacthost_id, then readwebmaster_get_popular_queries,webmaster_get_queries_history,webmaster_get_query_history, orwebmaster_query_analyticsas appropriate. - Treat Webmaster positions as aggregated search-performance data, not a point-in-time rank checker.
- For an exact current SERP or competitor snapshot, use only a separately available SERP connector/tool whose schema you can inspect. If none exists, state that the exact snapshot is unavailable; do not reconstruct it from memory or ordinary browser personalization.
- Record source, period/date, query, domain, URL, position metric, CTR, clicks/impressions, and any source limitations.
- Compare against prior verified data only when available.
- Save reports to Workspace through
call_write_toolonly when the user requests that destination and after resolvingworkspace_project_id. Otherwise return the report or use the requested available artifact tool.
Rules
- Mark exact SERP snapshots as point-in-time and Webmaster metrics as period aggregates.
- Do not claim stable ranking from one snapshot or average position.
- Do not infer advertising blocks from Yandex XML/Webmaster organic data.
- Do not mix organic and paid positions.
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.

