CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-adsense

Google AdSense through gog. Use for AdSense accounts, sites, payments, and earnings reports.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A lean, well-structured CLI-wrapper skill: executable safe-start commands, explicit safety gates for writes, and a clean command inventory that defers flag details to --help and machine-readable schemas. The only gaps are the absence of a worked operation example and any error-recovery guidance.

DimensionReasoningScore

Conciseness

Every line is operational — safe-start commands, safety bullets, and a compact command table — with zero concept explanations or padding. Fully matches the "lean and efficient; every token earns its place" anchor.

5 / 5

Actionability

The safe-start block ("gog auth list --check --json --no-input", "gog schema adsense --json", "gog --readonly --account user@example.com adsense --help") is copy-paste executable and the table covers the full command set. Not 5 because no worked example of a real operation (e.g., a reports invocation with flags) is shown; the skill defers entirely to --help and schema discovery.

4 / 5

Workflow Clarity

The safe-start sequence and safety rules form a clear order with real checkpoints (auth --check, --readonly, --dry-run, "Confirm the exact account, object, and mutation before any write or delete"), so the destructive-operation cap does not apply. Not 5 because there is no error-recovery feedback loop, e.g., what to do when the auth check fails.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and no need for bundle files; its single reference ("Read ../gog/SKILL.md first") is one level deep and clearly signaled at the top. Per the simple-skill guideline this matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

73%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.

A concise, distinctive description with an explicit "Use for..." trigger clause and natural AdSense terminology. Its main weakness is that it lists objects rather than actions, leaving the "what" thin on concrete capabilities.

Suggestions

Replace the bare object list with concrete actions, e.g. "List and manage AdSense accounts, sites, ad units, and payments; generate earnings and performance reports."

Add natural trigger synonyms such as "ad revenue", "payouts", or "AdSense monetization" so the description fires on the varied phrasings users actually say.

DimensionReasoningScore

Specificity

Names the domain and tool ("Google AdSense through gog") and enumerates concrete object areas ("accounts, sites, payments, and earnings reports"), but contains no action verbs, so coverage is stated as objects rather than specific actions. Fits anchor 3 rather than 4 because no concrete actions are listed, and above 2 because the enumeration goes beyond minimal/generic.

3 / 5

Completeness

Both parts are present: "what" via "Google AdSense through gog" plus the object list, and an explicit "when" via "Use for AdSense accounts, sites, payments, and earnings reports". Not 5 because the "what" omits actions and the "when" repeats the object list instead of offering varied, concrete trigger phrases.

4 / 5

Trigger Term Quality

"AdSense", "accounts", "sites", "payments", and "earnings reports" are phrases users would naturally say when needing this skill. Not 5 because common synonyms and variations like "ad revenue", "payouts", or "monetization" are missing.

4 / 5

Distinctiveness Conflict Risk

Every trigger mentions "AdSense", a distinct Google product, giving a clear niche with minimal conflict risk even against sibling gog skills. Matches anchor 5: clear niche with distinct triggers.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-adsense/SKILL.md

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.