airtable-automation

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

1.37x

Quality

63%

Does it follow best practices?

Impact

96%

1.37x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/airtable-automation/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

A dense, highly actionable MCP tool reference with well-sequenced workflows and rich pitfall coverage. Its main weaknesses are duplicated content (batch limits, quick-reference table) and missing validation/feedback loops around destructive and batch operations, plus the absence of a single complete example tool call.

Suggestions

Add pre-flight validation to destructive workflows (e.g., 'List/filter records to confirm the target recordIds before DELETE_RECORD') and a post-batch check (verify record count after chunked CREATE_RECORDS).

Deduplicate the batch limits (stated in both workflow 1's Pitfalls and Known Pitfalls) and consider trimming the Quick Reference table to tools not already fully covered, or moving it plus the formula syntax guide to a reference file.

Include one complete example tool call with a full argument payload (e.g., AIRTABLE_CREATE_RECORD with baseId, tableIdOrName, and a populated fields object) to make the guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is a lean tool reference with no explanations of concepts Claude already knows, but it contains real duplication: the 10-record batch limit appears both in workflow 1's Pitfalls and in the Known Pitfalls section, and the Quick Reference table re-lists every tool and its key params already covered in the workflows — it could be tightened.	3 / 5
Actionability	Concrete, executable guidance throughout: exact tool slugs, numbered sequences tagged [Prerequisite]/[Required]/[Optional], named key parameters, and specific formula examples with escape rules ('{Status}='Done'', "double them ('John''s Company')"). The minor gap keeping it from anchor 5 is that no single complete example tool call payload (arguments included) is shown.	4 / 5
Workflow Clarity	Sequences are clearly ordered with prerequisite tags and the setup flow has validation checkpoints ('Confirm connection status shows ACTIVE before running any workflows'), but destructive and batch operations (DELETE_RECORD, UPDATE/CREATE_MULTIPLE_RECORDS) lack any verification-before-acting or post-batch confirmation steps, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ do not exist) and the skill is a single, well-sectioned SKILL.md whose content is appropriately inline for its compact size. It falls short of anchor 5 only because the Quick Reference table and the Airtable formula syntax guide are natural candidates for a separate reference file in a longer skill.	4 / 5
	Total	14 / 20 Passed

Description

65%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A distinct, domain-specific description with good natural trigger terms, but it is capped by a generic action verb ('Automate tasks') and the complete absence of 'when to use' guidance. Adding a 'Use when...' clause and one or two concrete actions would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Airtable, wants to create/update/delete records, or filter data in a base.'

Replace the generic 'Automate Airtable tasks' with concrete actions such as 'Create, update, and delete records; filter with formulas; manage fields and schema.'

Include a common synonym variation such as 'Airtable base' or 'Airtable database' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Automate Airtable tasks via Rube MCP (Composio)') and enumerates concrete object areas ('records, bases, tables, fields, views'), but the action verb is generic — no specific actions like create/update/delete/filter records are stated, matching anchor 3 rather than 4.	3 / 5
Completeness	'What' is clearly answered (automating Airtable records/bases/tables/fields/views via Rube MCP), but 'when to use it' is entirely absent — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	'Airtable' plus 'records, bases, tables, fields, views' are the natural terms users say when they need this skill, giving good keyword coverage; a few natural phrasings (e.g., 'Airtable database', 'Airtable sync', 'update records') are missing, so it does not reach anchor 5.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (Airtable automation through a specific MCP integration) with distinct trigger vocabulary; there is minimal risk of it firing for the wrong skill.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/airtable-automation/SKILL.md
Commit: c9856ea

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