google-script-deploy

Deploy HTML files as stable Google Apps Script web apps.

2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/MDGrey33/memnyx --skill google-script-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-script-deploy
Source: https://github.com/MDGrey33/memnyx/tree/main/.claude/skills/google-script-deploy
Command: npx skills add https://github.com/MDGrey33/memnyx --skill google-script-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of publishing and updating HTML files as Google Apps Script web apps, so you can keep a permanent URL while iterating on the underlying content.

Core Features & Use Cases

  • First-time setup: Creates a standalone Apps Script project, configures the manifest, and prepares a per-project staging directory.
  • Repeatable deployments: Pushes updated HTML in place and redeploys without changing the web app URL.
  • Operational checks: Verifies clasp installation, Google authentication, Apps Script API availability, and project configuration.
  • Use case: A dashboard-generating workflow can hand off a source directory and rely on this Skill to set up, deploy, and maintain a stable public or restricted web app endpoint.

Quick Start

Ask the Skill to set up or redeploy a Google Apps Script web app from your source directory, and provide the HTML entry file name, project title, timezone, and access level when prompted.

Frequently Asked Questions about google-script-deploy

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

FAQPage Schema
How do I deploy HTML as a Google Apps Script web app without changing the URL?

To deploy HTML to a stable Google Apps Script URL, this Skill creates a standalone Apps Script project, configures the manifest, and manages a per-project staging directory. It pushes updated HTML in place and redeploys iteratively without altering the permanent web app URL.

What do I need to set up before publishing HTML through Google Apps Script?

Before publishing HTML through Google Apps Script, you need clasp installation, Google authentication, and Apps Script API access enabled. The Skill verifies these prerequisites during operational checks and prompts you for the HTML entry file, project title, timezone, and access level to complete the configuration.

Can I use clasp to update an internal tool dashboard while preserving a permanent endpoint?

Yes, you can use clasp to update an internal tool dashboard while preserving a permanent endpoint. The Skill handles repeatable deployments by pushing updated HTML content to the existing staging directory and redeploying in place, ensuring the web app URL remains stable across iterative updates.

How does the staging directory work when deploying web apps with clasp?

The staging directory works by acting as a per-project configuration area that prepares your HTML files for deployment. The Skill sets up this staging directory during first-time setup, allowing you to push updated HTML content and redeploy it in place to maintain a stable public or restricted web app endpoint.

Why does my Google Apps Script deployment require a per-project manifest?

A Google Apps Script deployment requires a per-project manifest to define the project configuration, timezone, and access levels. The Skill creates and configures this manifest during first-time setup to ensure the HTML files are correctly published as a functional web app with the appropriate permissions.