💡 Platform feature: Workspace Studio Skills packaging for script catalog

[github-actions[bot]]

Summary

Package existing and future GAS scripts in the catalog as Workspace Studio Skills — reusable automation modules invokable from the Gemini sidebar in any Google Workspace app. Users could trigger "archive my labeled emails" or "generate my calendar briefing" directly from Gmail or Calendar via natural language, without visiting the deploy page. This is a distribution and platform strategy proposal, not a new script.

Market Signal

Google Workspace Studio launched Skills at Cloud Next 2026 (May), with Apps Script custom triggers/steps integration announced. Skills are described as "an emerging method for effective agentic automation" — modular, reusable, shareable components that convert expertise into automation. Skills are "rolling out immediately" per AppsScriptPulse. The Workspace MCP Server (in preview) further enables external AI agents to integrate with Workspace capabilities. Google I/O 2026 launched Gemini 3.5 Flash, and the Gemini sidebar in the Apps Script editor began rolling out in August 2026. The platform signals are clear: Google is aggressively investing in making Workspace automations accessible through natural language and agentic interfaces.

User Signal

The project's PRD identifies "catalog-native extensibility" as a core architectural strength: each SCRIPT_CATALOG entry brings its own config schema, and the deploy page renders the appropriate form. Extending this pattern to Skills metadata is a natural evolution. Idea #144 (Schema-driven SCRIPT_CATALOG contract) provides the foundational schema — Skills packaging would consume and extend it with trigger-type, input-schema, and output-schema fields. No existing idea discussion covers Workspace Studio integration. The deploy page serves personal users well, but Skills would open an additional distribution channel for users who prefer conversational invocation over form-based configuration.

Technical Opportunity

Workspace Studio allows custom triggers and steps built with Apps Script. The project's scripts already follow a clean separation (config.gs + code.gs + src/index.js) that maps naturally to Skill inputs/outputs. The SCRIPT_CATALOG contract (#144) could be extended with Skills metadata (trigger type, input schema, output schema) using a single shared definition. This is additive — the existing deploy page flow is unaffected; Skills become an additional distribution channel. calendar-to-briefing-doc is an ideal pilot: clear trigger (schedule or user request), clear output (email briefing), well-tested (249 tests, 99% coverage).

Assessment

Dimension	Score	Rationale
Feasibility	med	Skills API is brand new with sparse documentation; the API surface may change; needs investigation before commitment
Impact	high	Opens a new distribution channel (Gemini sidebar across all Workspace apps); positions project as a reference implementation in the nascent Skills ecosystem
Urgency	high	First-mover advantage while the Skills ecosystem is nascent; early entrants get outsized visibility and community adoption

Adversarial Review

Strongest objection: Workspace Studio Skills API documentation is sparse (brand new), the API may change, and Skills may require Workspace Business/Enterprise licenses — excluding the project's core audience of personal Google account users.

Rebuttal: Start with a bounded proof-of-concept: one script (calendar-to-briefing-doc) exposed as a Skill. If the API changes, the investment is minimal — one wrapper, not a rewrite. If Skills require Business/Enterprise, the project still serves personal users via the deploy page — Skills are an additional channel, not a replacement. The project's clean architecture (DI, config separation, tested logic) means the Skills wrapper is thin. Early exploration positions the project to be a reference implementation as the ecosystem matures, attracting contributors and users from the growing Workspace Studio community.

Suggested Next Step

Monitor Workspace Studio Skills developer documentation as it matures (check monthly); prototype a Skills-compatible wrapper around calendar-to-briefing-doc with defined input/output schema once the custom Skills creation API is documented; track whether Skills are available on personal Google accounts vs. Business/Enterprise only.