airtable-scriptinglisted

# Airtable Scripting Skill ## Purpose This skill provides comprehensive guidance for writing Airtable scripts in both **Scripting Extensions** (manual execution) and **Automation Scripts** (triggered execution). It covers the Airtable Scripting API, Web API integration, field handling, and best practices. **Key conventions used throughout this skill:** - **Always use IDs** (not names) to refer to tables, fields, views, and bases. IDs are stable; names can be renamed by users and break scripts silently. - **`remoteFetchAsync`** is for Scripting Extensions only. **`fetch`** is for Automation Scripts only. Do not mix them up. ## Direct Airtable Access via MCP If the user asks Claude to **directly read or modify Airtable data** (rather than write a script for them to run), use an Airtable MCP server instead of this skill: ``` /plugin install airtable@claude-plugins-official ``` The official plugin bundles Airtable's hosted MCP server (OAuth or PAT, nothing to run locally) and is the only one that can read **Interface pages** and **create whole bases**. Alternatively, the community [`airtable-mcp-server`](https://github.com/domdomegg/airtable-mcp-server) by domdomegg is a self-hosted option (run via `npx` or its HTTP transport, PAT auth only) and is the one that can **delete records** and work with **record comments**. Its HTTP transport has no built-in auth, so only run it behind a reverse proxy or in a secured environment. Both cover read/search/create/update of records