airtable-automation

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./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.

The content is a dense, well-structured, highly actionable reference for Airtable via Rube MCP with clear tool sequences and concrete pitfalls. Its main weaknesses are some redundancy and generic closing boilerplate affecting conciseness, and the absence of validation feedback loops around destructive batch operations.

Suggestions

Add explicit validate/verify steps around destructive batch operations (e.g. 'Verify record IDs and field names via GET_BASE_SCHEMA before DELETE_MULTIPLE_RECORDS; confirm count after deletion').

De-duplicate the ID-format and batch-limit notes that appear in both per-workflow pitfalls and the 'Known Pitfalls' section, and trim the generic 'When to Use'/'Limitations' boilerplate.

Consider splitting the quick-reference table and formula-syntax reference into a separate REFERENCE.md to improve progressive disclosure, or explicitly state that no external references are needed.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material, but ID formats and batch limits are repeated across workflow pitfalls and the 'Known Pitfalls' section, and the closing 'When to Use'/'Limitations' boilerplate ('This skill is applicable to execute the workflow or actions described in the overview.') adds padding that could be tightened.	3 / 5
Actionability	Concrete tool slugs, exact parameter names, ID formats, HTTP error codes (422/403/429), formula syntax examples, and a quick-reference table give mostly executable, copy-ready guidance, with only minor gaps (no example full tool-call payloads).	4 / 5
Workflow Clarity	Workflows are clearly sequenced with [Prerequisite]/[Optional]/[Required] tags and a setup validation checkpoint, but destructive/batch operations (CREATE_RECORDS, UPDATE_MULTIPLE, DELETE_MULTIPLE) lack explicit validate-before/verify-after feedback loops, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-organized file with clear section headers covering workflows, patterns, pitfalls, and a quick-reference table; minor gaps remain since reference-style content (formula syntax, quick reference) is inlined rather than split out.	4 / 5
	Total	14 / 20 Passed

Description

66%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.

The description clearly names the domain and concrete object types and is well-scoped to a distinct niche, but it lacks an explicit 'Use when...' trigger clause, which limits its completeness score. Verb coverage is also thin beyond the generic 'Automate'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to automate Airtable records, bases, tables, fields, or views via Rube MCP.'

Strengthen action verbs beyond 'Automate' (e.g. 'create, read, update, delete records; inspect base schemas') to lift specificity.

Include common user synonyms such as 'Airtable database' or 'sync records' to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete Airtable object areas ('records, bases, tables, fields, views') and the mechanism ('Rube MCP (Composio)'), but the only verb is the generic 'Automate', so it lists several specific targets without fully comprehensive action coverage.	4 / 5
Completeness	The 'what' is clear ('Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views') but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms like 'Airtable', 'records', 'bases', 'tables', 'fields', 'views' are terms users actually say, but common variations such as 'database', 'sync', or spreadsheet phrasing are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Airtable via Rube MCP (Composio)' niche is mostly distinct with clear triggers, though minor overlap risk exists with other Composio/Rube MCP toolkit skills.	4 / 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: sickn33/antigravity-awesome-skills
Path: skills/airtable-automation/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours 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.