Name: google-calendar
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

google-calendar

Google Calendar integration. Manage communication data, records, and workflows. Use when the user wants to interact with Google Calendar data.

Quality

66%

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

Quality

Content

75%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 body is highly actionable, packed with executable Membrane CLI commands and a well-validated connection workflow with polling feedback loops. Its main weaknesses are an unnecessary opening explanation of what Google Calendar is and a monolithic single-file structure that could offload reference material.

Suggestions

Delete the opening paragraph explaining what Google Calendar is; Claude already knows this and it pads the token budget.

Resolve the dangling "skip to Step 2" reference by explicitly labeling the subsequent steps (e.g. Step 2: Search for actions).

Consider moving the Popular actions table and proxy flag reference into a separate reference file to improve progressive disclosure and keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, useful CLI reference, but it opens by explaining what Google Calendar is ("Google Calendar is a time-management and scheduling application...") and includes prose like "so you can focus on the integration logic rather than auth plumbing" that Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with clearly explained placeholders, plus a Popular actions table and proxy flag table that cover the common cases.	5 / 5
Workflow Clarity	The connection setup is a clear sequence with explicit validation (state checks: READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops (poll until ready, re-poll after user action), but the dangling "skip to Step 2" reference with no labeled Step 2 and the lack of a unified numbered flow are minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no broken or nested references, though at ~148 lines it is a single monolithic file with the action and flag reference tables inlined rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

57%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 correctly names the product and includes an explicit 'Use when' trigger, but its capability statement is generic and it omits the natural calendar vocabulary (events, scheduling) users would actually say. It is distinct enough to avoid most conflicts yet could be sharper.

Suggestions

Replace "Manage communication data, records, and workflows" with concrete calendar actions, e.g. "Create and list events, manage calendars, and query free/busy information."

Add natural trigger terms users say, such as "events", "scheduling", "appointments", or "meetings", to the 'Use when' clause.

Tighten the 'when' clause to reference specific scenarios, e.g. "Use when the user wants to create or manage calendar events, check availability, or list calendars."

Dimension	Reasoning	Score
Specificity	The phrase "Manage communication data, records, and workflows" names the Google Calendar domain but the actions are minimal and generic, with no concrete operations like creating events or listing calendars; "communication data" is also an odd fit for a calendar.	2 / 5
Completeness	It states a 'what' ("Google Calendar integration. Manage communication data, records, and workflows") and an explicit 'when' ("Use when the user wants to interact with Google Calendar data"), but the 'what' is generic and the 'when' could name concrete triggers, keeping it below a 5.	4 / 5
Trigger Term Quality	"Google Calendar" is the natural product keyword users would say, but common synonyms and variations users actually use (events, scheduling, calendar, appointments, meetings) are absent, so coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	The trigger "interact with Google Calendar data" is clearly niche-specific, but the broad phrase "Manage communication data, records, and workflows" risks minor overlap with other Google Workspace or communication-integration skills.	4 / 5
	Total	13 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/google-calendar/SKILL.md
Commit: f484c82

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