gog-sites

Google Sites operations through gog.

Quality

68%

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

Quality

Content

82%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 a lean, high-signal quick-start for a simple read-oriented skill: executable verification commands, explicit safety gates for writes, and correct deferral of detail to the CLI's own --help/schema output. Its only real weakness is the dangling reference to ../gog/SKILL.md, which is not part of this bundle.

Dimension	Reasoning	Score
Conciseness	Every line earns its place: executable safe-start commands, terse safety flags, a compact command table, and pointers to --help/schema instead of inlined flag documentation. There is no over-explanation of concepts Claude already knows.	5 / 5
Actionability	The safe-start block gives concrete, executable bash commands (auth check, schema, readonly help) and explicit safety guidance (--account, --json --wrap-untrusted, --dry-run). It is not 5 because the command table lists only verb names without any example invocations of the common cases.	4 / 5
Workflow Clarity	A clear safe-start sequence (check auth → read schema → inspect help) is presented with validation checkpoints (--check, --readonly, --dry-run, confirm-before-write). It is not 5 because there is no error-recovery guidance (e.g. what to do when the auth check fails).	4 / 5
Progressive Disclosure	A short, well-organized body correctly defers flag details to --help and gog schema, and points to a clearly signaled one-level reference (../gog/SKILL.md) for shared rules. It is not 5 because that referenced sibling file is not present in this bundle, so the navigation path cannot be validated.	4 / 5
	Total	17 / 20 Passed

Description

40%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 identifies a clear, distinct domain (Google Sites via the gog CLI) but says almost nothing about what the skill concretely does or when it should be used. It functions as a bare label rather than an actionable, trigger-rich description.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Google Sites — listing, searching, or getting site metadata or editor URLs."

Replace the generic word "operations" with the concrete verbs the skill supports: get, list, search, and print editor URLs for Google Sites.

Include natural synonyms users would say, such as "Google Sites website", "Sites", and "site URL", to improve trigger matching.

Dimension	Reasoning	Score
Specificity	"Google Sites operations" names the domain but "operations" is entirely generic — no concrete actions are listed, matching anchor 2 ("Processes PDF files"). It is not 3 because no specific action (e.g. list, search, get metadata) is enumerated.	2 / 5
Completeness	The "what" is vague ("operations") and there is no "when" clause at all, matching anchor 2 ("vague 'what' and no 'when'"). The missing 'Use when...' guidance also caps this dimension at 3 per the judging guidelines.	2 / 5
Trigger Term Quality	"Google Sites" and "gog" are relevant keywords users would naturally say, but common variations and synonyms ("Sites website", "Google Sites URL", "site editor") are missing. Coverage is a single natural term, below anchor 4's "a few natural terms missing".	3 / 5
Distinctiveness Conflict Risk	"Google Sites" plus "through gog" carves a distinct niche with clear tool attribution, only overlapping with closely related sibling gog-* skills (Drive, Docs). Not 5 because the domain is named without explicit trigger phrases to fully separate it from adjacent gog skills.	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-sites/SKILL.md
Commit: 414e2ff

Reviewed: 3 days 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.