mickzijdelmickzijdel/airtable-utils/skills/airtable-standards-check/SKILL.md

airtable-standards-check

Skill0 starsChanged 8 days agoMITView on GitHub

Check an Airtable schema JSON file against the BlueDot Impact Airtable Standards. Use when the user wants to validate their Airtable base structure, find naming convention violations, or produce a standards compliance report.

In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- airtable-schema-diffSkill
- airtable-schemaSkill
- airtable-scriptingSkill
- airtable-user-scrapingSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
No external dependencies — the script uses the Python standard library only.
line 14
Very specific:
Run the checker: airtable-check-standards {base_id}_{name}_{timestamp}_schema.json
line 61

≈ “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 Standards Check Skill

Purpose

This skill covers running airtable-check-standards to validate a schema JSON file (produced by airtable-export-schema) against the BlueDot Impact Airtable Standards. It outputs a Markdown report grouped by table, listing errors and warnings for each rule violation.

Prerequisites

No external dependencies — the script uses the Python standard library only. No API token or network access needed.

Running the Checker

# Check a schema and print report to stdout
airtable-check-standards schema.json

# Suppress warnings, show errors only
airtable-check-standards schema.json --errors-only

# Write the report to a file
airtable-check-standards schema.json --output report.md

# Both flags combined
airtable-check-standards schema.json --errors-only --output report.md

The script exits with code 0 if no errors are found, or 1 if any errors are found — making it suitable for CI pipelines.

Rules

The following rules are checked automatically:

Rule	Severity	Check
`table-sentence-case`	error	Table name starts with uppercase
`table-singular`	warning	Table name isn't plural (heuristic)
`table-description-keys`	warning	Description has "Description:" and "Last reviewed on:"
`table-missing-all-view`	warning	Table has an "All" view
`field-sentence-case`	error	Field name (after `[prefix]` strip) starts with uppercase
`field-boolean-is-prefix`	warning	Checkbox fields start with "Is "
`field-date-on-suffix`	warning	Date fields end in " on"
`field-datetime-at-suffix`	warning	DateTime fields end in " at"
`field-repeats-table-name`	warning	Field name doesn't repeat table name words

Rules Requiring Manual Review

The following standards cannot be checked automatically and require human judgment:

Whether table/field descriptions are meaningful (not just present)
Whether tables or bases should be merged to reduce duplication
Automation naming conventions

Workflow

Export the schema: airtable-export-schema --token ... --base ...
Run the checker: airtable-check-standards {base_id}_{name}_{timestamp}_schema.json
Review the report and fix violations in Airtable
Re-export and re-check until the report is clean

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