CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-sites

Google Sites through gog. Use for finding Google Sites in Drive, reading site metadata, and printing editor URLs; use gog-drive for file sharing.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

An exemplary lean, generated skill body: concrete safe-start commands, a tidy command table, and disciplined delegation of syntax details to `gog --help` and `gog schema`. The only gaps are minor — no worked example of a core command in action and no error-recovery guidance for failed auth or rejected writes.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and efficient: every line is an executable command, a safety rule, or a navigation pointer, with zero explanation of concepts Claude already knows. Matches the anchor-5 example of content where every token earns its place.

5 / 5

Actionability

The Safe start block gives copy-paste-ready commands (`gog auth list --check --json --no-input`, `gog schema sites --json`) and the Commands table maps each subcommand to its purpose. Not a 5 because no example invocations of the core commands (e.g., `gog sites list`) are shown — syntax is delegated to `--help` and `gog schema` instead of illustrated.

4 / 5

Workflow Clarity

A clear ordered sequence (auth check → schema → command help) with validation checkpoints for risky operations (`--check`, `--readonly`, `--dry-run`, "Confirm the exact account, object, and mutation before any write or delete"), so the destructive-operation cap does not apply. Falls short of 5 because there is no error-recovery loop (e.g., what to do when the auth check fails) and the per-command task flow is left implicit.

4 / 5

Progressive Disclosure

A simple skill under 50 lines with well-organized sections and no need for bundle files; per the simple-skill rule this can score 5. The single file reference (`../gog/SKILL.md`) is clearly signaled and one level deep, and detail is delegated to runtime disclosure via `--help` and `gog schema` rather than nested files.

5 / 5

Total

18

/

20

Passed

Description

78%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 strong description that names a clear niche, lists three concrete capabilities, includes an explicit "Use for" trigger clause, and even disambiguates a sibling skill. The main improvement room is in trigger phrasing: adding user-voice variants ("when the user asks about a Google Site") would push completeness and trigger quality to the top anchor.

Suggestions

Add user-voice trigger phrasing (e.g., "Use when the user asks about a Google Site, wants its editor URL, or mentions Sites in Drive") to raise completeness and trigger_term_quality.

Include a synonym-level term such as "Google Sites website" or "site link" alongside "Google Sites" for broader natural-keyword coverage.

DimensionReasoningScore

Specificity

Lists three concrete actions — "finding Google Sites in Drive", "reading site metadata", "printing editor URLs" — that map onto the skill's get/list/search/url commands. Not a 5 because the actions are stated tersely and nuances like search-by-text are absent; clearly above a 3 since more than 1-2 specific actions are named.

4 / 5

Completeness

Both what ("Google Sites through gog" plus a concrete action list) and when (explicit "Use for..." clause) are present, so the completeness cap does not apply. Falls short of 5 because the trigger guidance is task-voice ("Use for finding...") rather than the user-voice phrasing ("when the user mentions...") in the anchor-5 example.

4 / 5

Trigger Term Quality

Natural terms "Google Sites", "site metadata", "editor URLs", and "Drive" match what users would say. Not a 5 because common variations (e.g., "Sites website", "site link") are missing; well above a 3 since multiple relevant natural phrases are present.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Google Sites operations) with distinct triggers, and it actively disambiguates the sibling skill with "use gog-drive for file sharing". Minimal conflict risk — matches the anchor-5 example pattern of a narrow domain with explicit trigger terms.

5 / 5

Total

17

/

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-sites/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.