gog-appscript

Apps Script operations through gog.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-appscript/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 an efficient, well-structured CLI overview with copy-paste safety commands and a clear command map. Its main weakness is the lack of an explicit validation feedback loop for destructive/batch operations, which caps workflow clarity.

Suggestions

Add an explicit destructive-operation workflow with a validation checkpoint, e.g. run with --dry-run first, inspect the planned mutation, confirm account/object, then execute and re-verify.

Show one or two representative per-command invocations inline (e.g. `gog appscript run --account ... --function ...`) so common cases are copy-paste ready without consulting --help.

Clarify the pull→edit→deploy sequence as a concrete ordered workflow for the common 'modify an Apps Script project' task.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero padding — a Safe-start code block, a tight command table, and a one-line pointer to per-command help — assuming Claude's competence so every token earns its place.	5 / 5
Actionability	Safe start gives copy-paste-ready commands and the command table maps each subcommand to its purpose, but actual per-command syntax is deferred to --help/schema rather than shown inline, a minor gap short of fully executable coverage.	4 / 5
Workflow Clarity	A safe-start discovery sequence exists and safety flags (--readonly, --dry-run) plus a 'confirm before write/delete' note are present, but there is no explicit validate→fix→retry checkpoint loop for the destructive/batch ops (create, run, delete), which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Under 50 lines with clean sections (Safe start, Commands) and one clearly-signaled, one-level reference (../gog/SKILL.md); no nested references, so navigation is easy and content is appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

32%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 terse and distinct but underspecified: it names the domain and tool yet describes no concrete actions and provides no trigger guidance for when to invoke the skill. Expanding it with specific Apps Script operations and a 'Use when...' clause would substantially raise its score.

Suggestions

Replace the generic word "operations" with concrete actions, e.g. 'Create, pull, deploy, and run Apps Script projects through gog.'

Add a 'Use when...' trigger clause, e.g. 'Use when the user needs to manage Apps Script projects, deployments, versions, or run deployed functions.'

Include natural synonyms/extensions users might say, such as 'Google Apps Script', 'GAS', or '.gs' files, to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Apps Script") but the only action verb is the generic "operations", matching the anchor 'Names the domain but actions are minimal or generic'; it does not list concrete actions so it cannot reach 3.	2 / 5
Completeness	It gives only a vague 'what' ("Apps Script operations") and no 'when'/trigger clause, fitting anchor 2; the missing 'Use when...' guidance also caps completeness at 3.	2 / 5
Trigger Term Quality	"Apps Script" is a genuine natural term, but "operations through gog" is tool jargon and no synonyms or common phrasings are offered, leaving it below the 'some relevant keywords' bar of 3.	2 / 5
Distinctiveness Conflict Risk	"Apps Script ... through gog" carves a clear niche with minimal conflict risk, though the generic word "operations" leaves minor overlap risk with sibling gog skills, so it stops short of 5.	4 / 5
	Total	10 / 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-appscript/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.