airtable-automation

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

Quality

53%

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 ./plugins/antigravity-awesome-skills-claude/skills/airtable-automation/SKILL.md

Quality

Discovery

57%

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 via a specific MCP tool) which makes it distinctive, but it lacks specificity about what concrete actions it performs and omits an explicit 'Use when...' clause. The description would benefit from listing specific operations and adding natural trigger terms users would actually say.

Suggestions

Add specific concrete actions like 'create, update, delete, and query records; manage bases, tables, fields, and views' instead of the vague 'automate tasks'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to interact with Airtable, manage Airtable records, or automate Airtable workflows.'

Include more natural user-facing trigger terms like 'Airtable database', 'add rows', 'look up records', 'filter views' to improve matching.

Dimension	Reasoning	Score
Specificity	It names the domain (Airtable) and lists relevant nouns (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	The 'what' is partially addressed (automate Airtable tasks) but lacks specificity on concrete actions. There is no explicit 'Use when...' clause — the description only implies when it should be used. Per rubric guidelines, missing 'Use when' caps completeness at 2.	2 / 3
Trigger Term Quality	Includes 'Airtable', 'records', 'bases', 'tables', 'fields', 'views' which are relevant keywords, but 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. Missing natural phrases like 'spreadsheet database', 'create records', 'update rows'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Airtable' and 'Rube MCP (Composio)' creates a very clear niche. It's unlikely to conflict with other skills since Airtable is a specific product and the tooling is explicitly named.	3 / 3
	Total	9 / 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 structural organization, clear tool sequences, and useful pitfall documentation. Its main weaknesses are the lack of concrete executable examples (actual tool call payloads), missing validation/feedback loops for destructive and batch operations, and some redundancy across sections that inflates token usage without adding proportional value.

Suggestions

Add at least one concrete, executable example showing a full MCP tool call with actual JSON parameters (e.g., a complete AIRTABLE_CREATE_RECORD invocation) to improve actionability.

Add explicit validation checkpoints to batch and destructive workflows—e.g., 'Verify record exists before deleting' or 'After chunked create, list records to confirm count matches expected total'.

Consolidate repeated pitfalls (field name case sensitivity, 422 errors, batch limits) into the 'Known Pitfalls' section and reference it from workflows instead of duplicating across sections.

Remove the generic 'When to Use' and 'Limitations' boilerplate sections at the end, which add no skill-specific value.

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 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 feedback loops—for batch operations (chunking 10-record limits) and destructive operations (delete), there's no verify-before-proceeding or error-recovery guidance. The setup section has a good validation flow but core workflows lack it.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, 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 somewhat expected.	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: sickn33/antigravity-awesome-skills
Commit: b3869ba

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