CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-forms

Google Forms through gog. Use for Google Forms structure, questions, responses, and watches.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

An exemplary lean CLI skill: executable safe-start commands, a crisp command table, explicit write-safety validation, and clean structure that delegates detail to the CLI's own help and schema. The only improvement space is a worked example of a typical operation and brief error-recovery guidance.

DimensionReasoningScore

Conciseness

The body is lean and operational throughout — a three-command safe-start block, a compact command table, and pointers to '--help' and 'schema' — with no explanation of concepts Claude already knows and no padding, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The safe-start commands ('gog auth list --check --json --no-input', 'gog schema forms --json') are copy-paste executable and the command table is concrete, but no worked example of an actual operation (e.g., 'gog forms get <form-id> --json') is shown — syntax is deferred to '--help' — leaving minor gaps versus the fully executable anchor 5.

4 / 5

Workflow Clarity

The safe-start sequence is clear and write validation is explicit ('--dry-run' before supported writes, 'Confirm the exact account, object, and mutation before any write or delete'), satisfying the destructive-operation cap. However, no error-recovery/feedback loop or end-to-end example flow (get → modify → verify) is given, placing it between anchors 4 and 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for bundle files and is well-organized into clear sections (Safe start, Commands), meeting the rubric's simple-skill criterion for a 5. Its single reference ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules') is one level deep and clearly signaled, and detailed syntax is delegated to CLI-native disclosure via '--help' and 'schema --json'.

5 / 5

Total

18

/

20

Passed

Description

73%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.

A concise, well-targeted description with an explicit use-when clause and strong distinctiveness. Its main weakness is that it lists coverage areas as nouns rather than concrete action verbs, leaving the 'what' terser than ideal.

Suggestions

Replace or augment the noun list with action verbs, e.g., 'Create and update forms, add and reorder questions, fetch and analyze responses, and manage response watches.'

Add common user synonyms such as 'survey' or 'quiz' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Google Forms through gog') and concrete coverage areas ('structure, questions, responses, and watches'), but these are nouns rather than the specific action verbs (e.g., create, update, analyze) that anchor 4 requires, so it matches anchor 3: domain plus limited concrete actions, not comprehensive.

3 / 5

Completeness

Both parts are present: 'Google Forms through gog' states what it does and 'Use for Google Forms structure, questions, responses, and watches' is an explicit when-clause. The 'what' is terse and could more explicitly state the operations performed, matching anchor 4 rather than the fully concrete anchor 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say — 'Google Forms', 'questions', 'responses', 'watches' — giving good keyword coverage, though common variations like 'survey' or 'quiz' are missing, which keeps it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Google Forms through gog' carves out a clear niche tied to a specific product and CLI, with trigger terms ('Google Forms', 'responses', 'watches') that are unlikely to fire for other skills, matching the clear-niche anchor with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

openclaw/gogcli

Path

.agents/skills/gog-forms/SKILL.md

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.