gog-sites

Google Sites operations through gog.

Quality

64%

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

80%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 tight, well-structured CLI wrapper that gives executable safe-start commands and points one level deep to the parent gog skill. Its main gap is the lack of an explicit validation feedback loop for destructive writes, which caps workflow clarity.

Suggestions

Add a short numbered write/delete workflow with an explicit validation checkpoint (e.g., run with --dry-run, inspect the planned mutation, then execute only on confirmation).

Show one or two full executable command examples for the most common subcommands (e.g., `gog sites list --account ... --json`) instead of only the safe-start intros.

Clarify the expected `--json --wrap-untrusted` output shape so Claude can parse results without trial and error.

Dimension	Reasoning	Score
Conciseness	The ~33-line body is lean and assumes Claude's competence: a safe-start command block, a compact commands table, and brief flag guidance, with no padding or explanation of what Google Sites is.	5 / 5
Actionability	It provides copy-paste-ready safe-start commands and a concrete commands table, but delegates per-subcommand flag details to `--help`/`--schema` rather than showing full executable examples for each common case.	4 / 5
Workflow Clarity	The skill drives destructive Google-data mutations and provides safety checkpoints (--readonly, --dry-run, confirm account/object/mutation), but it has no explicit sequenced write workflow with a validate-fix-retry feedback loop, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	The under-50-line body is well organized into labeled sections and signals a single one-level-deep reference ("Read `../gog/SKILL.md` first") for shared rules, with no nested references; the references/scripts/assets bundle dirs are absent and nothing is over-inlined.	5 / 5
	Total	17 / 20 Passed

Description

48%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 short, third-person, and clearly scoped to Google Sites via gog, but it is generic about actions and lacks any explicit "use when" trigger guidance. It is distinguishable but under-specified compared to strong examples.

Suggestions

List 2-3 concrete actions in the description (e.g., "List, search, and get Google Sites metadata") instead of the generic "operations".

Add an explicit trigger clause such as "Use when working with Google Sites, listing or searching Sites in Drive, or getting Site metadata/URLs".

Include natural synonym/extension terms users say ("Google Sites", "Sites", "Google website") to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Google Sites operations through gog" names the domain and tool but uses the generic word "operations" instead of listing concrete actions (create, list, search), matching the anchor that names the domain with minimal or generic actions.	2 / 5
Completeness	It conveys a recognizable "what" (operations on Google Sites via gog) but provides no "when to use it" trigger clause, so per the missing-trigger cap it cannot exceed 3 even though the "what" is somewhat generic.	3 / 5
Trigger Term Quality	"Google Sites" is a natural term users would actually say, but the description omits common variations/synonyms ("Sites", "Google website") and the only other term, "gog", is tool jargon rather than a user phrase.	3 / 5
Distinctiveness Conflict Risk	"Google Sites operations through gog" targets a specific niche tied to the gog tool family, making it mostly distinct with only minor overlap risk against a sibling generic gog skill.	4 / 5
	Total	12 / 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: eb85a99

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.