airtable-automation

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

1.37x

Quality

41%

Does it follow best practices?

Impact

96%

1.37x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/airtable-automation/SKILL.md

Quality

Discovery

32%

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 target platform (Airtable) and lists relevant entities but lacks concrete action verbs describing what the skill can do and entirely omits a 'Use when...' clause. The internal instruction about searching tools first is operational guidance rather than a useful discriminator for skill selection. The description needs more specific capabilities and explicit trigger conditions.

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 the noun list with concrete action verbs, e.g., 'Create, update, and delete records; manage bases and tables; configure fields and views in Airtable.'

Remove internal implementation details ('Always search tools first for current schemas') and replace with user-facing trigger terms like 'Airtable database', 'Airtable automation', or 'Airtable API'.

Dimension	Reasoning	Score
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 answers 'what' (automate Airtable tasks) but very weakly, and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' should cap completeness at 2, and the 'what' is also vague enough to warrant 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 be used by users.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Airtable' specifically provides some distinctiveness, but the generic terms 'records', 'tables', 'fields', 'views' could overlap with database or spreadsheet skills. The mention of 'Rube MCP (Composio)' adds some specificity to the tooling but doesn't help distinguish the use case.	2 / 3
	Total	7 / 12 Passed

Implementation

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 reference skill that covers Airtable operations comprehensively with good structural organization, clear tool sequences, and useful pitfall documentation. Its main weaknesses are the lack of executable invocation examples, missing validation/verification steps in workflows (especially for batch and destructive operations), and some redundancy across sections that inflates token usage. The content would benefit from concrete call examples and explicit feedback loops.

Suggestions

Add at least one complete, executable tool invocation example per core workflow (e.g., a full AIRTABLE_CREATE_RECORD call with realistic baseId, tableIdOrName, and fields values).

Add explicit validation/verification steps after destructive and batch operations — e.g., after DELETE, call LIST_RECORDS to confirm removal; after batch CREATE, verify record count matches expected.

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

Consider splitting the formula syntax guide and quick reference table into separate bundle files to reduce the main SKILL.md size and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy — pitfalls are repeated across sections (e.g., field name case sensitivity, 422 errors), the ID formats table duplicates info mentioned inline, and the quick reference table largely restates the workflow sections. Some trimming would improve token efficiency.	2 / 3
Actionability	The skill provides concrete tool names, parameter names, and formula syntax examples, which is good. However, it lacks executable examples showing actual tool invocations with realistic parameter values (e.g., a complete RUBE_SEARCH_TOOLS call or AIRTABLE_CREATE_RECORD call with sample fields). The guidance is specific but stops short of copy-paste ready.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with labeled steps and prerequisite/optional annotations. However, there are no explicit validation checkpoints or feedback loops — for example, after creating records there's no step to verify success, and batch operations (which have hard limits) lack chunking/retry logic. For destructive operations like DELETE, there's no confirmation or verification step.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and a logical hierarchy, but it's a monolithic document (~150+ lines) with no bundle files to offload detailed reference material. The formula syntax guide, quick reference table, and detailed pitfalls could be split into separate reference files. The single external link to Composio docs is appropriate but insufficient for progressive disclosure.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: 364c6b2

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.