CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-sheets

Google Sheets through gog. Use for spreadsheet cells, formulas, formatting, notes, validation, and sheet structure.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A tight, action-oriented CLI skill body with executable safe-start commands, real validation checkpoints around writes, and clean delegation of detail to runtime discovery. The main gaps are the absence of a worked write-command example and any error-recovery guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: no explanation of what Google Sheets is, terse safety bullets, one-line command purposes, and a closing pointer to --help and schema for syntax. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The Safe start block is copy-paste executable with concrete flags (--readonly, --json --wrap-untrusted, --no-input, --dry-run), the command table provides the full vocabulary, and 'gog sheets <command> --help' / 'gog schema sheets <command> --json' give exact discovery commands. It stops short of anchor 5 because there is no worked example of an actual write invocation (e.g., update or append with arguments), only the read example.

4 / 5

Workflow Clarity

The sequence is clear: read the shared gog rules first, then auth check, schema, and a readonly read before any mutation, with validation checkpoints present ('--dry-run before supported writes', 'Confirm the exact account, object, and mutation before any write or delete'), so the destructive-operation cap does not apply. It misses anchor 5 because there is no error-recovery feedback loop (e.g., what to do when auth or a write fails).

4 / 5

Progressive Disclosure

Sections are well organized (Safe start, Commands), the single external reference (../gog/SKILL.md) is clearly signaled and one level deep, and per-command detail is delegated to runtime --help/schema rather than inlined. It sits between anchors 4 and 5 because the 39-row command table is inline bulk that could partly live in a reference file, and no bundle files exist to further split content.

4 / 5

Total

17

/

20

Passed

Description

78%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.

A concise, well-scoped description that states what it does and when to use it with an explicit trigger clause and strong distinctiveness. Its main limitation is terseness in the what-statement and a few missing natural trigger terms for supported features like charts, tabs, and filters.

DimensionReasoningScore

Specificity

The description names the domain and tool ("Google Sheets through gog") and lists six specific capability areas ("spreadsheet cells, formulas, formatting, notes, validation, and sheet structure"), matching the 'several specific items with minor gaps' anchor. It falls short of 5 because it uses feature nouns rather than concrete action verbs and omits supported areas like charts, filters, and tabs, but exceeds 3's '1-2 concrete actions' bar.

4 / 5

Completeness

Both parts are present: a what-statement ("Google Sheets through gog") and an explicit when-clause ("Use for spreadsheet cells, formulas, ..."). It matches anchor 4 rather than 5 because the what-statement is terse and lacks concrete operations, and the when-clause lists feature areas rather than concrete user-mention trigger phrases; it is above 3 since the trigger guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

It includes the natural synonym pair "Google Sheets" and "spreadsheet" plus feature terms users would say ("cells", "formulas", "formatting", "validation"), giving good keyword coverage. A few natural terms are missing (charts, tabs, rows/columns, filters), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Google Sheets through gog" carves out a clear, distinct niche with specific triggers, and the Sheets scoping (plus explicit feature areas like notes and validation) minimizes overlap with generic spreadsheet or sibling gog skills. It matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-sheets/SKILL.md

Reviewed

Table of Contents

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.