SKILLEMALL.ai
GitHub ↗ RU Sign in

AB google-search-console

When the user wants to analyze Google Search Console data, use GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "title tag," "meta description," "GSC data analysis," "Search Console API," or "searchanalytics.query."

ClawHub Agent Skills author: Kostja Zhang v0.1.0 MIT-0 2 files body ≈ 3 475 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Consistency w 8
40
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ClawHub

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 40Consistency. Frontmatter name (google-search-console) differs from the folder (google-search-console-2)
    • 60Result and completion. Output format stated, no completion criterion
    • 65Failures and branches. 3 branches
    • 70When it triggers. States when to use, but not when not to
    • 85Steps. 57 steps, 2 vague phrases
    • 100Tools and files. No external tools needed
    • 100Execution cost. Instruction body is 3475 tokens
    • 100Running it twice. Mutating operations check current state

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 17 example trigger phrases
    • +3Description length 485: enough signal without eating the budget
    • +4Structure: 27 headings
    • +3Step-by-step instructions: 57 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.

    External checks

    ClawHub: clean
    This is an instruction-only Google Search Console helper with no hidden code or install-time behavior, though users should be mindful when connecting real GSC data.
    LLM: benign (high) · VirusTotal: · 29 May 2026