Google Sheets Skill for Muse
Work Google Sheets from Muse like a power user.
- What
- Work Google Sheets from Muse like a power user.
- Cost
- Free
- Needs
- the gws CLI installed, a Google account with Sheets access, and a one-time OAuth flow (the shared auth SKILL.md is generated by running `gws generate-skills`). No paid API — Google Sheets API free tier.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Lets Muse read and write Google Sheets through the gws command-line tool: read cell ranges, append rows (single or bulk via JSON), create spreadsheets, and run full spreadsheets API operations (batchUpdate, metadata, value ranges). Companion skills cover the two most common moves — +read (read-only, never modifies the sheet) and +append (with an explicit confirm-before-write caution). Discovered via skills.sh. Honest note: requires installing the gws CLI and completing Google OAuth first (the shared auth skill is generated by running `gws generate-skills`); write operations should be confirmed with you before executing. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (Apache-2.0) by @googleworkspace.
Version:
Install
Prerequisites: the gws CLI installed, a Google account with Sheets access, and a one-time OAuth flow (the shared auth SKILL.md is generated by running `gws generate-skills`). No paid API — Google Sheets API free tier. Install "Google Sheets Skill for Muse" for me. Read and write Google Sheets from Muse via the gws CLI: read cell ranges, append rows (single or bulk), create spreadsheets, and full spreadsheets API operations — with dedicated +read (read-only) and +append helper skills. Repository: https://github.com/googleworkspace/cli 1. Locate the gws-sheets skill and its +read and +append helper skills in the repository; fetch their SKILL.md files (and any helper files) into a temporary folder and summarize what each does in one or two sentences. 2. Safety check: review the SKILL.md files and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy the SKILL.md files and their helper files into the agent's skills directory, in a folder named "gws-sheets". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the gws CLI, run `gws generate-skills` for auth, and complete the Google OAuth flow). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.