CtrlK
BlogDocsLog inGet started
Tessl Logo

gog-tasks

Google Tasks operations through gog.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-tasks/SKILL.md
SKILL.md
Quality
Evals
Security

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 an exemplary compact CLI wrapper skill: executable commands with exact flags, a complete command table, explicit safety/validation checkpoints for destructive operations, and clean one-level external navigation. No bundle files are present or needed, and the structure suits the skill's scope.

DimensionReasoningScore

Conciseness

The ~35-line body is lean: a short intro, a safe-start block with guardrail bullets, a compact command table, and a footer, with no filler, no concept explanations, and every token earning its place.

3 / 3

Actionability

It gives copy-paste-ready executable commands with exact flags (e.g. "gog --readonly --account user@example.com tasks lists list --json --wrap-untrusted"), a full command table, and explicit pointers to --help and schema JSON instead of guessing.

3 / 3

Workflow Clarity

The Safe start sequence is ordered (auth list, schema, readonly list) and destructive/batch operations get explicit checkpoints ("--dry-run before supported writes", "confirm the exact account, object, and mutation before any write or delete"), satisfying the destructive-ops feedback-loop requirement.

3 / 3

Progressive Disclosure

A short, well-sectioned body (## Safe start, ## Commands) with no bundle files present and a single clearly-signaled one-level reference to ../gog/SKILL.md for shared rules; per the simple-skills note this is well-organized and easy to navigate.

3 / 3

Total

12

/

12

Passed

Description

50%

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 correctly identifies the domain and tool but is minimal: it states only a generic capability with no concrete actions, no trigger guidance, and no distinguishing detail beyond the tool name. It meets the baseline but stops well short of the rubric's strong examples.

Suggestions

List concrete operations the skill supports, e.g. "add, list, complete, delete, and update Google Tasks via the gog CLI" to lift specificity and trigger-term coverage.

Add an explicit trigger clause such as "Use when the user asks to manage Google Tasks, to-do lists, or reminders." to satisfy the completeness "when" requirement.

Include natural user terms ("to-do list", "tasks", "reminders", "checklist") alongside "Google Tasks" so the description triggers on the phrasings users actually say.

DimensionReasoningScore

Specificity

Names the domain ("Google Tasks") and a generic class of action ("operations") but lists no concrete operations such as add, list, complete, or delete, so it does not reach multiple-specific-actions.

2 / 3

Completeness

It states what the skill does ("Google Tasks operations through gog") but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

"Google Tasks" is a natural keyword a user would say, but common variations (to-do list, tasks, reminders, checklist) are absent and "gog" is internal tool jargon rather than a user-spoken term.

2 / 3

Distinctiveness Conflict Risk

The Google Tasks niche is somewhat specific, but the shared "through gog" framing with sibling gog-* skills (calendar, mail, etc.) leaves overlap risk and no distinguishing triggers.

2 / 3

Total

8

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
openclaw/gogcli
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.