gog-appscript

Apps Script 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-appscript/SKILL.md

Quality

Content

87%

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 strong, concise CLI skill: executable safe-start commands, a clear command table, and good safety guidance, with the only gap being the lack of an explicit verify/retry feedback loop around destructive operations.

Suggestions

Add a post-action verification step for writes, e.g. re-run `gog appscript get` after `create` to confirm the project exists.

Make the safe-start checkpoint explicit, e.g. "Only proceed when `auth list --check` reports the expected account."

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: it never explains what Apps Script is, and every line (safe-start commands, safety bullets, command table) earns its place.	3 / 3
Actionability	The "Safe start" block gives three fully executable, copy-paste-ready commands, and the command table plus `--help`/`schema --json` guidance gives concrete, specific direction rather than vague description.	3 / 3
Workflow Clarity	There is a sensible safe-start sequence and pre-write checkpoints (confirm account/object/mutation, `--dry-run`, `--readonly`), but no explicit feedback loop or post-action verification for destructive create/write operations.	2 / 3
Progressive Disclosure	A simple, under-50-line skill with well-organized sections (Safe start, Commands) and a single one-level-deep, clearly signaled reference ("Read `../gog/SKILL.md` first"), so no further file split is needed.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 compact and names the right domain and tool, but it is vague on concrete actions and entirely lacks an explicit trigger clause, leaving every dimension at the middle level.

Suggestions

Replace "operations" with concrete actions, e.g. "Create, read, and run Google Apps Script projects through gog."

Add an explicit trigger clause, e.g. "Use when working with Google Apps Script projects or running Apps Script functions."

Include natural user phrasings such as "Google Apps Script" and "Apps Script functions" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Apps Script operations" names a concrete domain and the tool ("through gog") but uses the generic word "operations" rather than listing specific actions like create, read, or run.	2 / 3
Completeness	It states a weak "what" (Apps Script operations) but has no "when" clause; per the guidelines a missing "Use when..." trigger caps completeness at 2.	2 / 3
Trigger Term Quality	"Apps Script" is a natural keyword a user would say, but "operations" is generic and "gog" is internal jargon, with no common variations or trigger context.	2 / 3
Distinctiveness Conflict Risk	Apps Script is a specific niche unlikely to clash with unrelated skills, but the generic "operations" and absence of distinct trigger language keep it from a clear, conflict-free niche.	2 / 3
	Total	8 / 12 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: 1dbd820

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.