airtable-overview

Explains what Airtable is and how data is structured — bases, tables, fields, records, views, automations, and interfaces. Use when you need context about the Airtable data model.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/airtable/skills/airtable-overview/SKILL.md

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, well-organized, appropriately short reference for the Airtable data model that scores well on structure and efficiency. Its main limitation is that it is purely descriptive — it adds no guidance on how the data model affects real work (e.g., API operations, record ID formats, or interface-permission implications), leaving its practical value dependent on the reader's inference.

Suggestions

Add one or two actionable implications of the data model, e.g., what a record ID looks like (recXXXXXXXXXXXX) and how it is used in API calls or formulas.

Expand the interface-permission note into concrete guidance: when a user can only access a base through interfaces, table-level operations (API reads/writes, imports) may fail, so check access before attempting them.

Include a short worked example of a base with two tables linked by a linked-record field to make the abstract field/record relationship tangible.

Dimension	Reasoning	Score
Conciseness	The ~35-line body is lean with well-chosen detail, but minor instances of over-explanation remain — e.g., "similar to a sheet in a spreadsheet or a table in a relational database" and "It is the top-level container" restate knowledge Claude already has.	4 / 5
Actionability	The content provides concrete facts (unique record IDs, cell values per field, views not changing underlying data, interface-only access) but is entirely descriptive — it never instructs or shows how to apply the model, matching the "some concrete guidance but incomplete" anchor.	3 / 5
Workflow Clarity	This is a single-purpose skill under 50 lines with an unambiguous single task (explaining the Airtable data model) and no destructive or batch operations, so the simple-skill exception applies and workflow clarity is not impeded.	5 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references and a clean section hierarchy (Data model → Bases/Tables/Fields/Records/Views, Automations, Interfaces), satisfying the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that states a clear purpose, enumerates the specific concepts covered, and includes an explicit 'Use when' clause in third person. Its only weakness is that the trigger condition is somewhat narrow and abstract rather than enumerating the phrases a user would actually say.

Dimension	Reasoning	Score
Specificity	The description enumerates seven concrete concepts ("bases, tables, fields, records, views, automations, and interfaces") giving specific coverage of the domain, though the single generic verb "Explains" leaves it just short of the comprehensive anchor.	4 / 5
Completeness	Both parts are present — a clear "what" ("Explains what Airtable is and how data is structured") and an explicit "Use when you need context about the Airtable data model" — but the "when" clause is a single abstract condition rather than concrete user-mentionable triggers, so it does not fully reach the explicit anchor 5 example.	4 / 5
Trigger Term Quality	Terms like "Airtable", "bases", "records", "automations", and "interfaces" are exactly the natural nouns a user would say, but common variations such as "Airtable database" or "Airtable spreadsheet" are missing.	4 / 5
Distinctiveness Conflict Risk	"Airtable" names a clear niche and every trigger term is product-specific, so the risk of firing for the wrong skill is minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/airtable/skills/airtable-overview/SKILL.md
Commit: 5fd93af

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.