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

google-directory

Google Directory integration. Manage Users, Groups, Roles. Use when the user wants to interact with Google Directory data.

Quality

65%

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

Quality

Content

61%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 mostly actionable with concrete CLI commands and a sensible sequenced workflow. Its main gaps are a concept-explainer intro that pads tokens, and a complete absence of validation/verification steps for destructive directory operations.

Suggestions

Trim the opening 'what is Google Directory' explainer to a single line; assume Claude already knows the product.

Add validation/verification steps after state-changing actions (e.g. re-list a created user or check the command's error output before proceeding).

Provide at least one end-to-end worked example with realistic placeholder values and expected JSON output to lift actionability.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient, command-focused prose, but the opening paragraph explains what Google Directory is ('a service for managing users, groups, and devices...') and there is minor padding ('so you can focus on the integration logic rather than auth plumbing') — explaining concepts Claude already knows, fitting anchor 3.	3 / 5
Actionability	Provides concrete, executable `npx @membranehq/cli@latest` commands with flags, a proxy flag table, and a JSON-input example, with instructions for resolving placeholders; a fully worked end-to-end example with real output is missing, fitting anchor 4.	4 / 5
Workflow Clarity	Steps are sequenced (login, search connector, connect, discover actions, run/proxy) with numbered lists, but there are no validation or verification checkpoints after running actions on Users/Groups/Roles; the destructive/batch-operations cap holds this at anchor 3.	3 / 5
Progressive Disclosure	Single self-contained file (~120 lines) with clear, well-organized section headers and no nested references, good structure with minor organization gaps; it does not split content into separate reference files, fitting anchor 4 rather than the one-level-deep-reference anchor 5.	4 / 5
	Total	14 / 20 Passed

Description

70%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 is well-formed: it states a clear what, includes an explicit 'Use when' trigger, and names a specific product niche. The main weakness is a single generic action verb ('Manage') rather than a richer action vocabulary and the absence of common synonyms like 'Google Workspace'.

Suggestions

Replace or expand the generic verb 'Manage' with several concrete actions (e.g. 'Create, update, list, and delete Users, Groups, and Roles').

Add natural synonyms users say, such as 'Google Workspace' or 'G Suite admin directory', to broaden trigger coverage.

Sharpen the 'when' clause with concrete scenarios, e.g. 'Use when managing employees, group memberships, or role assignments in a Google Workspace org'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Google Directory') and concrete managed entities ('Users, Groups, Roles') but uses a single generic verb ('Manage') rather than several distinct actions, fitting anchor 3 ('Names domain and 1-2 concrete actions') better than anchor 4 which expects multiple distinct action verbs.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage Users, Groups, Roles') and 'when' ('Use when the user wants to interact with Google Directory data'); the 'when' clause is present but somewhat generic, matching anchor 4 rather than the maximally specific anchor 5.	4 / 5
Trigger Term Quality	Includes the primary natural term 'Google Directory' plus entity keywords ('Users, Groups, Roles') and an explicit 'Use when' phrase; a few natural synonyms users might say (e.g. 'Google Workspace', 'G Suite admin') are missing, matching anchor 4.	4 / 5
Distinctiveness Conflict Risk	Targets a specific named product niche ('Google Directory') with distinct triggers, but 'Manage Users, Groups, Roles' and 'interact with... data' carry minor overlap risk with a broader Google Workspace/IAM skill, fitting anchor 4 rather than the minimal-conflict anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/google-directory/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.