gws-script-push

Google Apps Script: Upload local files to an Apps Script project.

Quality

70%

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 ./skills/gws-script-push/SKILL.md

Quality

Content

87%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 content is a tight, fully executable CLI reference with excellent conciseness and actionability. Its main gap is the absence of a verification step after the destructive push, which caps workflow clarity despite the confirm-with-user caution.

Suggestions

Add a post-run verification step, e.g. list project files after push ('gws script +list --script <ID>') or check command exit status, to close the destructive-operation feedback loop.

Show expected success output or an exit-code check so Claude can confirm the upload actually replaced the project files.

Optionally note how to preview/dry-run before the destructive replace, if the CLI supports it.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized (usage, flags table, examples, tips, caution, see-also) with no padding or explanation of concepts Claude already knows, matching 'every token earns its place'.	5 / 5
Actionability	Provides copy-paste-ready commands covering the common cases ('gws script +push --script <ID>' and the '--dir ./src' variant) plus a complete flag table with defaults.	5 / 5
Workflow Clarity	The single action is unambiguous and there is a pre-execution confirm-caution, but this is a destructive write ('replaces ALL files') with no post-run verification/feedback loop, so workflow clarity is capped at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	Under 50 lines with no bundle files needed; sections are well-organized and the only references are one-level-deep sibling SKILL.md links clearly signaled in the prerequisite and See Also sections.	5 / 5
	Total	18 / 20 Passed

Description

53%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 states a single concrete action and names the Apps Script domain, but it lacks an explicit 'Use when' trigger clause and broader keyword coverage (synonyms, file extensions). It is distinct within its niche though adjacent to sibling script-management skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when uploading or deploying local Apps Script files (.gs, .html, appsscript.json) to a Google Apps Script project.'

Include natural synonyms and file extensions users would say, such as '.gs', 'push', and 'deploy', to improve trigger-term coverage.

Consider listing 1-2 more concrete actions (e.g. 'replaces all project files') to lift specificity above a single action.

Dimension	Reasoning	Score
Specificity	Names the domain ('Google Apps Script' / 'Apps Script project') and one concrete action ('Upload local files'), but offers no further actions, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Has a clear 'what' ('Upload local files to an Apps Script project') but no 'Use when...' trigger clause, so per the guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes the natural terms 'Google Apps Script' and 'Apps Script', but omits common variations and file extensions users would say (.gs, 'push', 'deploy', appsscript.json), matching 'some relevant keywords but missing synonyms'.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (uploading to an Apps Script project) with distinct triggers, with only minor overlap risk against sibling gws-script skills (e.g. pull).	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: googleworkspace/cli
Path: skills/gws-script-push/SKILL.md
Commit: a3768d0

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