airtable-automation
Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.
63
45%
Does it follow best practices?
Impact
96%
1.37xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/airtable-automation/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (Airtable via Rube MCP/Composio) which makes it distinctive, but it lacks concrete action verbs and has no explicit 'Use when...' clause to guide skill selection. The mention of entities (records, bases, tables, fields, views) provides some useful keywords but the overall description reads more like a label than actionable selection guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, read, update, or delete Airtable records, manage bases, or configure table schemas.'
Replace 'Automate Airtable tasks' with specific concrete actions like 'Create, update, delete, and query Airtable records; manage bases, tables, fields, and views.'
Include natural trigger terms users might say, such as 'add a row to Airtable', 'look up Airtable record', 'list Airtable tables', or 'sync Airtable data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airtable) and lists some entities (records, bases, tables, fields, views), but the actions are vague — 'automate tasks' doesn't specify concrete operations like create, update, delete, or query. | 2 / 3 |
Completeness | Describes what at a high level (automate Airtable tasks) but has no explicit 'Use when...' clause or equivalent trigger guidance, and the operational instruction ('Always search tools first') is implementation detail rather than selection guidance. Missing 'when' caps this at 2, but the 'what' is also weak, so scoring 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Airtable', 'records', 'bases', 'tables', 'fields', 'views', and 'Rube MCP (Composio)', but misses common user phrases like 'create a record', 'update a table', 'list bases', or 'airtable automation'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Airtable' and 'Rube MCP (Composio)' creates a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent reference skill for Airtable automation that covers the major operations with clear tool sequences and useful pitfall documentation. Its main weaknesses are the lack of concrete executable examples (actual tool call invocations), missing validation checkpoints for destructive operations, and a monolithic structure that could benefit from splitting reference material into separate files. The content is moderately efficient but has notable redundancy between sections.
Suggestions
Add at least one complete, concrete example showing an actual tool call with real parameter values and expected response structure for a common workflow (e.g., creating a record).
Add explicit validation/confirmation checkpoints before destructive operations (delete, batch update) — e.g., 'List records first to verify selection before deleting' with a feedback loop for error recovery.
Extract the formula syntax reference, quick reference table, and known pitfalls into separate linked files (e.g., FORMULAS.md, REFERENCE.md) to reduce the main skill's token footprint and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally well-structured but includes some redundancy — pitfalls are repeated across sections (e.g., field name case sensitivity, batch limits mentioned in both workflow sections and a dedicated 'Known Pitfalls' section), and the quick reference table largely duplicates information already covered in the workflows. The ID format details and some parameter descriptions could be tightened. | 2 / 3 |
Actionability | Tool sequences are clearly named and parameters are specified, but there are no concrete executable examples showing actual tool calls with real parameter values. The formula syntax section is helpful but the core workflows remain at the level of 'call this tool with these params' without showing a complete example invocation and expected response. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps and prerequisite/optional annotations, which is good. However, for destructive operations (delete records, update records, batch operations), there are no explicit validation or confirmation checkpoints — no 'verify before proceeding' or error recovery loops. The pagination pattern describes the loop but doesn't include a validation step for completeness. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, but it's a long monolithic file (~150+ lines of dense content). The formula syntax reference, quick reference table, and detailed pitfalls could be split into separate reference files. The only external reference is the Composio toolkit docs link. For a skill this comprehensive, better use of linked sub-documents would improve navigation. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- 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.