gog-docs

Google Docs operations through gog.

Quality

55%

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-docs/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 tight, highly actionable command catalog with a sensible safe-start sequence and clean progressive disclosure that delegates detail to runtime help and the shared gog skill. Its main gap is the absence of explicit validation/verification checkpoints for the destructive operations it exposes.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows; it opens with a one-line purpose, delegates shared rules to ../gog/SKILL.md, and every section (Safe start, command table, closing pointer) earns its tokens.	3 / 3
Actionability	The Safe start gives three copy-paste-ready commands, the command table enumerates real subcommands with one-line purposes, and the closing line directs to `--help` and `gog schema ... --json` for exact contracts — fully executable guidance.	3 / 3
Workflow Clarity	A clear starting sequence (auth list, schema, readonly cat) is present with safety bullets, but destructive commands (clear, delete, delete-tab) lack explicit validate-then-proceed checkpoints or feedback loops, capping the score at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Content is well-organized into sections, with the only file reference (../gog/SKILL.md) clearly signaled and one level deep, and detailed flags/contracts appropriately deferred to runtime `--help` and `schema` rather than nested files.	3 / 3
	Total	11 / 12 Passed

Description

22%

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 correctly identifies the Google Docs domain and the gog tool but is too abstract: it names no concrete actions and provides no usage triggers, leaving both the "what" and "when" underspecified. It is distinguishable by product but generic in capability.

Suggestions

Name concrete actions, e.g. "Create, edit, read, and export Google Docs; find/replace text, manage tables, tabs, and images through gog."

Add an explicit trigger clause, e.g. "Use when working with Google Docs or when the user mentions Docs, .gdoc, or document editing."

Use third-person capability verbs ("Creates", "Edits", "Exports") instead of the abstract noun "operations" to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names only the domain and tool ("Google Docs operations through gog") with the abstract word "operations" and no concrete actions, matching the vague/abstract anchor rather than the score-2 anchor that lists some actions.	1 / 3
Completeness	It states a weak "what" (abstract "operations") and entirely omits any "when"/"Use when" trigger guidance, satisfying the score-1 anchor of missing what-or-when or both very weak.	1 / 3
Trigger Term Quality	"Google Docs" is a natural term users would say, but "gog" is tool jargon and "operations" is generic, with no common variations (docs, documents) — matching the some-relevant-keywords-but-incomplete anchor.	2 / 3
Distinctiveness Conflict Risk	It targets a specific product niche (Google Docs) but the generic "operations" and absence of distinct trigger terms mean it could overlap sibling gog skills (Sheets, Slides), matching the somewhat-specific-but-overlapping anchor.	2 / 3
	Total	6 / 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-docs/SKILL.md
Commit: 1dbd820

Reviewed: about 23 hours 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.