gog-keep

Google Keep operations through gog.

Quality

73%

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

Quality

Content

100%

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 model of concise, actionable guidance: executable safe-start commands, a clean command table, and explicit safety checkpoints for writes and deletes. It delegates shared context one level deep without nested references.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines) with no concept explanation Claude already knows; the safe-start block, command table, and flag guidance each earn their tokens.	3 / 3
Actionability	It provides concrete, executable commands (e.g. 'gog auth list --check --json --no-input', 'gog schema keep --json') and a full command table, directing to --help and schema for the machine-readable contract.	3 / 3
Workflow Clarity	The Safe start section sequences auth/schema/help, and the explicit 'Confirm the exact account, object, and mutation before any write or delete' checkpoint covers destructive operations with --readonly and --dry-run safeguards.	3 / 3
Progressive Disclosure	As a simple, well-organized skill under 50 lines with no bundle files, it appropriately delegates shared rules to the one-level-deep '../gog/SKILL.md' reference and command details to --help/schema.	3 / 3
	Total	12 / 12 Passed

Description

47%

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 identifies a clear niche (Google Keep via gog) but is too terse: it names no concrete actions and omits any 'Use when...' trigger guidance. It reads more like a label than an actionable skill description.

Suggestions

List concrete actions, e.g. 'Create, list, search, get, and delete Google Keep notes through gog.'

Add an explicit trigger clause, e.g. 'Use when the user asks to manage Google Keep notes or checklists.'

Include natural user terms like 'notes', 'checklists', and 'to-dos' alongside 'Google Keep' to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The description uses the abstract term 'operations' and names no concrete actions (create, list, delete, search), paralleling the vague 'Helps with documents' anchor rather than the score-2 'Names domain and some actions'.	1 / 3
Completeness	It states a weak 'what' (Google Keep operations) but provides no 'when' guidance, and the missing 'Use when...' clause caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	'Google Keep' is a natural term a user would say, but common variations like 'notes', 'checklists', or 'to-dos' are missing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Google Keep is a clearly distinct niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor even though the phrasing is terse.	3 / 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-keep/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.