google-calendar

Google Calendar via gws: list events, create, accept, find free time.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google/google-calendar/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

The content is highly actionable with executable commands and clearly sequenced workflows, but it is somewhat redundant and monolithic where splitting detailed references would improve navigation.

Suggestions

De-duplicate the Rules section by removing rules 3, 4, 7, and 10, which restate the RSVP, RFC 3339, singleEvents, and inline-preview guidance already in the body.

Move the calendar-block format specification and the calendar-list/ACL reference into separate reference files linked from a concise overview, enabling one-level-deep progressive disclosure.

Tighten the prerequisites setup flow, which repeats the 'ask before setting up' pattern across several bullets.

Dimension	Reasoning	Score
Conciseness	The body largely assumes Claude's competence and adds gws-specific knowledge, but the Rules section restates material already covered in detail (rules 3, 4, 7, 10 duplicate the RSVP, RFC 3339, singleEvents, and preview-block sections), so it could be tightened.	2 / 3
Actionability	It provides abundant copy-paste-ready, fully executable `gws calendar` commands with exact `--params` JSON bodies and complete examples, matching the score-3 anchor.	3 / 3
Workflow Clarity	Multi-step processes like RSVP are clearly sequenced as numbered steps with rationale, and the prerequisites flow includes explicit error-recovery feedback loops (scope required, 401, ENOENT), satisfying the score-3 anchor.	3 / 3
Progressive Disclosure	The body is well-organized into sections but monolithic at ~226 lines with no bundle files; content such as the calendar-block format spec and ACL details is inline that could be split into references, and the under-50-line simple-skill exception does not apply.	2 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific and well-scoped to Google Calendar, but it omits an explicit 'when to use' trigger clause and only partially covers the natural terms a user would say.

Suggestions

Add an explicit 'Use when...' clause naming trigger situations (e.g. scheduling meetings, RSVPing to invites, finding free slots).

Broaden trigger terms to include 'meeting', 'schedule', 'invite', and 'RSVP' alongside 'events' and 'free time'.

Clarify that 'accept' refers to meeting invites so the verb reads as a natural user term.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'list events, create, accept, find free time' — matching the score-3 anchor of several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'Google Calendar', 'events', and 'free time' are natural user terms, but common variations like 'meeting', 'schedule', 'invite', and 'RSVP' are missing, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	'Google Calendar via gws' carves a clear, narrow niche unlikely to trigger for unrelated skills, matching the score-3 distinct-trigger anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Open-Curiosity/gini-agent
Path: skills/google/google-calendar/SKILL.md
Commit: 6c5d85e

Reviewed: 12 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.