airtable-automation

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

1.54x

Quality

58%

Does it follow best practices?

Impact

96%

1.54x

Average score across 3 eval scenarios

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 automation) and lists relevant data concepts, but lacks concrete action verbs and critically missing explicit trigger guidance for when Claude should select this skill. The operational instruction about searching tools first doesn't help with skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Airtable, needs to manage Airtable records, or references Airtable bases/tables'

Replace generic nouns with specific action verbs: 'Create, read, update, and delete Airtable records; manage bases, tables, fields, and views'

Include common user phrases like 'Airtable database', 'add rows to Airtable', or 'query Airtable data'

Dimension	Reasoning	Score
Specificity	Names the domain (Airtable) and lists general categories (records, bases, tables, fields, views) but doesn't describe concrete actions like 'create records', 'query tables', or 'update fields'.	2 / 3
Completeness	Describes what it does (automate Airtable tasks) but lacks any explicit 'Use when...' clause or trigger guidance. The instruction to 'search tools first' is operational guidance, not selection criteria.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Airtable', 'records', 'bases', 'tables', 'fields', 'views' but misses common user phrases like 'spreadsheet', 'database', 'add row', or file extensions.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Airtable specifically via Rube MCP/Composio - this is a distinct niche unlikely to conflict with other database or spreadsheet skills.	3 / 3
	Total	8 / 12 Passed

Implementation

77%

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

This is a well-structured skill that efficiently documents Airtable automation workflows with clear tool sequences and comprehensive pitfall documentation. The main weakness is the lack of concrete executable examples showing actual API calls with sample data. The content organization is good but could benefit from splitting detailed reference material into separate files.

Suggestions

Add concrete JSON examples showing actual tool calls with sample baseId, tableIdOrName, and fields values for at least the create/update record workflows

Include a sample filterByFormula request and response to demonstrate pagination handling in practice

Consider splitting the formula syntax reference and ID format documentation into a separate REFERENCE.md file to improve progressive disclosure

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Airtable is or how APIs work. Every section provides actionable information without padding, and the quick reference table is an excellent token-efficient summary.	3 / 3
Actionability	Provides clear tool sequences and parameter lists, but lacks executable code examples. The guidance is specific (tool names, parameter formats, ID patterns) but would benefit from concrete JSON request/response examples showing actual usage.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional). The setup section includes explicit validation checkpoints (verify connection, confirm ACTIVE status). Pitfalls sections provide error recovery guidance for each workflow.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and a useful quick reference table, but everything is in a single file. For a skill of this length (~180 lines), some content like the formula syntax reference or detailed pitfalls could be split into separate files for better navigation.	2 / 3
	Total	10 / 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: 5c5ae21

Reviewed: 3 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.