recipe-log-deal-update
Append a deal status update to a Google Sheets sales tracking spreadsheet.
Profile →npx skills add googleworkspace/cli --skill recipe-log-deal-update --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Log Deal Update to Sheet > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-sheets`, `gws-drive` Append a deal status update to a Google Sheets sales tracking spreadsheet. ## Steps 1. Find the tracking sheet: `gws drive files list --params '{"q": "name = '\''Sales Pipeline'\'' and mimeType = '\''application/vnd.google-apps.spreadsheet'\''"}'` 2. Read current data: `gws sheets +read --spreadsheet SHEET_ID --range "Pipeline!A1:F"` 3. Append new row: `gws sheets +append --spreadsheet SHEET_ID --range 'Pipeline' --values '["2024-03-15", "Acme Corp", "Proposal Sent", "$50,000", "Q2", "jdoe"]'`
- Steps
What does the recipe-log-deal-update skill do?
Append a deal status update to a Google Sheets sales tracking spreadsheet.
How do I install it?
Run `npx skills add googleworkspace/cli --skill recipe-log-deal-update --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From googleworkspace/cli, a repository with 30,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.