Recipe Create Expense Tracker

Set up a Google Sheets spreadsheet for tracking expenses with headers and initial entries.

Security Scan

The skill is internally consistent with its stated purpose (creating and sharing a Google Sheet) and requests only the Google Workspace CLI binary and related skills; nothing requested is disproportionate — but the instructions have small usability/operational issues you should be aware of (placeholder SHEET_ID, automatic sharing to [e-mail]).

Purpose & Capability

Name/description match the actions in SKILL.md. The required binary (gws) and the dependent skills (gws-sheets, gws-drive) are appropriate for creating and sharing a Google Sheets document.

Instruction Scope

Instructions are limited to creating a spreadsheet, appending headers/entries, and sharing it. They use a SHEET_ID placeholder but do not show capturing the ID from the create command (usability gap). They also unconditionally share the sheet with [e-mail] — this is operationally expected but is a policy/privacy decision the user should confirm.

Install Mechanism

Instruction-only skill with no install actions or external downloads. Lowest-risk installation posture.

Credentials

The skill declares no environment variables, which is consistent. However the gws CLI and the referenced gws-* skills will require Google authentication and scopes at runtime; the SKILL.md does not document those scopes or the account context, so users should verify what credentials and OAuth scopes gws/gws-sheets/gws-drive will request.

Persistence & Privilege

always is false and the skill does not request persistent system-wide changes or modify other skills. It runs only when invoked.

Assessment

This recipe is coherent for creating and sharing a Google Sheets expense tracker, but check a few things before running it: - The commands use a SHEET_ID placeholder; you must capture the spreadsheet ID returned by the create command and substitute it into the subsequent append and permissions commands. - The recipe shares the sheet with [e-mail] automatically. Confirm that email is correct and that sharing is acceptable for the data you will put into the sheet. - The gws CLI (and the gws-sheets/gws-drive skills) will use your Google credentials and OAuth scopes — review what scopes/permissions they request and ensure you trust the implementation of those skills. - Because this is instruction-only, there is no install risk from this skill itself, but the runtime actions will create and share a document in your Google account; exercise usual caution with sensitive data. If you want stronger safety, update the recipe to capture and show the created SHEET_ID, and prompt for the recipient email instead of hard-coding [e-mail].

Create a Google Sheets Expense Tracker

PREREQUISITE: Load the following skills to execute this recipe: gws-sheets, gws-drive

Set up a Google Sheets spreadsheet for tracking expenses with headers and initial entries.

Steps

1. Create spreadsheet: gws drive files create --json '{"name": "Expense Tracker 2025", "mimeType": "application/vnd.google-apps.spreadsheet"}'
2. Add headers: gws sheets +append --spreadsheet SHEET_ID --range 'Sheet1' --values '["Date", "Category", "Description", "Amount"]'
3. Add first entry: gws sheets +append --spreadsheet SHEET_ID --range 'Sheet1' --values '["2025-01-15", "Travel", "Flight to NYC", "450.00"]'
4. Share with manager: gws drive permissions create --params '{"fileId": "SHEET_ID"}' --json '{"role": "reader", "type": "user", "emailAddress": "[e-mail]"}'