CtrlK
BlogDocsLog inGet started
Tessl Logo

airtable-automation

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

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-airtable-automation/SKILL.md

The canonical home for this skill is airtable-automation in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body is a dense, concrete operational reference with specific tools, parameters, and pitfalls, but it suffers from internal duplication, lacks validation/feedback loops around batch and destructive operations, and keeps all reference material in a single inlined file. The placeholder Example section also weakens actionability.

Suggestions

Add validation/feedback loops to batch and delete workflows (e.g., verify expected record counts before/after bulk operations, confirm deletions) to lift the workflow_clarity cap.

De-duplicate by folding the "Quick Reference" table and "Known Pitfalls" section into the Core Workflows, or move them into a separate reference file.

Replace the placeholder "Example" section with a concrete worked example showing actual tool calls, inputs, and expected responses.

DimensionReasoningScore

Conciseness

Mostly an efficient operational reference with no concept over-explanation, but the "Quick Reference" table and "Known Pitfalls" section substantially duplicate content already presented in "Core Workflows".

3 / 5

Actionability

Provides concrete tool sequences, exact parameters, error codes (422, 403), and limits (10 records, 100 pageSize), but the "Example" section only echoes the description rather than showing a worked tool-call example.

4 / 5

Workflow Clarity

Numbered tool sequences carry [Prerequisite]/[Optional] markers, but batch (CREATE_RECORDS) and destructive (DELETE) workflows lack validation/feedback loops, capping clarity at 3 per the rubric's feedback-loop guidance.

3 / 5

Progressive Disclosure

Sections are well-organized in a single file, but no references/scripts/assets bundle exists and reference material (Quick Reference table, formula syntax) is inlined rather than split into navigable files.

3 / 5

Total

13

/

20

Passed

Description

70%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 its concrete object model and is highly distinct, but it omits an explicit "Use when..." trigger clause and uses a generic verb in place of specific actions. Adding trigger guidance and enumerating concrete operations would raise completeness and specificity.

Suggestions

Add an explicit "Use when..." clause with concrete trigger phrases (e.g., "Use when the user wants to create, read, update, or delete Airtable records, bases, or fields via Rube MCP").

Replace the generic verb "Automate" with specific actions (create, read, update, delete records; manage schema/fields) to increase specificity.

Include common synonyms (spreadsheet, database) alongside "Airtable" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists concrete Airtable objects ("records, bases, tables, fields, views") but relies on a single generic verb ("Automate") rather than enumerating specific actions such as create/update/delete.

4 / 5

Completeness

Has a clear "what" ("Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views") but no "Use when..." clause, so "when" is only weakly implied — capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("Airtable", "records", "bases", "tables", "fields", "views") plus "Rube MCP"/"Composio", but misses common synonyms like "spreadsheet" or "database".

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Airtable via Rube MCP/Composio) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
boisenoise/skills-collections
Reviewed

Table of Contents

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.