CtrlK
BlogDocsLog inGet started
Tessl Logo

airtable-automation

Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.

41

Quality

41%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-automation-builder/skills/airtable-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Scale 1-3

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

This is a competent Airtable automation skill that covers the major operations with clear tool sequences and useful pitfall documentation. Its main weaknesses are the lack of executable call examples (showing exact MCP invocation syntax), missing validation/error-recovery loops for batch and destructive operations, and some redundancy across sections. The content would benefit from being tightened and from including at least one complete end-to-end example.

Suggestions

Add at least one complete, executable MCP call example showing exact invocation syntax (e.g., a full AIRTABLE_CREATE_RECORD call with sample baseId, tableIdOrName, and fields) to improve actionability.

Add explicit validation checkpoints and error recovery loops for batch operations (e.g., 'After each 10-record chunk: verify response contains created record IDs; if 422 error, check field names against schema and retry').

Consolidate duplicate pitfall information — field name case-sensitivity, batch limits, and ID formats are mentioned in multiple places; centralize them in the 'Known Pitfalls' section and reference it from workflows.

Remove the generic 'When to Use' and 'Limitations' boilerplate at the end, which adds no Airtable-specific value and wastes tokens.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy — pitfalls are repeated across sections (e.g., case-sensitive field names mentioned multiple times), the 'When to Use' and 'Limitations' boilerplate at the end adds little value, and the quick reference table largely duplicates information already presented in the workflow sections. The ID format section and batch limits are also partially redundant with earlier pitfall mentions.

2 / 3

Actionability

The skill provides concrete tool names, parameter names, and formula syntax examples, which is good. However, it lacks executable code or actual MCP call examples showing exact invocation syntax with real parameters. The guidance is specific enough to follow but stops short of copy-paste ready examples — e.g., no example of a complete RUBE_SEARCH_TOOLS call or a full AIRTABLE_CREATE_RECORD invocation with sample fields.

2 / 3

Workflow Clarity

Workflows are clearly sequenced with labeled steps and prerequisite/optional annotations, which is helpful. However, there are no explicit validation checkpoints or error recovery loops — for batch operations (chunking 10 records at a time) and destructive operations (delete), there's no validate-then-proceed pattern or feedback loop for handling 422/429 errors beyond mentioning they exist as pitfalls.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's a monolithic document with no references to external files. Given the length (~150+ lines) and the breadth of topics covered (CRUD, search, schema management, comments, formula syntax, pagination), some content like the formula syntax reference or the quick reference table could be split into separate files for better organization.

2 / 3

Total

8

/

12

Passed

Description

32%Scale 1-3

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

The description identifies the platform (Airtable) and the tooling (Rube MCP/Composio) but is too vague about what specific actions it performs. It lacks an explicit 'Use when...' clause and doesn't include enough natural trigger terms that users would say when needing Airtable automation help.

Suggestions

Add specific concrete actions like 'Create, update, delete, and query Airtable records; manage bases, tables, fields, and views'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to interact with Airtable, manage database records, or automate Airtable workflows.'

Include natural trigger terms users might say, such as 'Airtable database', 'add a row', 'update records', 'create a table', or 'Airtable API'.

DimensionReasoningScore

Specificity

Names the domain (Airtable) and lists some entities (records, bases, tables, fields, views) but doesn't describe specific concrete actions beyond the vague 'automate tasks'. What actions? Create, update, delete, query?

2 / 3

Completeness

The 'what' is vague ('automate Airtable tasks') and there is no explicit 'when' clause (no 'Use when...' or equivalent trigger guidance). The instruction to 'always search tools first' is implementation guidance, not a trigger. Missing 'Use when...' caps this at 2 per guidelines, and the weak 'what' brings it to 1.

1 / 3

Trigger Term Quality

Includes 'Airtable', 'records', 'bases', 'tables', 'fields', 'views' which are relevant keywords, but misses natural user phrases like 'spreadsheet', 'database', 'add a row', 'create a record', or common task-oriented terms users would actually say.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Airtable' and 'Rube MCP (Composio)' provides some distinctiveness, but the generic 'automate tasks' phrasing could overlap with other Airtable or database-related skills. The mention of the specific MCP tool helps somewhat.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation — 10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
Reviewed

Table of Contents

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.