agentleFS
Sign inStart free
mickzijdelmickzijdel/airtable-utils/skills/airtable-schema-diff/SKILL.md

airtable-schema-diff

Skill0 starsChanged 7 days agoMITView on GitHub

Compare two Airtable schema exports to see what changed between them. Use when the user wants to diff two schema JSON files, detect table/field/view additions, removals, renames, or type changes.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No external dependencies — the script uses the Python standard library only.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Airtable Schema Diff Skill

Purpose

This skill covers running airtable-diff-schema to compare two schema JSON files produced by airtable-export-schema. It reports what changed between them: tables added or removed, fields added/removed/renamed/type-changed, and views added/removed/renamed.

Comparisons are done by entity ID, so renames are detected correctly rather than showing as a remove + add.

Prerequisites

No external dependencies — the script uses the Python standard library only.

Running the Diff

# Print diff to stdout
airtable-diff-schema old_schema.json new_schema.json

# Write diff report to a file
airtable-diff-schema old_schema.json new_schema.json --output diff.md

Both arguments are schema JSON files as produced by airtable-export-schema.

Output Format

The output is a Markdown report structured as follows:

# Schema Diff: <base name>

## Tables

### Added
- TableName

### Removed
- TableName

## Fields in <TableName>

### Added
- FieldName (type)

### Removed
- FieldName

### Renamed
- OldName → NewName

### Type changed
- FieldName: oldType → newType

## Views in <TableName>

### Added
- ViewName

### Removed
- ViewName

### Renamed
- OldName → NewName

Tables and sections with no changes are omitted from the report. If there are no differences at all, the report says so explicitly.

Workflow

  1. Export the old schema (or use a previously saved one): airtable-export-schema
  2. Make changes in Airtable
  3. Export the new schema: airtable-export-schema
  4. Diff them: airtable-diff-schema old_schema.json new_schema.json

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free