airtable-automation

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

Quality

45%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Discovery

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 specificity in what actions it performs and entirely omits explicit trigger guidance for when Claude should select this skill. The operational instruction about searching tools first is useful but doesn't compensate for the missing 'Use when...' clause.

Suggestions

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

Replace 'automate tasks' with specific concrete actions like 'create, update, delete, and query records; manage bases and tables; configure fields and views'.

Include natural trigger terms users might say, such as 'Airtable database', 'add a row', 'look up record', 'list entries', or 'manage Airtable data'.

Dimension	Reasoning	Score
Specificity	Names the domain (Airtable) and lists some entities (records, bases, tables, fields, views), but the actions are vague — 'automate tasks' doesn't specify concrete operations like create, update, delete, or query.	2 / 3
Completeness	Describes what at a high level (automate Airtable tasks) but has no explicit 'Use when...' clause or trigger guidance. The instruction to 'search tools first' is operational guidance, not a when-to-use trigger. Missing 'when' caps this at 2, and the 'what' is also weak, so scoring at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Airtable', 'records', 'bases', 'tables', 'fields', 'views', and 'Rube MCP (Composio)', but misses common user phrasings like 'spreadsheet', 'database', 'create record', 'update row', or 'list entries'.	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. The tool and platform are clearly identified.	3 / 3
	Total	8 / 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 Airtable automation skill with good coverage of operations, useful pitfall documentation, and clear tool sequencing. Its main weaknesses are the lack of executable invocation examples (actual tool call payloads), some content redundancy across sections, and missing validation/feedback loops for batch and destructive operations. The monolithic structure could benefit from splitting reference material into separate files.

Suggestions

Add concrete, copy-paste-ready examples of actual MCP tool invocations with JSON parameter structures for at least the most common operations (create record, list with filter, batch create).

Add explicit validation and error-recovery steps for batch operations: verify record count after batch create, handle partial failures, implement retry with backoff for 429 rate limits.

Remove the generic 'When to Use' and 'Limitations' boilerplate sections at the end—they add no actionable information and waste tokens.

Consolidate duplicate pitfall mentions (e.g., case-sensitive field names, batch limits) into a single reference section to reduce redundancy.

Dimension	Reasoning	Score
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 no value, and the quick reference table largely duplicates information already covered in the workflow sections. The ID formats section and batch limits are also partially redundant with inline pitfalls.	2 / 3
Actionability	The skill provides concrete tool names, parameter names, and formula syntax examples, which is good. However, it lacks 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	Workflows are clearly sequenced with labeled steps and prerequisite/optional annotations. However, for batch operations (creating/updating/deleting multiple records in chunks of 10), there are no explicit validation or feedback loop steps—no guidance on verifying success after each batch, handling partial failures, or retry logic for rate limits beyond mentioning 429 exists.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic document (~150 lines of dense content) with no references to external files. The formula syntax guide and detailed pitfalls could be split into separate reference files to keep the main skill leaner. For a skill with no bundle files, the inline organization is decent but not optimal.	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: boisenoise/skills-collections
Commit: 95574f3

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.