gws-classroom

Google Classroom: Manage classes, rosters, and coursework.

Quality

37%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-classroom/SKILL.md

Quality

Discovery

40%

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 benefits from naming a specific platform (Google Classroom), which gives it strong distinctiveness. However, it is too brief—it lacks a 'Use when...' clause, provides only high-level action categories rather than concrete operations, and misses common trigger terms users would naturally use when requesting help with Google Classroom tasks.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Google Classroom, creating or managing assignments, enrolling students, or grading coursework.'

Expand the capability list with more specific concrete actions, e.g., 'Create and manage classes, enroll students, post assignments, distribute materials, review and grade submissions.'

Include additional natural trigger terms users might say, such as 'assignments', 'students', 'grades', 'enroll', 'course materials', or 'Google Classroom API'.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Classroom) and some actions ('manage classes, rosters, and coursework'), but these are fairly high-level categories rather than specific concrete actions like 'create assignments, enroll students, grade submissions'.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also quite thin, placing this at a 1.	1 / 3
Trigger Term Quality	Includes 'Google Classroom', 'classes', 'rosters', and 'coursework' which are relevant keywords, but misses common variations users might say like 'assignments', 'students', 'grades', 'course', 'classroom API', or 'enroll'.	2 / 3
Distinctiveness Conflict Risk	'Google Classroom' is a very specific product/platform, making this clearly distinguishable from other skills and unlikely to conflict with unrelated skills.	3 / 3
	Total	8 / 12 Passed

Implementation

35%

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

This skill is essentially an API reference dump with verbose error code descriptions that waste tokens without adding actionable value. It lacks concrete usage examples showing real commands with flags/params, and the extensive method descriptions repeat standard REST error patterns Claude already understands. The 'Discovering Commands' section is the strongest part but is insufficient on its own.

Suggestions

Remove all inline error code descriptions (PERMISSION_DENIED, NOT_FOUND, etc.) — these are standard REST patterns Claude already knows, and they consume a large portion of the token budget.

Add 2-3 concrete, copy-paste-ready examples showing common workflows (e.g., creating a course, listing students, creating coursework) with actual --params and --json flags.

Add a brief workflow for common multi-step operations like 'Create course → Add students → Create assignment' with validation steps (e.g., verify course was created before adding students).

Condense the API resource listing to a compact table or brief list of resource.method pairs, moving verbose descriptions to a separate reference file if needed.

Dimension	Reasoning	Score
Conciseness	The content is bloated with verbose API error code descriptions that Claude doesn't need (e.g., 'This method returns the following error codes: * PERMISSION_DENIED if the requesting user is not permitted to...'). These are standard REST API error patterns that add no actionable value and waste significant token budget.	1 / 3
Actionability	The skill provides the CLI syntax pattern and a useful 'Discovering Commands' section with concrete commands (gws schema, --help), but lacks any concrete usage examples showing actual course creation, listing, or management with real flags and parameters.	2 / 3
Workflow Clarity	There's a basic two-step workflow implied (discover with gws schema, then call the method), but no explicit multi-step workflows for common tasks like creating a course and adding students, and no validation checkpoints for operations like deleting courses.	2 / 3
Progressive Disclosure	The prerequisite reference to ../gws-shared/SKILL.md is good progressive disclosure, but the main content is a monolithic listing of all API resources and methods with verbose descriptions that could be better organized or referenced externally. Sub-resources like 'aliases', 'announcements', etc. are mentioned but not linked to any detail.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: a3768d0

Reviewed: about 1 month 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.