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.

44

Quality

45%

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

The canonical home for this skill is airtable-automation in sickn33/agentic-awesome-skills

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 invocation examples (actual tool call payloads), missing validation/feedback loops for destructive and batch operations, and some content redundancy across sections. The 'When to Use' footer adds no value.

Suggestions

Add at least one concrete, copy-paste-ready example of an actual MCP tool invocation with full parameter JSON for a common operation like creating a record.

Add explicit validation checkpoints for batch and destructive workflows (e.g., 'Verify record count before bulk delete', 'Confirm chunk was created successfully before proceeding to next batch').

Remove the vacuous 'When to Use' section and deduplicate pitfalls — consolidate batch limits and ID formats into the Known Pitfalls section only, removing duplicates from individual workflows.

Consider splitting the formula syntax reference and quick reference table into separate referenced files to improve progressive disclosure for this longer skill.

DimensionReasoningScore

Conciseness

The content is reasonably efficient but includes some redundancy — pitfalls are repeated across sections (e.g., field name case sensitivity, batch limits mentioned in both workflow sections and a dedicated 'Known Pitfalls' section), and the quick reference table largely duplicates information already covered in the workflows. The 'When to Use' section at the end is vacuous.

2 / 3

Actionability

The skill provides concrete tool names, parameter names, and formula syntax examples, which is good. However, there are no executable code/command examples showing actual MCP tool invocations with real parameter structures (e.g., JSON payloads). The guidance is specific but stops short of copy-paste ready examples of actual tool calls.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with labeled steps and prerequisite/optional annotations. However, there are no explicit validation checkpoints or feedback loops — for batch operations (chunking 10 records at a time) and destructive operations (delete), there's no verify-before-proceeding or error-recovery guidance, which caps this at 2 per the rubric.

2 / 3

Progressive Disclosure

The content is well-structured with clear headers and sections, but it's a monolithic document with no references to external files for detailed content. The formula syntax reference, quick reference table, and detailed pitfalls could be split into separate files. For a skill of this length (~150+ lines), inline everything is borderline.

2 / 3

Total

8

/

12

Passed

Description

40%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 a clear niche (Airtable via Composio/Rube MCP) which makes it distinctive, but it lacks specificity about what concrete actions it performs and completely omits an explicit 'Use when...' clause. The listed nouns (records, bases, tables, fields, views) hint at scope but don't convey actionable capabilities.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to create, read, update, or delete Airtable records, manage bases, or configure table schemas.'

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

Include natural user terms like 'database', 'spreadsheet', 'add row', 'lookup record' that users might say when they need Airtable functionality.

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

Describes a vague 'what' (automate Airtable tasks) but has no explicit 'when' clause — no 'Use when...' or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance, not a trigger condition. Per rubric, missing 'Use when...' caps completeness at 2, and the 'what' is also weak, so this scores 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', 'create record', 'update row', or 'Composio'. The term 'Rube MCP' is technical jargon unlikely to be used by users.

2 / 3

Distinctiveness Conflict Risk

The combination of 'Airtable' and 'Rube MCP (Composio)' creates a very specific niche that is unlikely to conflict with other skills. Airtable is a distinct product.

3 / 3

Total

8

/

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.

Validation10 / 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
administrakt0r/AI-Agents-Safe-Coding-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.