gog-adsense

Google AdSense 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-adsense/SKILL.md

Quality

Content

75%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 an exemplar of lean, action-oriented skill content with concrete commands and a clean command index, but its write/mutation workflow lacks an explicit validation feedback loop, which caps workflow clarity.

Suggestions

Add an explicit write workflow with a validation checkpoint, e.g. run `--dry-run`, inspect the planned mutation, then execute only if correct, with a re-verify step on failure.

Include one concrete example of a non-trivial read (e.g., a `reports generate` invocation with flags) so the most common operation is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: a short safe-start block, a compact command table, and a one-line pointer to help/schema, with no padding or explanation of concepts Claude already knows; every token earns its place, matching the 5-anchor.	5 / 5
Actionability	It provides concrete, copy-pasteable commands (`gog auth list --check --json --no-input`, `gog schema adsense --json`) and a command table, but actual report-generation or object-mutation examples are deferred to `--help`/schema rather than shown inline, leaving minor gaps versus the fully copy-paste-ready 5-anchor.	4 / 5
Workflow Clarity	The Safe start section gives a sequenced read-only startup flow and explicit pre-write confirmations, but the destructive/batch write path has no validate->fix->retry feedback loop (only a `--dry-run` mention); per the rubric's feedback-loop cap, a destructive skill without validation cannot score above 3.	3 / 5
Progressive Disclosure	Content is well organized into Safe start and Commands sections with one-level-deep pointers to shared rules (`../gog/SKILL.md`) and machine contracts (`gog schema ... --json`), and no bundle files exist to over-structure; it is not a 5 because detailed flag/syntax reference is implicit via --help rather than clearly signaled dedicated references.	4 / 5
	Total	16 / 20 Passed

Description

36%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 distinctive and on-domain but extremely terse: it states only a vague 'what' and provides no concrete actions or 'when to use' trigger guidance, which the rubric penalizes heavily on completeness and specificity.

Suggestions

Add 2-3 concrete capabilities, e.g. 'List ad units and clients, generate reports, review alerts, payments, and policy issues through gog.'

Append an explicit trigger clause such as 'Use when working with Google AdSense accounts, ad units, reports, earnings, or policy issues.'

Mention natural synonyms users say (ads, ad units, earnings, payouts) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description only names the domain ('Google AdSense operations') with the generic verb 'operations' and no concrete actions (e.g., list ad units, generate reports, manage payments), matching the 'names the domain but actions are minimal or generic' anchor and falling well below the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It gives a vague 'what' (AdSense operations through gog) and entirely omits any 'when to use it' clause; the rubric explicitly caps completeness at 3 when a 'Use when...' trigger is missing, and the vague what pushes it down to 2.	2 / 5
Trigger Term Quality	'Google AdSense' is a relevant natural term a user would say, but the phrase lacks common synonyms or variations (e.g., 'ad units', 'reports', 'earnings', 'payouts'), placing it at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Google AdSense operations through gog' is a clear, narrow niche tied to a specific product and tool, with minimal overlap risk against other skills; it is not a 5 only because the brevity leaves the precise trigger scope slightly underspecified.	4 / 5
	Total	11 / 20 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-adsense/SKILL.md
Commit: 29a5adf

Reviewed: 1 day 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.