airtable-automation
Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill airtable-automation72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 96%
↑ 1.54xAgent success when using this skill
Validation for skill structure
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 automation via Rube MCP) but lacks specificity about concrete actions and completely omits trigger guidance for when to use the skill. The technical reference to 'Rube MCP (Composio)' is helpful for distinctiveness but the description would benefit from explicit user-facing trigger terms and a 'Use when...' clause.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Airtable, needs to manage database records, or references bases/tables'
Replace generic 'automate tasks' with specific actions like 'Create, read, update, and delete records; manage table schemas; configure views'
Include common user phrases like 'database', 'add entry', 'lookup record', or 'sync data' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airtable) and lists general categories (records, bases, tables, fields, views) but doesn't describe concrete actions like 'create records', 'query tables', or 'update fields'. | 2 / 3 |
Completeness | Describes what it does (automate Airtable tasks) but completely lacks a 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Airtable', 'records', 'bases', 'tables', 'fields', 'views' which are relevant keywords, but misses common user phrases like 'database', 'spreadsheet', 'add row', or 'lookup'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly targets Airtable specifically via Rube MCP/Composio, which is a distinct niche unlikely to conflict with other database or spreadsheet skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently documents Airtable automation workflows with clear sequencing and comprehensive pitfall documentation. The main weakness is the lack of concrete executable examples showing actual tool calls with sample inputs/outputs. The content is appropriately concise but could benefit from splitting detailed reference material into separate files.
Suggestions
Add concrete examples showing actual tool calls with sample baseId, tableIdOrName, and fields values to improve actionability
Include an example showing a complete workflow from listing bases to creating a record with actual parameter values
Consider splitting the formula syntax reference and pagination patterns into a separate REFERENCE.md file for better progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Airtable is or how APIs work. Every section provides actionable information without padding, and the quick reference table is an efficient format for lookup. | 3 / 3 |
Actionability | Provides clear tool sequences and parameter lists, but lacks executable code examples. The guidance is specific (tool names, parameter formats, formula syntax) but would benefit from concrete copy-paste examples showing actual API calls with sample data. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and labeled prerequisites. Each workflow includes explicit validation points (checking connection status, verifying schema before operations) and documents pitfalls that serve as implicit checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a useful quick reference table, but it's a fairly long monolithic document. Some content like the detailed formula syntax or pagination patterns could be split into separate reference files for better navigation. | 2 / 3 |
Total | 10 / 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 | |
- 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.