gog-weekly-digest

Read-only weekly digest across Google Calendar, Gmail, and Tasks with gog.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-weekly-digest/SKILL.md

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is admirably concise and action-packed with executable read-only commands and clear constraints. Its main weaknesses are missing verification and prerequisite references that point to skills not present in the bundle.

Suggestions

Replace or guard the four '../gog*/SKILL.md' prerequisite references so the digest still works when those sibling skills are absent, or note that they are external dependencies.

Add a lightweight verification checkpoint, e.g. 'Confirm each command returned JSON before summarizing; if a source errors, note it in the digest rather than silently dropping it.'

Explicitly state the expected output shape (sections for milestones, upcoming commitments, overdue tasks, actionable mail, schedule risks) so the summarize step is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~20 lines of executable gog commands with no padding and no explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready gog commands with concrete flags (--readonly, --max, --json, --wrap-untrusted) and a real Gmail search query, plus an explicit read-only constraint.	3 / 3
Workflow Clarity	A sequence is present (read prerequisites, collect inputs, summarize, observe constraints) but there is no validation/checkpoint step and the four prerequisite SKILL.md references resolve to non-existent files, leaving the entry step broken.	2 / 3
Progressive Disclosure	The skill is short with no bundle files, which is appropriate, but it points to four sibling SKILL.md paths (../gog, ../gog-calendar, ../gog-gmail, ../gog-tasks) that are not part of this bundle and do not exist, so the references are not reliably navigable.	2 / 3
	Total	10 / 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 is concise and names a clear cross-product niche, but it only implies what to do and gives no explicit trigger guidance for when Claude should invoke it. Adding a 'Use when...' clause and a few concrete actions would lift all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a weekly summary or recap of their calendar, mail, and tasks.'

Expand the action list beyond 'digest' to concrete verbs such as 'collect, summarize, and surface risks across Google Calendar, Gmail, and Tasks'.

Include a couple of natural user phrasings ('weekly recap', 'what did I miss this week') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three data sources (Google Calendar, Gmail, Tasks) and one action ('weekly digest'), but does not list multiple concrete actions like summarize, collect, or report, so it stops at 'domain and some actions'.	2 / 3
Completeness	States clearly what the skill does but provides no 'when to use it' trigger; per the rubric, a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes some natural terms ('weekly digest', 'Google Calendar', 'Gmail', 'Tasks') but misses common variations users would say ('schedule', 'inbox', 'to-do') and has no explicit 'Use when' trigger phrase.	2 / 3
Distinctiveness Conflict Risk	The three-source weekly-digest niche with the 'gog' tool is somewhat specific and unlikely to conflict broadly, but the absence of explicit trigger terms leaves it relying on tool name alone rather than distinct triggers.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openclaw/gogcli
Path: .agents/skills/gog-weekly-digest/SKILL.md
Commit: 1dbd820

Reviewed: about 23 hours 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.