gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
56
Quality
48%
Does it follow best practices?
Impact
57%
1.20xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-classroom/SKILL.mdDiscovery
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 product (Google Classroom) which provides clear distinctiveness, but it lacks the depth needed for effective skill selection. The actions are too high-level and there's no explicit guidance on when Claude should use this skill, making it difficult to distinguish from other education-related skills in a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Google Classroom, creating assignments, managing student rosters, or grading coursework'
Expand the action list with specific concrete operations like 'create assignments, grade submissions, enroll students, post announcements, manage course materials'
Include natural trigger terms users might say such as 'assignments', 'grades', 'students', 'course materials', or 'classroom API'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Classroom) and mentions some actions ('manage classes, rosters, and coursework'), but these are high-level categories rather than specific concrete actions like 'create assignments', 'grade submissions', or 'enroll students'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this is weaker than that threshold. | 1 / 3 |
Trigger Term Quality | Includes 'Google Classroom', 'classes', 'rosters', and 'coursework' which are relevant, but misses common variations users might say like 'assignments', 'students', 'grades', 'course materials', or 'classroom management'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Classroom' is a specific product name that creates a clear niche. This is unlikely to conflict with other skills since it explicitly targets Google's education platform rather than generic classroom or education tools. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable reference for Google Classroom API resources but is weakened by verbose error code descriptions that add little value and a lack of concrete usage examples. The structure and progressive disclosure are good, but actionability suffers from missing copy-paste-ready examples for common operations.
Suggestions
Add 2-3 concrete examples showing common operations like creating a course, listing students, or adding a teacher with actual --params usage
Remove or significantly condense the error code descriptions from method documentation - Claude understands API error patterns
Add a validation step example for destructive operations like course deletion (e.g., verify course exists before deleting)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes verbose API error code descriptions that Claude doesn't need explained. The resource method descriptions could be trimmed to just the action without the error code details. | 2 / 3 |
Actionability | Provides the basic command structure and discovery commands, but lacks concrete executable examples showing actual usage with real parameters. No example of creating a course, listing students, or other common operations. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic workflow (inspect then call), but there's no validation or error handling guidance. For operations like deleting courses, there should be verification steps. | 2 / 3 |
Progressive Disclosure | Appropriately references the shared skill file for auth and global flags, keeps the main content as an overview of available resources, and uses gws schema for detailed parameter discovery. Well-structured with clear navigation. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 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 |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Reviewed
Table of Contents
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.