Borrowing it
Nothing to install: this file belongs to FlorianBruniaux/google-search-console-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FlorianBruniaux/google-search-console-mcp/main/.claude/skills/schema-audit/SKILL.mdgit clone --depth 1 https://github.com/FlorianBruniaux/google-search-console-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/schema-audit)<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/schema-audit"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/schema-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/florianbruniaux/google-search-console-mcp/schema-audit"><img src="https://agentmods.dev/badge/skills/florianbruniaux/google-search-console-mcp/schema-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00092 | $0.00400 |
| Opus 5 | $0.00046 | $0.00200 |
| Sonnet 5 | $0.00018 | $0.00080 |
| Haiku 4.5 | $0.00009 | $0.00040 |
Grade A, and why
schema-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Schema Audit
Validate structured data on the site's most-visible pages to find errors that block rich results eligibility.
Steps
- Call
list_propertiesto confirm thesite_url. - Call
get_search_analyticswithdimensions=page,sort_by=impressions,row_limit=20to get the top 20 pages by impression volume. - For each page URL, call
schema_validateto check structured data validity. - Categorize results:
- Valid: schema present and error-free
- Warnings: schema present with non-critical issues
- Errors: schema present but invalid (blocks rich results)
- No schema: no structured data detected on the page
- Prioritize errors and missing schema on pages with the highest impressions.
Output format
Summary line: X valid / Y warnings / Z errors / W no-schema out of 20 pages.
Issues table: Page URL | Schema type | Status | Issue | Impressions
Prioritized fixes:
- Critical: errors on high-traffic pages blocking rich results
- High: missing schema on pages where rich results would apply (Article, Product, FAQ, Review)
- Medium: warnings reducing rich result quality
- Low: pages with no schema and low traffic
For each fix, specify which schema type to add or correct and which properties are required.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 40 lines · 92 tokens per session scan A d82ee6e49c73
schema-audit is a skill published in the GitHub repository FlorianBruniaux/google-search-console-mcp (10 stars, last pushed 9d ago), licensed MIT. It adds 92 tokens to every session and 400 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gsccli
Use when the user wants to query Google Search Console search analytics (clicks/impressions/CTR/position by query/page/country/device), inspect URL indexing status, manage sitemaps, or send Indexing API notifications via the gsccli shell command. Triggers on GSC, Search Console, sitemap, indexing API, mobile…
web-analytics
Analyze web traffic, SEO performance, and search engine trends using Google Search Console, Google Analytics 4, and Bing Webmaster Tools. Use when the user asks to analyze traffic, check SEO, or find keyword opportunities.
seo-mcp-reports
Generate professional, visually stunning SEO reports using SEO-MCP tools. Use when generating HTML/PDF SEO reports with charts, metric cards, gradient headers, and agency-quality styling. Covers weekly, monthly, quarterly, technical audit, competitive analysis, and client-friendly agency report formats. Requires…
seo
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, keyword research, competitors, backlinks, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data…
bot-traffic-detection
Identify and exclude bot, scraper, and spam sessions from GA4 data.
featured-snippet-optimizer
Use when you want to win a featured snippet for a keyword you already rank for. The agent checks the current snippet format, analyzes your content, and rewrites the relevant section to match what Google wants.