gog-classroom

Google Classroom operations through gog.

Quality

60%

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

80%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 efficient, actionable overview with concrete safe-start commands and a clean command table, well-structured for a simple skill. Its main gap is the absence of an explicit validate->fix->retry feedback loop for destructive Google writes, which caps workflow clarity.

Suggestions

Add a short explicit feedback loop for writes/deletes, e.g. run with --dry-run, inspect the planned mutation, then execute and re-verify the resulting object via a read command.

Show one or two concrete per-command examples (e.g. listing courses, posting an announcement) instead of deferring entirely to --help, to raise actionability.

Optionally add a one-line 'Verify' checkpoint after the safe-start block confirming the account and schema resolved before proceeding.

Dimension	Reasoning	Score
Conciseness	The body is lean: a short pointer to ../gog/SKILL.md, three copy-paste safe-start commands, terse safety bullets, and a compact command table, with no explanations of concepts Claude already knows. It matches 'Lean and efficient; assumes Claude's competence; every token earns its place'. It is not a 4 because there are no noticeable instances of over-explanation to trim.	5 / 5
Actionability	The safe-start block gives concrete, copy-paste-ready commands and the command table plus the explicit 'run --help / schema --json, do not guess' guidance is executable. It is not a 5 because per-command common-case examples are deferred to --help rather than shown inline, a minor gap; it is not a 3 because the guidance is real executable commands, not pseudocode.	4 / 5
Workflow Clarity	A clear safe-start sequence and explicit safety checkpoints exist ('Confirm the exact account, object, and mutation before any write or delete', '--dry-run', '--readonly'), but there is no explicit validate->fix->retry feedback loop. Per the rubric, a destructive/batch-capable skill missing such feedback loops is capped at 3. It is not a 4 because the recovery loop is absent, and not a 2 because checkpoints are explicitly present rather than missing.	3 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections (Safe start, Commands) and a single clearly-signaled one-level reference ('Read ../gog/SKILL.md first'); no bundle files exist to nest. This matches the simple-skill exception allowing a 5 with well-organized sections. It is not a 4 because structure and signaling are clean with no organization gaps.	5 / 5
	Total	17 / 20 Passed

Description

40%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 correctly names a distinct niche (Google Classroom via gog) but is too vague on capabilities and entirely lacks a Use-when trigger clause, capping its completeness and specificity. It is distinguishable but under-specified for confident skill selection.

Suggestions

Replace the generic word 'operations' with 2-4 concrete actions (e.g. 'create courses, post announcements, manage coursework and student submissions').

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when the user asks to manage Google Classroom courses, announcements, coursework, or rosters').

Include natural synonyms/file-context terms users might say (e.g. 'class', 'assignment', 'student submission') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Google Classroom operations' names the domain but the only action word is the generic 'operations', matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no concrete actions (e.g. create courses, post announcements) are listed, and not a 1 because the domain is explicitly named.	2 / 5
Completeness	The description gives a vague 'what' ('operations') and entirely omits a 'when'/'Use when...' clause, matching 'Has a vague what and no when'. Per the rubric guideline, the missing Use-when clause caps completeness at 3 at most, and the vague what pulls it to 2; it is not a 3 because the 'what' is not clearly stated.	2 / 5
Trigger Term Quality	'Google Classroom' is a natural term users actually say, but it is the only such keyword; 'operations' is generic and 'gog' is tool jargon, so synonyms/variations are missing. It is not a 4 because no additional natural phrases or synonyms appear, and not a 2 because 'Google Classroom' is a genuinely natural user term rather than generic language.	3 / 5
Distinctiveness Conflict Risk	'Google Classroom' is a clear, specific niche with minimal conflict risk, only minor overlap with sibling Google Workspace skills. It is not a 5 because no explicit trigger phrase ('Use when...') is present, and not a 3 because the domain is far more specific than generic document/file skills.	4 / 5
	Total	11 / 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: eb85a99

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.