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.

59

Quality

69%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/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

68%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, actionable MCP-tool reference with concrete slugs, parameter formats, and error codes, organized into clear sections. Its main weaknesses are the capped workflow clarity (no validation feedback loops for batch/destructive ops) and some duplicated content between Core Workflows and the Quick Reference / Known Pitfalls sections.

Suggestions

Add explicit validation/verification checkpoints before batch and destructive operations (e.g., verify record IDs and counts, then confirm before DELETE_MULTIPLE_RECORDS; chunk CREATE_RECORDS and verify each chunk's result) to lift workflow clarity above 3.

De-duplicate the Quick Reference table and Known Pitfalls batch-limit block against the inline Core Workflows content, or move them to a separate reference file to reduce redundancy and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the Known Pitfalls and Quick Reference sections duplicate tool slugs and batch limits already stated in Core Workflows, leaving minor redundancy that could be trimmed.

4 / 5

Actionability

Tool sequences name exact slugs (AIRTABLE_LIST_BASES, AIRTABLE_CREATE_RECORDS) with concrete parameter formats (app/tbl/rec IDs, 17 chars), specific limits (max 10/request, pageSize 100), and error codes (422, 403, 429), but there is no end-to-end worked example with a real baseId/table, a minor gap.

4 / 5

Workflow Clarity

Workflows are well-sequenced with [Prerequisite] markers and a setup checkpoint ('Confirm connection status shows ACTIVE'), but batch/destructive operations (CREATE_RECORDS, UPDATE_MULTIPLE, DELETE_MULTIPLE_RECORDS) lack explicit validate-before-proceeding feedback loops, so per the judging guideline workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

The single-file skill is well-organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with easy navigation, but at ~170 lines with no separate reference files for the duplicated Quick Reference / batch-limit tables, it sits just below a fully split 5.

4 / 5

Total

15

/

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.

A precise, domain-specific description with concrete object nouns and a clear integration mechanism, but it lacks any 'Use when...' trigger clause, which caps completeness. Distinctiveness is strong.

Suggestions

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

Consider naming the concrete actions (create/read/update/delete records, manage schema) rather than the single verb 'Automate' to lift specificity toward a 5.

DimensionReasoningScore

Specificity

The description lists several concrete Airtable objects ('records, bases, tables, fields, views') and names the integration mechanism ('via Rube MCP (Composio)'), though 'Automate' is a single generic verb rather than multiple distinct actions, keeping it just below the comprehensive 5 anchor.

4 / 5

Completeness

It gives a clear 'what' (Automate Airtable tasks: records, bases, tables, fields, views) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

It surfaces strong domain keywords a user would naturally say ('Airtable', 'records', 'bases', 'tables', 'fields', 'views') plus the integration name, but lacks synonyms or file/extension-style variations that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is precise — Airtable automation specifically via Rube MCP (Composio) — giving it distinct triggers with minimal overlap risk against 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.