CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-google

Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, highly actionable command reference with concrete script invocations, a credential-tier model, quota tables, and error-recovery guidance. Its main weaknesses are missing pre-batch validation for outward-facing batch operations and references/scripts that are signaled but not present in the bundle.

Suggestions

Add an explicit validation/confirmation checkpoint before batch operations — e.g., for 'indexing_notify --batch' and 'gsc_inspect --batch', require reviewing the URL list and confirming with the user before submission, which would lift workflow_clarity above the batch cap.

Ensure the referenced bundle files actually exist (references/auth-setup.md, references/api-reference.md, references/rate-limits-quotas.md) and that skills/blog-google/scripts/run.py is shipped, so the signaled navigation resolves instead of dead-ending.

Trim tangential claims such as the '0.737, Ahrefs 75K brands' YouTube correlation and the E-E-A-T explanatory sentence, or move them into a reference file, to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is largely an efficient command reference that assumes Claude's knowledge (no explanation of what PageSpeed/CrUX are), but includes minor trims like 'YouTube mentions have the strongest AI visibility correlation (0.737, Ahrefs 75K brands)' and 'Enhances E-E-A-T scoring for blog content' that are tangential, fitting the efficient-with-minor-over-explanation anchor rather than the lean anchor.

4 / 5

Actionability

Every command ships a copy-paste-ready invocation with flags and batch variants, e.g. 'python3 skills/blog-google/scripts/run.py pagespeed_check <url> --json' and '--batch <file>' forms, matching the fully-executable anchor that covers common cases.

5 / 5

Workflow Clarity

A clear pre-flight validation exists ('Always check credentials before running any command: python3 ... google_auth --check --json') plus an Error Handling recovery table, but batch operations ('gsc_inspect --batch <file>', 'indexing_notify --batch <file>') lack an explicit review/confirm checkpoint before the outward-facing batch submission, so the batch-validation cap holds at 3.

3 / 5

Progressive Disclosure

Structure is good with clear sections and well-signaled one-level-deep references ('Read references/auth-setup.md', 'Reference: references/api-reference.md', 'Read references/rate-limits-quotas.md'), but those referenced files and the scripts/ directory are absent from the bundle, so navigation does not fully resolve — a minor organization gap rather than the clean navigation anchor.

4 / 5

Total

16

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is excellent: it enumerates nine concrete Google API capabilities, declares a credential-tier model, and gives an explicit 'Use when' clause with eleven natural trigger phrases. The only minor risk is acknowledged overlap with the sibling claude-seo skill.

DimensionReasoningScore

Specificity

Quotes a comprehensive inventory of concrete capabilities — 'PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner' — matching the anchor for multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

Clearly answers both 'what' (the full capability list plus 'Progressive feature availability based on credential tier') and 'when' ('Use when user says ...' with concrete trigger phrases), matching the anchor that requires explicit what AND when with concrete triggers.

5 / 5

Trigger Term Quality

The explicit 'Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup"' provides comprehensive natural-term coverage including synonyms and acronyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The 'Google API integration for blog performance' niche with distinct Google-API triggers is mostly distinct, but the stated 'Shares config with claude-seo at ~/.config/claude-seo/google-api.json' signals a minor overlap risk with that closely related skill, keeping it just below the minimal-conflict anchor.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository
AgriciDaniel/claude-blog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.