CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gog-appscript

Apps Script through gog. Use for Apps Script projects, source files, deployments, and executions.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-appscript/SKILL.md
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.

The body is an exemplary lean CLI reference: executable discovery commands, a scannable command table, and explicit mutation-safety rules. Its main gap is the absence of worked example invocations for the most common operations and any error-recovery guidance.

Suggestions

Add one worked example per high-frequency command, e.g., 'gog appscript pull <projectId> --account user@example.com' and 'gog appscript run <projectId> <functionName>'.

Include a brief validate-fix-retry loop for failed executions or writes (e.g., re-check 'gog schema appscript run --json' output before retrying).

Clarify how errors from 'gog appscript run' are surfaced (exit codes / --json error fields) so failures are actionable.

DimensionReasoningScore

Conciseness

The body is a lean reference card: executable safe-start commands, a terse command table, and one-line safety rules with zero padding or explanation of concepts Claude already knows. This matches anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place'); the only near-noise is the generator comment, which is not enough to drop to 4.

5 / 5

Actionability

The safe-start block gives copy-paste-ready commands and the closing lines give a concrete discovery pattern ('gog appscript <command> --help', 'gog schema appscript <command> --json'), matching anchor 4 ('Mostly executable guidance... minor gaps'). It falls short of anchor 5 because common tasks like pulling a project or running a function lack a worked example invocation with arguments.

4 / 5

Workflow Clarity

The safe-start section gives a coherent ordered sequence and mutation checkpoints are explicit ('--dry-run before supported writes', 'Confirm the exact account, object, and mutation before any write or delete'), fitting anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps'). It is not 5 because there is no validate-fix-retry feedback loop for failed runs or writes.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and no bundle files to disclose; its single reference ('Read ../gog/SKILL.md first for shared auth, output, safety, and live-write rules') is clearly signaled and one level deep. Per the simple-skill guideline this matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

57%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 has an explicit and appropriate trigger clause and occupies a distinct niche, but it never states what operations the skill performs. Adding a few concrete verbs (create, pull, run, deploy) would lift both specificity and completeness.

Suggestions

State the concrete actions, e.g., 'Create, pull, inspect, and deploy Apps Script projects, and run deployed functions through the gog CLI.'

Add natural synonyms such as 'Google Apps Script', 'Apps Script functions', and '.gs files' to improve trigger term coverage.

Replace the generic 'projects, source files' phrasing with Apps Script-specific terms to reduce overlap with sibling gog skills.

DimensionReasoningScore

Specificity

The description names the domain ('Apps Script through gog') but contains no concrete action verbs — the 'Use for' clause lists objects ('projects, source files, deployments, and executions') rather than what the skill does with them, matching the anchor 'Names the domain but actions are minimal or generic'. It falls below anchor 3 because no 1-2 concrete actions (e.g., create, deploy, run) are stated.

2 / 5

Completeness

Both parts are present: a 'what' ('Apps Script through gog') and an explicit 'when' ('Use for Apps Script projects, source files, deployments, and executions'). It fits anchor 4 ('both what and when; when could be more explicit or specific') rather than 5 because the 'what' states no concrete operations, and not 3 because the 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

'Apps Script', 'deployments', and 'executions' are terms users would naturally say, but common variations such as 'Google Apps Script', 'Apps Script functions', or file extensions like '.gs' are missing. This matches 'Some relevant keywords but missing common variations or synonyms' rather than anchor 4's 'Good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'Apps Script' is a clear, distinct niche with minimal conflict risk against unrelated skills. It sits at anchor 4 ('Mostly distinct; minor overlap risk') rather than 5 because the generic trailing terms 'projects' and 'source files' could collide with other project- or source-oriented skills in the same CLI family.

4 / 5

Total

13

/

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-appscript/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.