coda-automation
Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas.
69
58%
Does it follow best practices?
Impact
82%
1.28xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/coda-automation/SKILL.mdQuality
Discovery
67%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 strong on specificity and distinctiveness, clearly identifying the Coda platform and listing concrete entity types it manages. However, it lacks an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are adequate but lean toward internal/technical naming rather than natural user language.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Coda documents, Coda tables, or automating tasks in Coda.'
Include natural user-facing trigger terms like 'Coda doc', 'Coda spreadsheet', 'Coda database', or 'Coda automation' to improve matching against typical user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage docs, pages, tables, rows, formulas, permissions, and publishing. Also specifies the mechanism (Rube MCP via Composio) and a procedural instruction (search tools first for current schemas). | 3 / 3 |
Completeness | Clearly answers 'what' (automate Coda tasks via Rube MCP with specific capabilities listed), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the mention of Coda tasks. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Coda', 'docs', 'pages', 'tables', 'rows', 'formulas', 'permissions', 'publishing', but misses common user phrasings like 'spreadsheet', 'Coda doc', or variations users might naturally say. 'Rube MCP' and 'Composio' are technical/internal terms unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Coda specifically via Rube MCP (Composio), which is a distinct niche. The combination of platform (Coda), mechanism (Rube MCP/Composio), and specific entity types (docs, pages, tables, rows, formulas) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 API integration skill that covers the Coda toolkit comprehensively with clear workflow sequences and useful pitfall documentation. Its main weaknesses are the lack of concrete, executable examples (actual tool call payloads), some content redundancy across sections, and missing validation/feedback loops for destructive operations like publishing and permission changes. The monolithic structure could benefit from splitting detailed reference material into separate files.
Suggestions
Add concrete, executable tool call examples with sample parameters and expected response shapes (e.g., a complete CODA_UPSERT_ROWS call with actual row data and keyColumns values).
Add explicit validation/verification steps after destructive operations—e.g., after CODA_UPSERT_ROWS, verify with CODA_GET_A_ROW; after CODA_ADD_PERMISSION, verify with CODA_GET_SHARING_METADATA.
Consolidate the duplicated pitfalls content—either keep pitfalls inline per workflow OR in the Known Pitfalls section, not both.
Consider splitting the Quick Reference table and Known Pitfalls into a separate REFERENCE.md to reduce the main file's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some redundancy—pitfalls are repeated across sections and in the 'Known Pitfalls' summary, and some information (like ID formats) appears multiple times. The quick reference table duplicates information already covered in the workflows. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | The skill provides clear tool names, parameter lists, and sequenced steps, which is good. However, the 'code' examples are pseudocode-style numbered lists rather than executable commands or actual API call examples with concrete payloads. There are no copy-paste-ready examples showing actual tool invocations with sample parameters and expected responses. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Alternative, which is helpful. However, the async export workflow lacks explicit polling loop guidance (e.g., retry intervals, max attempts), and the upsert workflow doesn't include a validation/verification step to confirm rows were written correctly. Missing feedback loops for destructive operations like permission changes and publishing cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table. However, at ~200 lines it's quite long for a single file with no bundle files to offload detail into. The detailed pitfalls, common patterns, and quick reference table could be split into separate reference files. The single external link to Composio docs is appropriate but the skill itself is somewhat monolithic. | 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
d065ead
- 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.