Name: google-meet
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

google-meet

Google Meet integration. Manage Meetings, Recordings. Use when the user wants to interact with Google Meet data.

Quality

73%

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

Quality

Content

72%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 highly actionable with executable commands and clear state-handling, but is held back by inlined API-reference material that should be split into reference files and by a lack of validation checkpoints around the destructive End Active Conference action.

Suggestions

Add an explicit validation/confirmation checkpoint before running destructive actions such as "End Active Conference" (e.g., confirm the meeting code and active state, then verify the result).

Move the Popular Actions table and proxy flag reference into a separate reference file (e.g., references/actions.md) and link to it from SKILL.md to improve progressive disclosure.

Trim motivational and CLI-internals prose (e.g., "so you can focus on the integration logic rather than auth plumbing" and the URL-normalization explanation) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with direct commands and organized headers, but contains minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing", restated best-practice concepts, and CLI-internals prose that could be trimmed.	4 / 5
Actionability	Commands are fully executable and copy-paste ready across install, auth (including headless), connection, action search/run, and proxy flows, with a populated actions table and flag reference covering the common cases.	5 / 5
Workflow Clarity	The connect-and-poll sequence with state branching (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) is coherent, but the skill exposes a destructive action ("End Active Conference") with no validation or verification checkpoint before execution, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Section headers and tables give structure, but no bundle files exist and substantial reference-style content (the 13-row Popular Actions table and proxy flag table) is inlined in SKILL.md with no one-level-deep references, so it is not yet well split.	3 / 5
	Total	15 / 20 Passed

Description

73%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 identifies a distinct niche and provides both a what and a when, but its action list is shallow ("Manage Meetings, Recordings") and the trigger clause is generic. Strengthening the concrete actions and trigger phrasing would raise it.

Suggestions

Expand the action list beyond "Manage Meetings, Recordings" to concrete operations the skill supports (e.g., list/create/update meeting spaces, list participants, retrieve transcripts and recordings).

Replace the generic "Use when the user wants to interact with Google Meet data" with concrete trigger phrases such as "Use when the user wants to list Google Meet recordings, manage meeting spaces, or retrieve transcripts and participants".

Add common synonyms and variations (video calls, conferences, meeting codes) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Meetings, Recordings" names the Google Meet domain plus two action areas, but "Manage" is generic and only two nouns are listed, leaving coverage non-comprehensive (no spaces, participants, or transcripts).	3 / 5
Completeness	It states the "what" ("Google Meet integration. Manage Meetings, Recordings.") and an explicit "when" ("Use when the user wants to interact with Google Meet data."), but the trigger clause is generic rather than enumerating concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Natural terms like "Google Meet", "Meetings", and "Recordings" appear and would be said by users, but common variations (video calls, conference, transcripts, meeting codes) and the generic "interact with ... data" phrasing leave a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	"Google Meet integration" anchors the skill to a distinct named product with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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-meet/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.