CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-calendar

Google Calendar through gog. Use for calendars, events, availability, and scheduling; use gog-meeting-prep for meeting briefings or gog-weekly-digest for a cross-service summary.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

An exemplary lean command-reference skill: executable safe-start commands, a complete command table, explicit write-safety rules, and detail correctly deferred to --help/schema rather than bundled. The only gap is the lack of an explicit post-write verification or error-recovery step in the workflow.

DimensionReasoningScore

Conciseness

Every line is a command, flag, or safety rule; there is zero padding or explanation of concepts Claude already knows (no 'what Google Calendar is' prose). The 28-row command table is dense reference, not verbosity — matches 'every token earns its place'.

5 / 5

Actionability

The 'Safe start' block is copy-paste-ready with exact flags (--json --wrap-untrusted, --readonly, --no-input), and 'Run gog calendar <command> --help ... gog schema calendar <command> --json' plus 'Do not guess command syntax' gives a deterministic way to obtain exact executable syntax for every listed command. This discovery-based pattern covers the common cases as fully as inlined examples would.

5 / 5

Workflow Clarity

The safe-start sequence (auth check → schema → readonly read) and safety bullets (--dry-run before writes, 'Confirm the exact account, object, and mutation before any write or delete') provide the key checkpoints for destructive operations, so the destructive-cap applies neither. It falls short of 5 only because there is no post-write verification or error-recovery loop (e.g. re-reading an event after create).

4 / 5

Progressive Disclosure

Clean overview structure: the only file reference is the clearly signaled, one-level-deep 'Read ../gog/SKILL.md first', and per-command detail is delegated to --help/schema rather than inlined. Sections are well organized and the skill needs no bundle files — matching the under-50-lines exception for well-organized single-purpose skills.

5 / 5

Total

19

/

20

Passed

Description

68%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.

A concise, well-scoped description with an explicit 'Use for' trigger clause and excellent sibling-skill disambiguation. Its main weakness is the absence of concrete action verbs — what operations (create, list, update, delete events) the skill performs is left entirely implied.

Suggestions

Add 2-3 concrete capability verbs, e.g. 'Create, update, and delete events, check availability, and manage calendars through gog' — this would lift specificity from naming the domain to listing real actions.

Include common synonyms such as 'meetings', 'appointments', or 'invites' in the trigger clause to catch more natural user phrasings.

Consider mentioning free/busy or scheduling-conflict checks explicitly, since 'availability' alone may not trigger for users asking 'when am I free'.

DimensionReasoningScore

Specificity

The description names the domain and tool ("Google Calendar through gog") but lists no concrete actions — phrases like "Use for calendars, events, availability, and scheduling" name objects, not operations (no create/list/update events verbs). This matches the anchor 'Names the domain but actions are minimal or generic' rather than 3, which requires 1-2 explicit actions.

2 / 5

Completeness

Both parts are present: what = "Google Calendar through gog" and when = the explicit "Use for calendars, events, availability, and scheduling" clause. It sits at anchor 4 rather than 5 because the 'what' doesn't enumerate concrete capabilities and the trigger phrases, while explicit, are a bare object list.

4 / 5

Trigger Term Quality

"calendars, events, availability, and scheduling" plus "Google Calendar" are natural terms users would say, giving good keyword coverage. Score 5 requires synonyms/extensions like 'meetings', 'appointments', 'invites', or 'free/busy', which are absent.

4 / 5

Distinctiveness Conflict Risk

"use gog-meeting-prep for meeting briefings or gog-weekly-digest for a cross-service summary" actively routes ambiguous cases away, and "Google Calendar" is a clear niche with distinct triggers — minimal conflict risk, matching the top anchor.

5 / 5

Total

15

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-calendar/SKILL.md

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.