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?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/airtable-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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 concrete executable examples (actual tool call payloads), missing validation/error-recovery loops for batch and destructive operations, and some redundancy across sections. The formula syntax guide and ID format reference are genuinely useful additions.

Suggestions

Add concrete, copy-paste-ready examples of actual MCP tool calls with JSON parameter structures (e.g., a complete RUBE_SEARCH_TOOLS call followed by AIRTABLE_CREATE_RECORD with a real fields object).

Add explicit validation and error-recovery loops for batch operations: e.g., 'chunk into groups of 10 → call CREATE_RECORDS → check response for errors → retry failed chunks'.

Consolidate duplicate pitfall information (field name case sensitivity, 422 errors, batch limits) into the 'Known Pitfalls' section and reference it from workflows instead of repeating.

Remove the generic 'When to Use' and 'Limitations' boilerplate sections at the end—they add no actionable information beyond what the description and prerequisites already convey.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy—pitfalls are repeated across sections (e.g., field name case sensitivity, 422 errors), the quick reference table largely duplicates the workflow tool sequences, and the boilerplate 'When to Use' and 'Limitations' sections at the end add little value. The ID format section and batch limits are useful but could be more compact.

2 / 3

Actionability

The skill provides specific tool names, parameter names, and formula syntax examples, which is good. However, it lacks any concrete executable examples showing actual MCP tool calls with real parameter structures (e.g., JSON payloads). The guidance is specific enough to follow but stops short of copy-paste ready invocations.

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 error recovery loops—particularly important for batch operations (chunking 10-record batches) and destructive deletes. The setup section has a good verification flow, but core workflows lack feedback loops for error handling.

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. Given the length (~150+ lines) and the amount of reference material (formula syntax, ID formats, quick reference table), some content could be split into separate reference files. However, with no bundle files provided, this is a reasonable single-file approach.

2 / 3

Total

8

/

12

Passed

Description

40%

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 Rube MCP/Composio) which makes it distinctive, but it lacks concrete action verbs describing what it can do and entirely omits a 'Use when...' clause. The listed terms (records, bases, tables, fields, views) are entity nouns rather than actionable capabilities, leaving Claude without strong guidance on when to select this skill.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks to create, read, update, or delete Airtable records, manage bases, or configure table fields and views.'

Replace the noun list with specific concrete actions, e.g., 'Create, update, and delete Airtable records; manage bases and tables; configure fields and views; query and filter data.'

Remove or de-emphasize the internal instruction ('Always search tools first for current schemas') from the description, as it is operational guidance rather than skill-selection information.

DimensionReasoningScore

Specificity

Names the domain (Airtable) and lists some entities (records, bases, tables, fields, views) but these are nouns rather than concrete actions. The only action mentioned is 'search tools first for current schemas,' which is an internal instruction rather than a user-facing capability.

2 / 3

Completeness

Partially addresses 'what' (automate Airtable tasks) but lacks any explicit 'when' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is vague enough ('automate tasks') that this falls to a 1.

1 / 3

Trigger Term Quality

Includes 'Airtable', 'records', 'bases', 'tables', 'fields', 'views' which are relevant keywords, but misses natural user phrases like 'create a record', 'update a table', 'manage my Airtable base', or 'spreadsheet database'. 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Airtable' and 'Rube MCP (Composio)' creates a very clear niche. It is unlikely to conflict with other skills since Airtable is a specific product and the tooling context is explicit.

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
sickn33/antigravity-awesome-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.