gog-tasks

Google Tasks operations through gog.

Quality

71%

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

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, command-first skill body with executable safe-start commands, explicit safety checkpoints for destructive operations, and clean structure. The only gaps are the absence of a worked example for a common operation and any post-write verification step.

Dimension	Reasoning	Score
Conciseness	The body contains only executable commands, flag guidance, safety rules, and a command table — every token earns its place with no concept explanations or padding.	5 / 5
Actionability	The safe-start block ('gog auth list --check --json --no-input', 'gog schema tasks --json') is copy-paste ready with concrete flags, but no example invocation of a common case such as adding or completing a task is shown — a minor gap left to '--help'.	4 / 5
Workflow Clarity	Explicit pre-write checkpoints are present ('Confirm the exact account, object, and mutation before any write or delete', '--dry-run', '--readonly'), so the destructive-operation cap does not apply, but no post-write verification step exists. Anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') fits better than 5, which requires feedback loops for error recovery.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files, well-organized sections, and a single clearly-signaled one-level reference ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules') plus --help/schema for detail — matches the simple-skill exception for a full score.	5 / 5
	Total	18 / 20 Passed

Description

43%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 is distinct and appropriately concise but undersells the skill: it names the domain and tool without listing any concrete operations and gives no trigger guidance for when to use it. Anchor comparisons consistently land at the low-to-mid range for specificity and completeness.

Suggestions

Enumerate the concrete operations in the description, e.g. 'Add, list, update, complete, and delete Google Tasks through the gog CLI' to raise specificity from anchor 2.

Add an explicit 'when' clause, e.g. 'Use when the user mentions Google Tasks, to-dos, or task lists' — its absence currently caps completeness at 3 and the vague 'what' drops it to 2.

Include natural trigger synonyms such as 'to-dos' and 'task lists' alongside 'Google Tasks' to improve keyword coverage from anchor 3 toward 4-5.

Dimension	Reasoning	Score
Specificity	'Google Tasks operations' names the domain and tool but lists zero concrete actions — anchor 2 ('Names the domain but actions are minimal or generic'). Not 3 because no operation (add, list, complete, delete) is enumerated; not 1 because the domain and tool are concretely named.	2 / 5
Completeness	The 'what' is vague — 'operations' is unspecified — and the 'when' is entirely absent, matching anchor 2 ('Has a vague "what" and no "when"'). The missing 'Use when...' clause caps completeness at 3, and the vague what places it below that cap.	2 / 5
Trigger Term Quality	'Google Tasks' is a specific, natural term a user would say, but common variations and synonyms (to-dos, todo lists, task lists) are missing — anchor 3 ('Some relevant keywords but missing common variations or synonyms'). Not 4 because keyword coverage beyond the product name is absent.	3 / 5
Distinctiveness Conflict Risk	'Google Tasks' combined with the 'gog' tool is a clear niche with distinct triggers and minimal conflict risk with other skills; no other common skill would trigger on this phrase.	5 / 5
	Total	12 / 20 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-tasks/SKILL.md
Commit: 414e2ff

Reviewed: 3 days 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.