skills.rest
minicoohei
minicooheiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gas-clasp-ops

Automate batch push, deploy, and run operations across Google Apps Script projects via clasp.

345|12|Updated Apr 14, 2026
Search Tags:#automation#deployment#batch#multi-project#gas#clasp#google-apps-script
One-click install
npx skills add https://github.com/minicoohei/ai-agent-camp --skill gas-clasp-ops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gas-clasp-ops
Source: https://github.com/minicoohei/ai-agent-camp/tree/main/.claude/skills/gas-clasp-ops
Command: npx skills add https://github.com/minicoohei/ai-agent-camp --skill gas-clasp-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates batch operations for Google Apps Script projects via clasp, eliminating repetitive manual tasks when managing many GAS projects.

Core Features & Use Cases

  • Batch operations: push, deploy, and run across multiple GAS projects with a single command.
  • Project discovery: automatically detects GAS projects that contain a .clasp.json file.
  • Safe execution and reporting: supports dry-run mode and per-project results, continuing on errors to maximize coverage.

Quick Start

Push all GAS projects detected in the workspace and review the results.

Frequently Asked Questions about gas-clasp-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch push multiple Google Apps Script projects at once?▼

Batch push for Google Apps Script projects automates deploying multiple GAS projects by discovering directories containing a .clasp.json file and executing clasp push across all of them in a single workflow.

What is the best way to manage deployments across many Google Apps Script projects?▼

Managing deployments across many Google Apps Script projects is best handled by batch clasp operations that automate project discovery and execute deploy actions with per-project reporting and dry-run support for safe orchestration.

Do I need a .clasp.json file in every directory to batch manage Google Apps Script projects?▼

Yes, you need a .clasp.json file in every target directory because batch Google Apps Script management relies on automatic project discovery by detecting the presence of this clasp configuration file to orchestrate push, deploy, and run actions.

Can I run clasp commands across multiple Google Apps Script projects without stopping on errors?▼

Running clasp commands across multiple Google Apps Script projects continues on errors to maximize batch coverage, ensuring that a failure in one project does not halt the execution of subsequent push, deploy, or run actions.

How does dry-run mode work for batch Google Apps Script deployments?▼

Dry-run mode for batch Google Apps Script deployments executes clasp operations safely by simulating push, deploy, and run actions across discovered projects without applying changes, providing per-project reporting to verify orchestration before actual execution.

Related Skills

Explore More Software Engineering Skills→
lim010111lim010111
1

clasp-deploy-addon

Deploy, push, and test Google Calendar Add-on code using clasp CLI and Apps Script API.

Community
Advanced
niclasmartinsson-sysniclasmartinsson-sys
8

recipe-deploy-apps-script

Deploy local Google Apps Script files to live projects via the gws CLI.

Community
Advanced
kensaku63kensaku63

appscript

Develop and deploy Google Apps Script projects locally using the clasp CLI.

Community
Intermediate
fukukei23fukukei23

gas-autopilot

Automate Google Apps Script deployment, execution, and verification workflows using clasp and gws.

Community
Advanced