The content is an exemplary lean instruction skill: fully executable bounded commands, concrete summary directives with a facts-vs-inference rule, an explicit safety constraint, and correct delegation of detail to sibling skill files. The only gap is the absence of validation/error-handling checkpoints around the batch input collection.

Dimension	Reasoning	Score
Conciseness	The ~20-line body contains zero concept explanations and no padding: 'Read ... first', four bounded commands, a summarization directive, and a safety constraint. Every token earns its place, matching the anchor for lean and efficient content.	5 / 5
Actionability	Four complete, executable gog commands with exact flags (--readonly, --max, --json, --wrap-untrusted, --gmail-no-send) plus concrete summary categories cover the common cases. The placeholders (user@example.com, TASKLIST_ID) are standard variables on par with good examples like 'validate.py unpacked_dir/', not pseudocode, so this is fully executable rather than the minor-gap level of 4.	5 / 5
Workflow Clarity	The sequence is clear: read sibling skills first, collect bounded read-only inputs (with the tasks list command depending on the prior lists call), then summarize with an explicit facts-vs-inference rule and a no-mutation constraint. It is not 5 because there are no validation checkpoints or error-recovery steps (e.g., what to do if a command fails or returns partial data). The destructive/batch cap at 3 does not apply since the skill is explicitly read-only.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no bundle files, and is well organized with a heading, command block, and instructions. Detail is delegated one level deep to clearly signaled sibling skill files ('Read ../gog/SKILL.md ... first'), which fits the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

61%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 concise and specific about the domain and the read-only nature of the skill, with good natural trigger keywords. Its main weakness is the missing 'Use when...' trigger guidance and the absence of enumerated concrete actions, which leaves completeness and specificity at the mid-level.

Suggestions

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

Enumerate the digest contents to raise specificity, e.g. 'Summarizes completed milestones, upcoming commitments, overdue tasks, and unanswered actionable mail.'

Include common synonyms users say, such as 'email', 'weekly recap', or 'weekly summary', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain clearly ('weekly digest across Google Calendar, Gmail, and Tasks') and one capability ('read-only ... digest'), but does not list several concrete actions such as what the digest covers. Anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') fits; it is not 4 because no specific actions are enumerated, and not 2 because the domain and action are clearly stated rather than minimal or generic.	3 / 5
Completeness	The 'what' is clear ('Read-only weekly digest across Google Calendar, Gmail, and Tasks with gog') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is specific, not vague; not 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	'weekly digest', 'Google Calendar', 'Gmail', and 'Tasks' are natural phrases a user would say when needing this skill, giving good keyword coverage. It is not 5 because common synonyms like 'email', 'weekly recap', or 'weekly summary' are missing; it is above 3 because multiple natural product and task terms are present.	4 / 5
Distinctiveness Conflict Risk	The cross-service digest framing with 'gog' is a clear niche unlikely to trigger for unrelated skills. Minor overlap risk remains with single-service gog-calendar/gmail/tasks skills, so anchor 4 ('mostly distinct; minor overlap risk with closely related skills') fits better than 5 or 3.	4 / 5
	Total	14 / 20 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: 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.