Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
Install MCP Sheet Cache Bridge
$ npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-sheet-cache-bridge --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gtm-ops/mcp-sheet-cache-bridge .claude/skills/mcp-sheet-cache-bridge && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mcp-sheet-cache-bridge" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridge into .claude/skills/mcp-sheet-cache-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-sheet-cache-bridge", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridgeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-sheet-cache-bridge --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gtm-ops/mcp-sheet-cache-bridge .agents/skills/mcp-sheet-cache-bridge && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mcp-sheet-cache-bridge" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridge into .agents/skills/mcp-sheet-cache-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-sheet-cache-bridge", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-sheet-cache-bridge --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gtm-ops/mcp-sheet-cache-bridge .cursor/skills/mcp-sheet-cache-bridge && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mcp-sheet-cache-bridge" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridge into .cursor/skills/mcp-sheet-cache-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-sheet-cache-bridge", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zapier/gtm-cheat-codes.git --path skills/gtm-ops/mcp-sheet-cache-bridge--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-sheet-cache-bridge --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gtm-ops/mcp-sheet-cache-bridge .gemini/skills/mcp-sheet-cache-bridge && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mcp-sheet-cache-bridge" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridge into .gemini/skills/mcp-sheet-cache-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-sheet-cache-bridge", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zapier/gtm-cheat-codes mcp-sheet-cache-bridgeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gtm-ops/mcp-sheet-cache-bridge .github/skills/mcp-sheet-cache-bridge && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mcp-sheet-cache-bridge" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridge into .github/skills/mcp-sheet-cache-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-sheet-cache-bridge", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/gtm-cheat-codes mcp-sheet-cache-bridge --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gtm-ops/mcp-sheet-cache-bridge .opencode/skills/mcp-sheet-cache-bridge && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mcp-sheet-cache-bridge" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/mcp-sheet-cache-bridge into .opencode/skills/mcp-sheet-cache-bridge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-sheet-cache-bridge", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mcp-sheet-cache-bridge- GitHub stars
- 342
- Token cost
- ~905 tokens
- SKILL.md length
- 490 words
- Files
- 6
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
- Works in 5 steps: Designs a cache tab schema that mirrors… → Builds an event-driven sync pattern from… → Uses create, update, and delete logic… → …
- Keeping Zapier Tables as the source of truth while legacy sheets still need the data
- SKILL.md covers What This Skill Does, When You Need This Pattern, Architecture and Required Connections Through…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This pattern fits teams that moved a multi-tab spreadsheet into Zapier Tables but still have Apps Script, Looker Studio, formulas or exports reading Google Sheets. The agent designs a cache tab that mirrors only the fields those consumers need, builds create, update and delete logic keyed by a stable record ID, points legacy consumers at the cache and documents the field map and cutover plan so the sync stays maintainable.
Sync rules are laid out in a table: matching records are created or updated, records that stop matching the filter or are deleted at the source are removed, and a schema change pauses the sync until the field map is reviewed. A sample cache layout has record_id, display_title, status, priority, assignee, link and updated_at columns. Syncing on change rather than on a schedule avoids pointless task usage. The skill runs through Zapier MCP connections to Zapier Tables, Google Sheets and, optionally, Slack, and ships README, setup, schema map and onboarding prompt files.
When your agent uses it
- Keeping Zapier Tables as the source of truth while legacy sheets still need the data
- Feeding a Slack digest or daily report from fresh cache rows
- Cutting task usage by replacing a scheduled full-table sync
Example prompts
- “Design a Google Sheets cache tab for our Zapier Tables support-ticket table.”
- “Add delete and update sync so the cache drops records that leave the active filter.”
- “Write the field map and cutover plan for moving our Looker Studio report onto the cache tab.”
Requirements
- A Zapier MCP connection
- Zapier Tables or another approved record store
- Google Sheets access
- Slack access, if digests are wanted
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Designs a cache tab schema that mirrors only the fields downstream tools need.
- Builds an event-driven sync pattern from the source record store to Google Sheets.
- Uses create, update, and delete logic keyed by a stable record ID.
- Points legacy consumers at the cache instead of direct API reads.
- Documents the field map and cutover plan so the sync stays maintainable.
What it can do on your machine
Read from SKILL.md and the folder at commit 022a288. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
MCP Sheet Cache Bridge loads about 905 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 490 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from zapier/gtm-cheat-codes at commit 022a288, republished under its MIT licence (© zapier). 490 words, ~905 tokens.
Download SKILL.mdSave it as
.claude/skills/mcp-sheet-cache-bridge/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- mcp-sheet-cache-bridge
- description
- Keep Zapier Tables or another MCP-connected record store as the source of truth while Google Sheets-based tools read an event-driven cache tab.
MCP Sheet Cache Bridge
Use this skill when a team wants Zapier Tables to be the source of truth but still needs Google Sheets-based tools, scripts, dashboards, or exports to read a simple tab.
What This Skill Does
- Designs a cache tab schema that mirrors only the fields downstream tools need.
- Builds an event-driven sync pattern from the source record store to Google Sheets.
- Uses create, update, and delete logic keyed by a stable record ID.
- Points legacy consumers at the cache instead of direct API reads.
- Documents the field map and cutover plan so the sync stays maintainable.
When You Need This Pattern
- A team replaced a multi-tab spreadsheet with Zapier Tables but still has Apps Script, Looker Studio, formulas, or exports reading Google Sheets.
- A Slack pinned digest or daily report needs fresh rows without running a scheduled full refresh.
- Scheduled syncs would create too many unnecessary tasks.
- Existing tools can read Google Sheets easily but do not have direct access to the source record store.
- The team wants one source of truth with a cheap, stable read path.
Architecture
Zapier Tables source of truth
-> event-driven cache sync on record change
-> Google Sheet cache tab
-> Apps Script, Looker Studio, exports, or digestsRequired Connections Through Zapier MCP
- Zapier Tables or another approved record store: read record changes.
- Google Sheets: create, update, and delete cache rows.
- Optional Slack: post digest or sync-health summaries.
Cache Sync Rules
| Source event | Cache action |
|---|---|
| Record matches active cache filter | Create or update matching row |
| Record no longer matches filter | Delete or clear matching row |
| Record deleted in source | Delete matching cache row |
| Cache schema changes | Pause sync until the field map is reviewed |
Cache Tab Columns
| Column | Purpose |
|---|---|
| record_id | Source row ID or external join key |
| display_title | Subject, name, or primary label |
| status | Filter or workflow state |
| priority | Sort order for digest or dashboard |
| assignee | Owner or responsible team |
| link | Source record, ticket, or Slack permalink |
| updated_at | Last sync timestamp |
Show full SKILL.md (180 more words)Show less
Task Budget Pattern
| Pattern | Approximate task impact |
|---|---|
| Cache sync on record change | One sync run per relevant source change |
| Scheduled full-table sync every 5 minutes | Hundreds of unnecessary runs per day |
| Apps Script read of cache tab | No Zapier task usage for the read path |
Zapier MCP And SDK Role
- Use Zapier MCP to read source record changes and update Google Sheets cache rows.
- Use Zapier SDK when the pattern becomes repeatable: schema map validation, idempotent upsert handling, sync logging, retry handling, and health alerts.
- Keep destructive sync actions behind approval until the team trusts the mapping.
Guardrails
- Do not run scheduled full-table syncs unless the team explicitly accepts the task cost.
- Do not store private API tokens in Apps Script if the cache solves the read path.
- Do not delete production cache tabs without explicit approval.
- Do not disable legacy read paths until cutover is verified.
- Keep schema changes documented in both the source table and cache map.
Inspired By
Generalized from a public workflow by Kenny Taber. The public writeup names Kenny and does not name the company.
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files in skills/gtm-ops/mcp-sheet-cache-bridge of zapier/gtm-cheat-codes.
- SKILL.md
- ONBOARDING-PROMPT.md
- README.md
- SCHEMA-MAP.md
- SETUP.md
- metadata.yaml
Open the folder on GitHubat commit 022a288
Compare with similar skills
MCP Sheet Cache Bridge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| MCP Sheet Cache Bridge this skillzapier/gtm-cheat-codes | 342 | — | ~905 | Automated safety check: Pass | MIT | |
| Zapier Statuszapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Zapier Workflowsdavila7/claude-code-templates | 32k | 2 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Makeericrisco/rsc-harness | 174 | — | ~3.1k | Automated safety check: Notes | MIT | |
| Piece Builderactivepieces/activepieces | 25k | — | ~3.1k | Automated safety check: Notes | Custom licence | |
| MCP Clientcoleam00/second-brain-skills | 832 | — | ~1k | Automated safety check: Pass | None |
Similar skills
- Official
Zapier Workflows
davila7/claude-code-templates
Manage and trigger pre-built Zapier workflows and MCP tool orchestration.
Make
ericrisco/rsc-harness
A skill your agent uses when operating Make.com (formerly Integromat) programmatically — driving its REST API v2 or the Make MCP server from code or an agent to create, read, update, activate, run…
Piece Builder
activepieces/activepieces
Build and edit Activepieces pieces (integrations) — creating new pieces, adding actions or triggers, or fixing bugs in existing ones.
MCP Client
coleam00/second-brain-skills
Universal MCP client for connecting to any MCP server with progressive disclosure.
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
More from zapier/gtm-cheat-codes
All 21 skills in this repo- Official
Customer Deck Builder
zapier/gtm-cheat-codes
Builds a tailored sales or customer success deck from approved CRM context and generates it in Gamma through Zapier MCP for calls like QBRs or renewals.
- Official
Customer Story Writer
zapier/gtm-cheat-codes
Drafts customer stories or metric-led story pages from approved transcripts, notes and quotes, keeping verified claims apart from ones that still need approval.
- Official
Customer Social Proof Finder
zapier/gtm-cheat-codes
Finds approved case studies, quotes, stats, logos and peer examples for campaigns, decks, emails and sales conversations, and flags anything that still needs approval.
- Official
Install Zapier
zapier/gtm-cheat-codes
Works out whether you need Zapier MCP, the SDK or the CLI, then walks through installing and verifying that one path step by step.
- Official
Media Inbox Triage
zapier/gtm-cheat-codes
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.
- Official
MCP Urgent Caller Triage
zapier/gtm-cheat-codes
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
Related
Categories
Questions about MCP Sheet Cache Bridge
What does MCP Sheet Cache Bridge do?
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads. This pattern fits teams that moved a multi-tab spreadsheet into Zapier Tables but still have Apps Script, Looker Studio, formulas or exports reading Google Sheets. The agent designs a cache tab that mirrors only the fields those consumers need, builds create, update and delete logic keyed by a stable record ID, points legacy consumers at the cache and documents the field map and cutover plan so the sync stays maintainable.
When should I use MCP Sheet Cache Bridge?
MCP Sheet Cache Bridge fits situations like: keeping Zapier Tables as the source of truth while legacy sheets still need the data; feeding a Slack digest or daily report from fresh cache rows; cutting task usage by replacing a scheduled full-table sync.
How do I install MCP Sheet Cache Bridge in Claude Code?
Run `npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a claude-code`. Or copy the skill folder (skills/gtm-ops/mcp-sheet-cache-bridge in zapier/gtm-cheat-codes) into .claude/skills/mcp-sheet-cache-bridge in your project. Claude Code loads it when a task matches its description.
How do I install MCP Sheet Cache Bridge in Codex?
Run `npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a codex`. Or copy the skill folder (skills/gtm-ops/mcp-sheet-cache-bridge in zapier/gtm-cheat-codes) into .agents/skills/mcp-sheet-cache-bridge in your project. Codex loads it when a task matches its description.
Can I use MCP Sheet Cache Bridge in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zapier/gtm-cheat-codes --skill mcp-sheet-cache-bridge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcp-sheet-cache-bridge, .gemini/skills/mcp-sheet-cache-bridge, .github/skills/mcp-sheet-cache-bridge and .opencode/skills/mcp-sheet-cache-bridge in your project.
What does MCP Sheet Cache Bridge need to run?
SKILL.md names no scripts, command-line tools or credentials: MCP Sheet Cache Bridge is instructions for the agent only. Our summary lists: A Zapier MCP connection; Zapier Tables or another approved record store; Google Sheets access; Slack access, if digests are wanted.
Does MCP Sheet Cache Bridge access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is MCP Sheet Cache Bridge safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does MCP Sheet Cache Bridge use?
MCP Sheet Cache Bridge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does MCP Sheet Cache Bridge use?
About 905 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to MCP Sheet Cache Bridge?
Skills that share tags, products or a category with MCP Sheet Cache Bridge: Zapier Status (zapier/zapier-mcp, 430 stars), Zapier Workflows (davila7/claude-code-templates, 32k stars), Make (ericrisco/rsc-harness, 174 stars) and Piece Builder (activepieces/activepieces, 25k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains MCP Sheet Cache Bridge?
zapier (a GitHub organization, an official publisher) maintains it in zapier/gtm-cheat-codes, which has 342 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 13, 2026.
Source: zapier/gtm-cheat-codes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.