airtable-schema-structure

Map Airtable tables, field IDs, types, and links via the Meta API.

2|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor --skill airtable-schema-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: airtable-schema-structure
Source: https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor/tree/main/.cursor/skills/airtable-schema-structure
Command: npx skills add https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor --skill airtable-schema-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect Airtable base structure (tables, field ids/types, links) via Meta API and repo SSOT. Schema only — no row data. Use before sampling cells or mapping fld/tbl constants. Triggers: Meta API, field id, linked tables, schema drift vs code.

Core Features & Use Cases

  • Schema discovery: list table ids, field ids/types, and links
  • Drift detection: compare code constants against live schema
  • Repo SSOT: maintain a single source of truth for schema constants

Quick Start

Run the airtable-schema-structure skill to retrieve the base schema metadata from the Meta API and compare it against your code constants.

Frequently Asked Questions about airtable-schema-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect an Airtable base schema without loading row data?

You can inspect an Airtable base schema without loading rows by fetching table and field metadata via the Meta API. This retrieves table ids, field ids, field types, and linked table structures directly.

What is Airtable schema drift detection and when do I need it?

Airtable schema drift detection compares your code constants against live base schemas to catch misaligned field ids. You need it when aligning code constants with live schemas across multiple bases to prevent integration failures.

How do I map Airtable linked tables and field ids using the Meta API?

To map Airtable linked tables and field ids, query the Meta API to retrieve schema metadata. This identifies table structures, field types, and link relationships without accessing individual cell values or rows.

Can I validate Airtable field id constants against a live base automatically?

Yes, you can validate Airtable field id constants by comparing your repository source of truth against live schema metadata fetched from the Meta API. This highlights any drift between code definitions and the actual base.

Does this approach retrieve Airtable row data or only schema metadata?

This approach retrieves schema metadata only, meaning it fetches table ids, field types, and links without loading rows. It is designed for structural inspection and drift detection rather than cell sampling or data export.

Why do my Airtable code constants keep breaking after base schema changes?

Airtable code constants break after schema changes because field ids or types drift from your code definitions. Running schema drift detection compares your constants against live base schemas to identify mismatches early.