Is airtable-schema-diff safe to install?

SaferSkills independently audited airtable-schema-diff (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/airtable-schema-diff/SKILL.md · 1 file

skills/airtable-schema-diff/SKILL.md1.8 KB · Markdown

name: airtable-schema-diff

description: "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."

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

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

airtable-schema-diff— agent skill

Is airtable-schema-diff safe to install?

Airtable Schema Diff Skill

Purpose

Prerequisites

Running the Diff

Output Format

Workflow

Audit the pieces. Scan the whole. Decide.