Spreadsheet Automation

v0.1.0

Turn Google Sheets into a powerful database and workflow engine using formulas, Apps Script, and integrations. Use when building systems in Sheets, automatin...

0· 903·9 current·9 all-time
byJatin Khatri@jk-0001
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description promise spreadsheet automation using formulas, Apps Script, and integrations; the SKILL.md content (formulas, multi-sheet patterns, Apps Script/integration guidance) matches that purpose and does not request unrelated capabilities.
Instruction Scope
Instructions are focused on Sheets, formulas, Apps Script, and connecting external services. This legitimately includes guidance to create OAuth authorizations, webhooks, or API keys for third-party integrations — expected for the purpose — but users should be aware that following the playbook will require granting Apps Script permissions and connecting external endpoints.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no environment variables, credentials, or config paths. The guidance may advise acquiring third-party API keys or OAuth consents for integrations, which is proportionate to the stated functionality.
Persistence & Privilege
The skill is not always-enabled and does not request system-level persistence or modification of other skills; autonomous invocation is allowed (platform default) and is appropriate for an instruction skill.
Assessment
This guide appears coherent for building automations in Google Sheets, but before following its examples: (1) review any Apps Script code or templates before authorizing them — Apps Script can request broad OAuth scopes; (2) avoid putting sensitive secrets (passwords, long-lived API keys) directly into sheet cells or shared scripts; prefer service accounts or secret managers where possible; (3) when connecting webhooks or third-party APIs, use least-privilege credentials and rotate them if shared; (4) test automations in a copy of your sheet and limit sharing permissions to reduce risk.

Like a lobster shell, security has layers — review code before you run it.

latestvk979mhnmf2kfecy3ab23szzpz582cfe2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments