CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-tasks

Google Tasks through gog. Use for Google Tasks lists, task creation, updates, completion, and materialized repeats.

Quality

88%

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

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

An exemplary lean CLI skill: executable safe-start commands, explicit safety gates before any write, a complete command table, and authoritative schema-based discovery instead of inlined syntax. The only gap is the absence of a post-write verification step for its delete/clear operations.

DimensionReasoningScore

Conciseness

The body is lean with zero padding: three executable commands, a compact command table, and one-line safety directives. No concept Claude already knows is explained, and every token earns its place.

5 / 5

Actionability

The safe-start block is copy-paste ready ('gog auth list --check --json --no-input', 'gog schema tasks --json', a readonly list command), the table enumerates every subcommand with its purpose, and 'gog tasks <command> --help' plus 'gog schema tasks <command> --json' give a concrete, authoritative path for exact syntax instead of guessing.

5 / 5

Workflow Clarity

Safe start establishes a real sequence (auth check, schema, readonly list) with pre-write checkpoints ('--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 stops short of a 5 because there is no post-write verification or feedback loop (e.g., re-fetch the task to confirm the mutation).

4 / 5

Progressive Disclosure

At ~43 lines with no bundle files needed, the skill is well organized into Safe start / Commands / discovery guidance, and its single external reference ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules') is clearly signaled and one level deep.

5 / 5

Total

19

/

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, third-person description with an explicit 'Use for...' trigger clause and a distinct product-specific niche. Its main limitation is modest coverage: deletion/clearing operations and common synonyms ('to-dos', 'reminders') are absent, and 'materialized repeats' is jargon users would not naturally say.

Suggestions

Mention the deletion and clearing operations (e.g., 'delete tasks, clear completed tasks') so the capability list is comprehensive.

Add a natural synonym or two such as 'to-do list' alongside 'Google Tasks lists', and rephrase 'materialized repeats' in user-facing terms (e.g., 'recurring tasks materialized as individual entries').

DimensionReasoningScore

Specificity

Lists several concrete actions ('task creation, updates, completion, and materialized repeats') alongside the tool and domain, but omits deletion and clearing of completed tasks, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Both parts are present: 'Google Tasks through gog' states what, and an explicit 'Use for...' clause states when. The what-clause is terse compared to the anchor-5 pattern where the operation list carries the what, keeping this just below a 5.

4 / 5

Trigger Term Quality

Natural phrases users would say ('Google Tasks lists', 'task creation', 'updates', 'completion') are present, but common synonyms like 'to-do list' or 'reminders' are missing and 'materialized repeats' leans on internal jargon.

4 / 5

Distinctiveness Conflict Risk

'Google Tasks' is a product-specific trigger with a clear niche and unambiguous trigger terms; the only overlap risk is with sibling gog skills, which the 'Google Tasks' qualifier already disambiguates.

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