CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-keep

Google Keep through gog. Use for Google Keep notes and attachments.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured CLI wrapper skill: executable safe-start commands, a clear command table, and explicit safety checkpoints for destructive operations. The only gaps are the absence of worked examples for common operations and any error-recovery guidance beyond 'do not guess command syntax'.

DimensionReasoningScore

Conciseness

The body is ~30 purely operational lines — "Use `gog` for Google Keep operations. Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules." — with no explanation of concepts Claude already knows and no padding. It matches anchor 5 (lean, every token earns its place); there is no over-explanation to trim, so it is not 4.

5 / 5

Actionability

Safe start provides three copy-paste-ready commands (`gog auth list --check --json --no-input`, `gog schema keep --json`, `gog --readonly --account user@example.com keep --help`) plus a command table and explicit flag guidance. It is not 5 because no worked examples cover the common cases (create/list/search) — the skill defers entirely to `--help` and schema; it is not 3 because the commands given are real and executable, not pseudocode.

4 / 5

Workflow Clarity

The safe-start sequence is clear with explicit checkpoints: auth `--check`, `--readonly`, `--dry-run` before writes, and "Confirm the exact account, object, and mutation before any write or delete" — so the destructive `delete` command does have validation guidance and the ≤3 cap does not apply. It is not 5 because there is no error-recovery feedback loop (e.g., what to do when the auth check fails) and "before supported writes" is vague about which writes support dry-run; it is not 3 because the checkpoints are present and explicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references: well-organized sections (Safe start, Commands) and a single clearly signaled one-level-deep reference (`../gog/SKILL.md`) for shared suite rules. The rubric's simple-skill exception applies, so well-organized sections alone warrant 5; no bundle files exist to inline or reorganize.

5 / 5

Total

18

/

20

Passed

Description

68%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 has an explicit use-when clause and a highly distinct niche, but the 'what' clause names no concrete actions — it identifies the domain and objects without saying what can be done with them. Trigger coverage is good but misses common Keep vocabulary like checklists and reminders.

Suggestions

Add concrete action verbs to the 'what' clause, e.g. "Create, list, search, get, and delete Google Keep notes and download attachments via the gog CLI" — this mirrors the command table already in the body.

Broaden trigger coverage with natural Keep variations users actually say, such as checklists, reminders, or note lists.

Consider making the 'when' clause slightly more task-specific (e.g., note creation, searching notes, retrieving attachments) rather than object-level only.

DimensionReasoningScore

Specificity

"Google Keep through gog" names the domain and tool, but the description contains no action verbs — "notes and attachments" are objects, not concrete actions. It matches anchor 2 (names the domain, actions minimal or generic); it is not 3 because no concrete actions are listed, and not 1 because the domain is clearly and specifically named.

2 / 5

Completeness

The explicit when-clause "Use for Google Keep notes and attachments" is present, and "Google Keep through gog" supplies a minimal what. It is not 5 because the 'what' lacks concrete actions, and not 3 because the 'when' is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

"Google Keep", "notes", and "attachments" are the natural terms a user would say when needing this skill, giving good keyword coverage. It is not 5 because common Keep variations (checklists, reminders, lists) are missing, and not 3 because the primary natural terms are all present.

4 / 5

Distinctiveness Conflict Risk

"Google Keep" is a clear niche with distinct, unambiguous triggers — a user mentioning Keep is unlikely to mean another skill. It is not 4 because even the overlap risk with sibling gog skills is negligible given the service is explicitly named.

5 / 5

Total

15

/

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-keep/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.