recipe-deploy-apps-script
Push local files to a Google Apps Script project.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-deploy-apps-script65
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 platform (Google Apps Script) but is too terse to be effective for skill selection. It lacks explicit trigger guidance ('Use when...'), comprehensive action coverage, and natural keyword variations that users would employ when needing this functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Apps Script', 'GAS', 'clasp push', 'deploy script', 'upload to Google'
Expand the action list to include related capabilities such as 'sync local .js/.gs files', 'deploy Apps Script projects', or 'update script code'
Include file type triggers like '.gs files', 'script files', or mention the clasp CLI tool if applicable
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Apps Script) and one action (push local files), but lacks comprehensive coverage of what this entails - doesn't mention syncing, deployment, or specific file types handled. | 2 / 3 |
Completeness | Only addresses 'what' (push files to Apps Script) but completely lacks any 'when' clause or explicit trigger guidance. Per rubric guidelines, missing 'Use when...' should cap at 2, but this also has a weak 'what'. | 1 / 3 |
Trigger Term Quality | Includes 'Google Apps Script' and 'push' which are relevant, but misses common variations users might say like 'GAS', 'clasp', 'deploy script', 'upload to Apps Script', or 'sync files'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Apps Script' provides some specificity, but 'push local files' is generic enough to potentially conflict with other deployment or file sync skills. Could overlap with general Git push or other cloud sync tools. | 2 / 3 |
Total | 7 / 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 actionable CLI commands for deploying Apps Script projects. The main weakness is the lack of validation steps between updating content and creating a version - there's no guidance on verifying the update succeeded or handling potential errors in the deployment workflow.
Suggestions
Add a validation step after updateContent to verify the push succeeded (e.g., re-fetch content or check response)
Include brief error handling guidance for common failure scenarios (e.g., permission errors, invalid JSON)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands without explaining what Apps Script is or how the CLI works. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete parameter examples and JSON payloads that are copy-paste ready with minimal modification (just replacing SCRIPT_ID). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced for the deployment workflow, but lacks validation checkpoints - no verification that updateContent succeeded before creating a version, no error handling guidance. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. The prerequisite skill reference is clear and one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%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
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.