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.

80

1.37x
Quality

73%

Does it follow best practices?

Impact

96%

1.37x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

76%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 highly actionable with concrete tooling, parameters, and error guidance, and is well-structured for navigation. Its chief gap is the lack of explicit validation/feedback checkpoints on the batch and destructive record workflows.

Suggestions

Add explicit verification steps to batch/destructive workflows (e.g., after CREATE_RECORDS, confirm created record IDs in the response before proceeding; re-list to verify).

De-duplicate ID formats and batch limits between per-workflow Pitfalls and the Known Pitfalls section, or consolidate them in one place.

Optionally move the detailed Quick Reference table and formula syntax into a reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no concept tutorials), though the Known Pitfalls and Quick Reference sections restate ID formats and batch limits already covered per-workflow, leaving minor trimmable redundancy.

4 / 5

Actionability

Concrete tool slugs, exact parameter names, real error codes (422, 403, 429), ID format patterns, and executable formula syntax examples cover the common cases in copy-paste-ready detail.

5 / 5

Workflow Clarity

Tool sequences are clearly ordered with prerequisite markers, but batch/destructive workflows (CREATE_RECORDS, UPDATE/DELETE_MULTIPLE) lack explicit post-operation validation checkpoints, invoking the cap that holds workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized into Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference with no nested references and a single external docs link, though it is a self-contained monolith over 50 lines that could optionally split detailed reference material.

4 / 5

Total

16

/

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 is specific and clearly niched to Airtable via Rube MCP, with good natural keyword coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user wants to automate Airtable records, bases, tables, fields, or views').

Include concrete action verbs (create, list, update, delete) alongside the entity nouns to make capabilities more actionable.

Consider adding the common user phrasing 'Airtable base' or 'Airtable automation' as natural trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain and enumerates concrete entities ('records, bases, tables, fields, views') via a specific MCP path, listing several specific targets with only minor gaps in action verbs.

4 / 5

Completeness

Has a clear 'what' (automate Airtable tasks via Rube MCP over named entities) but no 'Use when...' clause, so the 'when' is only weakly implied, capping completeness at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Strong natural keyword coverage ('Airtable', 'records, bases, tables, fields, views') that users would actually say, though a few common phrasings and an explicit trigger clause are missing.

4 / 5

Distinctiveness Conflict Risk

The Rube MCP (Composio) Airtable framing is a clear, narrow niche with distinct triggers and minimal conflict 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
davepoon/buildwithclaude
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.