gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
49
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-classroom/SKILL.mdQuality
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, create assignments, post announcements, review and grade submissions, manage course materials.'
Include additional natural trigger terms users might say, such as 'assignments', 'students', 'grades', 'enroll', 'course materials', and 'announcements'.
| 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 a verbose API reference dump that reproduces information Claude could discover through the CLI's built-in help. It lacks concrete usage examples with actual flag values, and the extensive error code documentation wastes significant token budget without adding actionable value. The skill would benefit greatly from being condensed to a quick-start with 2-3 concrete examples and letting the CLI's own help system serve as the reference.
Suggestions
Remove the verbose method descriptions and error codes—these are discoverable via `gws classroom --help` and `gws schema`. Replace with a concise resource/method table.
Add 2-3 concrete, copy-paste-ready examples showing common workflows (e.g., creating a course, listing students, creating an assignment) with actual --params flags.
Add a multi-step workflow example for a common task like 'set up a course with students and coursework' with validation checkpoints.
Move the full API resource listing to a separate reference file and keep SKILL.md focused on quick-start patterns and the most common operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely verbose, reproducing full API documentation including error codes and descriptions that Claude already knows or could discover via `gws classroom --help`. The lengthy method descriptions with error code lists are unnecessary padding that wastes token budget. | 1 / 3 |
Actionability | It provides the basic CLI pattern and the `gws schema` discovery command, but lacks any concrete executable examples showing actual usage (e.g., creating a course, listing students, adding coursework with specific --params flags). The guidance is more of a reference catalog than actionable instructions. | 2 / 3 |
Workflow Clarity | The 'Discovering Commands' section provides a basic two-step workflow (browse then inspect), but there are no validation checkpoints, no error recovery guidance, and no multi-step workflow examples for common tasks like managing rosters or creating coursework. | 2 / 3 |
Progressive Disclosure | It references the shared skill file as a prerequisite which is good, and mentions sub-resources, but the massive inline API reference listing should be condensed or moved to a separate file. The content that is inline would be better served by pointing to `gws classroom --help` output. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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
c7c6646
- 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.