gog-meeting-prep

Google Calendar meeting preparation with gog, including attendees and linked Workspace files.

Quality

75%

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

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.

The content is a lean, highly actionable workflow with concrete executable commands, a clear sequenced process with sensible checkpoints, and well-signaled one-level references to sibling skills. The only minor gap is the absence of an explicit error-recovery loop for failed API calls.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean with no padding or explanation of concepts Claude already knows (no definition of gog, Calendar, or attendees); every line is actionable instruction, matching anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place').	5 / 5
Actionability	Concrete, executable `gog` commands with real flags (--readonly, --from now --days 2 --max 20, --json --wrap-untrusted) cover the common cases (fetch events, get Drive file, cat Doc), with only expected placeholder substitution (account, FILE_ID, DOCUMENT_ID), matching anchor 5 ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases').	5 / 5
Workflow Clarity	A clear numbered 5-step sequence is present with checkpoints ('Report ambiguity' in step 2, an access-authorization guard in step 4, and a read-only safety note); it is not a destructive/batch operation so the workflow-clarity cap does not apply, but there is no explicit error-recovery feedback loop for failed API calls, fitting anchor 4 rather than 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files, well-organized into a heading, a clearly signaled 'Read ... first' pointer to one-level-deep sibling SKILL.md files, numbered steps, and a safety note, matching anchor 5 ('Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').	5 / 5
	Total	19 / 20 Passed

Description

56%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 clearly scopes the skill to Google Calendar meeting preparation with gog and surfaces natural trigger terms, but it lacks concrete action verbs and any explicit 'Use when' invocation guidance. These gaps leave it moderately rather than strongly specified.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when preparing for an upcoming Google Calendar meeting or when the user asks for meeting prep.'

Replace the scope statement with concrete action verbs, e.g. 'Fetches upcoming Google Calendar events, extracts attendees, agenda, and linked Workspace files to produce a meeting prep brief.'

Include common synonym triggers users might say, such as 'agenda', 'prep', or 'calendar event', to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Google Calendar meeting preparation with gog') and entities ('attendees and linked Workspace files') but uses no concrete action verbs, matching anchor 2 ('Names the domain but actions are minimal or generic') rather than anchor 3 which requires 1-2 concrete actions.	2 / 5
Completeness	A clear 'what' is stated but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3 ('Has a clear what but when is missing or only weakly implied').	3 / 5
Trigger Term Quality	Natural user-facing terms are present ('Google Calendar', 'meeting', 'meeting preparation', 'attendees', 'Workspace files'), giving good keyword coverage; a few common synonyms are missing (e.g., 'agenda', 'prep', 'calendar event'), placing it at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The 'meeting preparation' framing carves a clear niche distinct from generic calendar/drive skills, but there is minor overlap risk with the closely related sibling gog-calendar and gog-drive skills it references, fitting anchor 4 ('Mostly distinct; minor overlap risk with closely related skills').	4 / 5
	Total	13 / 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-meeting-prep/SKILL.md
Commit: eb85a99

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.