gog-searchconsole

Google Search Console operations through gog.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-searchconsole/SKILL.md

Quality

Content

87%

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

The content is a tight, executable CLI wrapper: concise, copy-paste-ready commands, clear safety gates, and well-structured sections with a single one-level reference. The only gap is an explicit end-to-end workflow with validation feedback loops, which keeps workflow clarity at 2.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows: every line is either an executable command, a safety rule, or a command-purpose row, matching the score-3 anchor of lean and efficient where every token earns its place.	3 / 3
Actionability	The Safe start block gives copy-paste executable `gog` commands and the body routes detail to `--help` and `schema ... --json` for the machine-readable contract, matching the score-3 anchor of fully executable commands with copy-paste-ready guidance.	3 / 3
Workflow Clarity	A safe-start sequence and destructive-op gates (--readonly, --dry-run, confirm account/object/mutation) are present, but there is no explicit end-to-end sequenced task workflow with a validate→fix→retry feedback loop, fitting the score-2 anchor of steps present but checkpoints only implicit.	2 / 3
Progressive Disclosure	At under 50 lines with well-organized sections (Safe start, Commands) and a single clearly signaled one-level reference ("Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules"), this matches the score-3 anchor for short, well-organized skills with no nested references.	3 / 3
	Total	11 / 12 Passed

Description

22%

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 terse and names the right product, but it is too vague to be a strong trigger: it states no concrete actions and gives no explicit "Use when" guidance, leaving both specificity and completeness weak.

Suggestions

List concrete actions in the description, e.g. "Run Search Analytics queries, list and inspect sites, and manage sitemaps in Google Search Console via gog."

Add an explicit trigger clause such as "Use when working with Google Search Console — search performance, sitemaps, or site verification."

Include natural keyword variations (search analytics, sitemaps, sites, SEO performance) so the description triggers on the terms users actually say.

Dimension	Reasoning	Score
Specificity	The phrase "Google Search Console operations through gog" names the domain and tool but uses the abstract word "operations" and lists no concrete actions (query, sitemaps, sites), matching the score-1 anchor for vague/abstract language.	1 / 3
Completeness	It offers only a weak "what" ("operations") and no "when"/"Use when" trigger clause; per the guidelines a missing Use-when clause caps completeness at 2, and the weak what places it at the score-1 anchor (both very weak).	1 / 3
Trigger Term Quality	"Google Search Console" is a natural term a user would say, but "operations" is generic, "gog" is tool jargon, and common variations (search analytics, sitemaps, sites, SEO) are absent, fitting the score-2 anchor of some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	"Google Search Console" is a recognizable niche, but the bare "operations through gog" framing overlaps sibling gog-* skills and does not state distinct triggers, matching the score-2 anchor of somewhat specific but potentially overlapping.	2 / 3
	Total	6 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openclaw/gogcli
Path: .agents/skills/gog-searchconsole/SKILL.md
Commit: 1dbd820

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.