gog-classroom

Google Classroom operations through gog.

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 ./.agents/skills/gog-classroom/SKILL.md

Quality

Content

86%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 an exemplary lean CLI skill card: executable safe-start commands, explicit safety gates (readonly, dry-run, account confirmation) for destructive operations, a scannable subcommand table, and disciplined offload of syntax details to --help/schema. The only notable gap is the absence of even one worked usage example for the most common operations.

Dimension	Reasoning	Score
Conciseness	Every line is operational: three safe-start commands, flag rules, a compact command table, and "Run `gog classroom <command> --help`... Do not guess command syntax." There is no concept explanation or padding, matching the anchor 'lean and efficient; every token earns its place'.	5 / 5
Actionability	The safe-start commands (e.g. `gog auth list --check --json --no-input`, `gog schema classroom --json`) are copy-paste ready and the command table names real subcommands, but no worked examples for common operations (list courses, post an announcement) are given — those are delegated to --help and schema. This fits 'mostly executable guidance; concrete commands with minor gaps' rather than the fully example-covered level 5.	4 / 5
Workflow Clarity	There is a clear safe-start sequence with real validation checkpoints for risky operations — "Use `--dry-run` before supported writes" and "Confirm the exact account, object, and mutation before any write or delete" — so the missing-validation cap does not apply. It falls short of 5 because no explicit feedback loop (dry-run, review output, then execute) or error-recovery step is described.	4 / 5
Progressive Disclosure	The body is under 50 lines and well organized into Safe start / Commands sections; its one external reference ("Read `../gog/SKILL.md` first for shared auth, output, safety, and live-write rules") is clearly signaled and one level deep, and per-command detail is appropriately offloaded to `--help` and `gog schema` rather than inlined.	5 / 5
	Total	18 / 20 Passed

Description

48%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 identifies a specific, distinctive product domain but relies on the single generic action word "operations" and omits any 'when to use' guidance or natural trigger phrases (courses, assignments, students). It is concise but under-specified relative to the rubric's good examples, which pair a concrete action list with an explicit trigger clause.

Suggestions

Enumerate concrete capabilities in the description, e.g. "List courses and rosters, post announcements, manage coursework and student submissions, and handle guardian invitations via gog".

Add an explicit trigger clause, e.g. "Use when the user mentions Google Classroom, courses, assignments, announcements, students, teachers, or guardians".

Include natural user synonyms and product vocabulary (coursework, homework, submissions, roster) so the skill triggers on the phrases users actually say rather than only the product name.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Google Classroom operations") but the only action is the generic word "operations", matching the anchor 'names the domain but actions are minimal or generic'. No concrete capabilities (courses, announcements, coursework, guardians) are listed, so it cannot reach 3.	2 / 5
Completeness	The 'what' is stated ("Google Classroom operations through gog") but there is no 'Use when...' clause or any trigger guidance, which per the judging guidelines caps completeness at 3. It cannot score 4 because the 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"Google Classroom" is a natural term users would say, but it is the only one; common variations like courses, assignments, students, or guardians are absent, and "gog" alone is internal jargon. This fits 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	"Google Classroom" carves out a clear niche distinct from sibling gog skills (drive, gmail), leaving only minor overlap risk with closely related Google-suite skills. It falls short of 5 because "operations through gog" does not by itself distinguish it from other gog-family skills.	4 / 5
	Total	12 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openclaw/gogcli
Path: .agents/skills/gog-classroom/SKILL.md
Commit: 414e2ff

Reviewed: 3 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.