apps-script-clasp-workflow skill
Documents the clasp CLI workflow for Google Apps Script projects — login, project creation/cloning, push vs deploy, versioning, and multi-environment (dev/staging/prod) setups. Use when setting up CI/CD for an Apps Script project, publishing a new version, or switching between multiple script IDs. Framework-agnostic — applies with or without bootgs. Not for Marketplace listing and review (`apps-script-marketplace-publish`), nor for why a trigger isn't firing (`apps-script-triggers`).
- GitHub stars
- 5
- Files
- 1
- Last commit
- Sep 22, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the apps-script-clasp-workflow skill do?
apps-script-clasp-workflow documents the clasp CLI workflow for Google Apps Script projects — login, project creation/cloning, push vs deploy, versioning, and multi-environment (dev/staging/prod) setups. Use when setting up CI/CD for an Apps Script project, publishing a new version, or switching between multiple script IDs. Framework-agnostic — applies with or without bootgs. Not for Marketplace listing and review (`apps-script-marketplace-publish`), nor for why a trigger isn't firing (`apps-script-triggers`).
How to install the apps-script-clasp-workflow skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the apps-script-clasp-workflow skill in Plugin
/plugin marketplace add bootgs/skills /plugin install apps-script@bootgs-skills
Install the apps-script-clasp-workflow skill in Claude Code
~/.claude/skills/apps-script-clasp-workflow/SKILL.md
$ npx degit bootgs/skills/skills/apps-script-clasp-workflow ~/.claude/skills/apps-script-clasp-workflowInstall the apps-script-clasp-workflow skill in Claude Code (project)
.claude/skills/apps-script-clasp-workflow/SKILL.md
$ npx degit bootgs/skills/skills/apps-script-clasp-workflow .claude/skills/apps-script-clasp-workflowInstall the apps-script-clasp-workflow skill in Codex
~/.agents/skills/apps-script-clasp-workflow/SKILL.md
$ npx degit bootgs/skills/skills/apps-script-clasp-workflow ~/.agents/skills/apps-script-clasp-workflowInstall the apps-script-clasp-workflow skill in Gemini CLI
~/.gemini/skills/apps-script-clasp-workflow/SKILL.md
$ npx degit bootgs/skills/skills/apps-script-clasp-workflow ~/.gemini/skills/apps-script-clasp-workflowInstall the apps-script-clasp-workflow skill in Claude.ai
npx degit bootgs/skills/skills/apps-script-clasp-workflow apps-script-clasp-workflow && zip -r apps-script-clasp-workflow.zip apps-script-clasp-workflow # claude.ai → Customize → Skills → + → Create skill → Upload a skill → apps-script-clasp-workflow.zip
SKILL.md
View on GitHubApps Script clasp Workflow
Auth
clasp login # interactive, opens a browser
clasp login --no-localhost # headless/CI — prints a URL to visit, then paste the resulting code back
Produces ~/.clasprc.json. In CI, inject this file from a secret — never commit it; it's a live OAuth credential.
Project setup
clasp create --type standalone --title "My Project" # new project
clasp clone <scriptId> # existing project
.clasp.json fields that matter:
| Field | Purpose |
|---|---|
scriptId |
Target Apps Script project — the single most important field to get right per environment (see Multi-environment below) |
rootDir |
Directory clasp pushes from, e.g. "./dist/appsscript" — point it at your build output, not source, if you bundle |
filePushOrder |
Files pushed first, before the rest — appsscript.json is commonly listed here since manifest changes should land before code that depends on new scopes/services |
Push vs. deploy — the distinction that causes silent "my fix isn't live" bugs
clasp pushupdates the project's HEAD (the editor/dev version). Anyone opening the script editor sees it immediately. It does not affect any existing versioned deployment.clasp deploycreates or updates a versioned deployment with a stable URL/ID. A web app or add-on installed by end users runs whatever version its deployment points at — pushing new code does nothing for them until you deploy.
clasp push -f # force push, skip the interactive diff/overwrite prompt — needed for CI
clasp push --watch # dev loop: push on every local file change
clasp deploy -i <deploymentId> -d "Fix widget sorting" # update an existing deployment
clasp deployments # list deployment IDs
clasp versions # list version history
Forgetting the deploy step after a push is the single most common "I fixed it but users still see the bug" report — always pair a fix with a deploy when the project has a live deployment.
Multi-environment (dev/staging/prod)
clasp has no native named-environment concept — one .clasp.json points at one scriptId. The standard workaround is one config file per environment, copied into place before pushing:
.clasp.dev.json
.clasp.staging.json
.clasp.prod.json
{
"scripts": {
"push:dev": "cp .clasp.dev.json .clasp.json && clasp push -f",
"push:staging": "cp .clasp.staging.json .clasp.json && clasp push -f",
"deploy:prod": "cp .clasp.prod.json .clasp.json && clasp push -f && clasp deploy -d \"$npm_config_message\""
}
}
Never commit the active .clasp.json if it varies per developer machine/environment — commit the per-environment copies instead and gitignore the working one, or keep .clasp.json itself checked in only for single-environment projects.
Manifest essentials worth setting explicitly
Don't leave appsscript.json at its scaffolded defaults:
runtimeVersion: "V8"— required for modern syntax and decorators (see thebootgs-quickstartskill if the project uses bootgs).oauthScopes— list only what's actually called. GAS shows the full list on the consent screen; an over-broad list (a common copy-paste mistake) increases user friction and review scrutiny for public add-ons without adding capability.webapp.executeAs/webapp.access— only relevant ifdoGet/doPostare deployed as a web app.exceptionLogging: "STACKDRIVER"— otherwise uncaught errors only appear in the legacy execution log tied to the script's lifetime.
Verification
-
clasp push -fused in CI (interactive prompts hang non-interactively without-f). - A deploy step (
clasp deploy) runs after push whenever the project has a live deployment end users depend on — push alone is not a release. -
.clasprc.jsonis never committed; CI injects it from a secret. -
oauthScopesreviewed against what the code actually calls before each release.
Files in this skill
1apps-script-clasp-workflow skill questions
How do I install the apps-script-clasp-workflow skill in Claude Code?
Run npx degit bootgs/skills/skills/apps-script-clasp-workflow ~/.claude/skills/apps-script-clasp-workflow. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the apps-script-clasp-workflow skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.