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:haniakrim21/everything-claude-code --skill airtable-automation69
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/skillValidation 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 specific tooling) but lacks concrete action verbs and explicit trigger guidance. The absence of a 'Use when...' clause significantly weakens Claude's ability to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Airtable, needs to manage database records, or references Composio/Rube MCP'
Replace the noun list (records, bases, tables) with specific action phrases like 'create and update records, query tables, manage field schemas, configure views'
Include common user language variations such as 'no-code database', 'spreadsheet database', or 'add/edit rows'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Airtable) and lists general categories (records, bases, tables, fields, views) but doesn't describe specific 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 'spreadsheet', 'database', or action-oriented terms like 'add row', 'lookup'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly specific to Airtable via Rube MCP (Composio), which is a distinct niche unlikely to conflict with other skills due to the specific platform and integration mentioned. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
85%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 via Rube MCP. Its strengths are excellent organization, clear workflow sequences with validation steps, and comprehensive pitfall documentation. The main weakness is the lack of concrete, executable examples showing actual tool invocations with sample parameters.
Suggestions
Add at least one complete executable example showing a full tool invocation with actual parameter values (e.g., a RUBE_SEARCH_TOOLS call followed by AIRTABLE_CREATE_RECORD with sample fields object)
Include a concrete example of filterByFormula usage in context, showing the full AIRTABLE_LIST_RECORDS call with the formula parameter
| 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 excellent token-efficient summary. | 3 / 3 |
Actionability | While tool sequences and parameters are clearly listed, there are no executable code examples or copy-paste ready commands. The guidance is specific but remains at the level of tool names and parameter descriptions rather than concrete invocation examples. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional). The setup section includes explicit validation checkpoints (verify connection is ACTIVE before proceeding), and pitfalls sections provide error recovery guidance. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections progressing from setup to core workflows to common patterns. The quick reference table at the end provides efficient navigation. External toolkit docs are linked appropriately without deep nesting. | 3 / 3 |
Total | 11 / 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.