gog-forms

Google Forms operations through gog.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-forms/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 exceptionally lean, well-structured overview that points to the shared gog skill and to per-command --help/schema contracts for detail rather than inlining it. Actionability and workflow clarity are strong, with only minor gaps around a complete worked write example and an explicit validate-fix feedback loop.

Suggestions

Add one complete copy-paste example of a safe write (e.g. add-question with --dry-run then the real call) to make actionability fully concrete.

Make the destructive-write feedback loop explicit (e.g. 'After --dry-run, inspect the planned mutation; only then run without --dry-run').

Dimension	Reasoning	Score
Conciseness	The body is lean: a Safe start block, a compact command table, and a closing pointer to --help and schema, with no padding or explanations of concepts Claude already knows. Every token earns its place.	5 / 5
Actionability	The Safe start block gives concrete, executable gog commands and the command table maps names to purposes, but no complete copy-paste example of a representative write operation is given, leaving a minor gap.	4 / 5
Workflow Clarity	The Safe start sequence (auth list -> schema -> readonly help) and the safety bullets (confirm account/object/mutation, --dry-run before writes) provide a clear, mostly checkpointed workflow, but an explicit validate-then-fix feedback loop for destructive writes is only implied rather than stated.	4 / 5
Progressive Disclosure	The skill is a short, well-organized overview with clear sections (Safe start, Commands) and one-level-deep references ('Read ../gog/SKILL.md first', 'Run gog forms <command> --help', 'gog schema forms <command> --json'); no bundle files exist, so the structure is appropriate for a simple skill.	5 / 5
	Total	18 / 20 Passed

Description

70%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 clearly identifies a distinct niche (Google Forms via the gog tool) but stops short of listing concrete actions or providing an explicit 'Use when...' trigger clause, which caps completeness at 3. Adding a trigger sentence would lift the strongest remaining weakness.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural phrases such as 'Google Forms, forms, form questions, form responses'.

Enumerate a few concrete actions in the description (e.g. create forms, add/move/delete questions, read responses) to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the concrete domain (Google Forms operations through gog) and several specific actions are implied by the command list referenced in the body, but the description text itself lists only the domain rather than enumerating concrete actions, leaving minor gaps in coverage.	4 / 5
Completeness	The description clearly states what the skill does ('Google Forms operations through gog') but lacks any explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	'Google Forms operations through gog' surfaces the natural term 'Google Forms' that users would say, and 'gog' names the tool, but common synonyms and natural trigger phrases ('forms', 'form questions', 'form responses') are not enumerated in the description.	4 / 5
Distinctiveness Conflict Risk	'Google Forms operations through gog' carves out a clear niche tied to a specific product and tool, with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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-forms/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.