gws-apps-script-push

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

Install with Tessl CLI

npx tessl i github:googleworkspace/cli --skill gws-apps-script-push

What are skills?

1.63x

Quality

63%

Does it follow best practices?

Impact

100%

1.63x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-apps-script-push/SKILL.md

SKILL.md

Review

Evals

Discovery

40%

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 identifies a specific domain (Google Apps Script) and a clear action (uploading files), giving it reasonable distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural keywords users might say. The missing 'when' clause significantly limits Claude's ability to know when to select this skill.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to push code to Google Apps Script, deploy scripts, or sync local .gs/.js files to a GAS project'

Include common variations and natural terms users might say: 'GAS', 'clasp push', 'deploy script', '.gs files', 'script editor'

Expand the action list to be more comprehensive: 'Upload, sync, and deploy local JavaScript/TypeScript files to Google Apps Script projects'

Dimension	Reasoning	Score
Specificity	Names the domain (Google Apps Script) and one action (upload local files), but lacks comprehensive coverage of what uploading entails or additional capabilities.	2 / 3
Completeness	Describes what it does (upload files to Apps Script) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'Google Apps Script', 'upload', 'local files', and 'Apps Script project' which are relevant, but misses common variations like 'GAS', 'clasp', 'push', 'deploy', or '.gs files'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google Apps Script' and 'upload local files to an Apps Script project' creates a clear, specific niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, concise skill that provides clear, actionable guidance for the push command. The main weakness is the lack of validation/verification steps for what is explicitly marked as a destructive operation that replaces all project files. The structure and progressive disclosure are excellent.

Suggestions

Add a verification step after push (e.g., 'Verify upload succeeded by checking the script editor or running `gws apps-script +list-files --script SCRIPT_ID`')

Consider adding a pre-push checklist or confirmation pattern given the destructive nature of replacing all files

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations of what Apps Script is or how file uploads work. Every line serves a purpose - flags, examples, and critical warnings only.	3 / 3
Actionability	Provides complete, copy-paste ready commands with clear flag documentation. The examples show both basic and directory-specific usage patterns that are immediately executable.	3 / 3
Workflow Clarity	For a destructive write operation that 'replaces ALL files in the project', the skill lacks explicit validation/verification steps. The caution warning is present but no feedback loop for confirming success or recovering from errors.	2 / 3
Progressive Disclosure	Excellent structure with clear prerequisite reference, well-organized sections, and appropriate 'See Also' links to related skills. References are one level deep and clearly signaled.	3 / 3
	Total	11 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

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