gog-calendar

Google Calendar operations through gog.

Quality

78%

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

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 a tight, well-structured overview: executable safe-start commands, a complete command table, and explicit safety checkpoints for writes/deletes, with shared rules delegated one level deep to the parent gog skill. It is concise, actionable, and clearly organized.

Dimension	Reasoning	Score
Conciseness	The body is lean: a short intro, a Safe start block, and a compact command table, with no explanation of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Concrete, executable commands with exact flags are given ('gog auth list --check --json --no-input', 'gog --readonly --account user@example.com calendar events --today --json --wrap-untrusted') plus a full command table and pointers to '--help' and 'schema ... --json', making it copy-paste ready.	3 / 3
Workflow Clarity	The Safe start section gives a sequenced onboarding (auth list -> schema -> readonly events) and explicit validation checkpoints for risky operations ('Confirm the exact account, object, and mutation before any write or delete', '--dry-run before supported writes', '--readonly when the task must not mutate'), so destructive-operation validation is present rather than missing.	3 / 3
Progressive Disclosure	Content is well-organized into sections (Safe start, Commands) and points one level deep to '../gog/SKILL.md' for shared rules; no bundle files exist and none are needed for this under-50-line skill, satisfying the simple-skill allowance for a 3.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 a distinct niche (Google Calendar via gog) but is too thin: it uses the vague word 'operations', includes no concrete action list, and lacks any explicit 'Use when' trigger guidance. It is distinguishable but under-specified.

Suggestions

Replace the generic 'operations' with concrete actions, e.g. 'Create, update, delete, and search Google Calendar events; manage calendars, free/busy, and invitations via gog.'

Add an explicit trigger clause, e.g. 'Use when the user asks about Google Calendar events, scheduling, appointments, free/busy, or meeting invitations.'

Include natural trigger variations users say ('events', 'schedule', 'appointments', 'meetings', 'free/busy') rather than relying on the tool name 'gog'.

Dimension	Reasoning	Score
Specificity	Quotes 'Google Calendar operations through gog' — it names a concrete domain and tool but relies on the generic word 'operations' rather than listing concrete actions (create/update/delete events). It is more specific than the score-1 anchor 'Helps with documents' but lacks the multiple concrete actions required for a 3.	2 / 3
Completeness	The phrase 'Google Calendar operations through gog' states a (weak) 'what' but provides no 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2; it is not a 1 because a purpose is named, and not a 3 because 'when' is entirely absent.	2 / 3
Trigger Term Quality	'Google Calendar' is a natural term a user would say, but the description omits common variations users actually use ('events', 'schedule', 'appointments', 'meetings') and 'gog' is tool jargon, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'Google Calendar' is a clear, single-product niche that is unlikely to trigger for sibling gog skills (contacts, drive, etc.), matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

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

Reviewed: 1 day 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.