CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

73

1.28x
Quality

71%

Does it follow best practices?

Impact

82%

1.28x

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/coda-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

A well-organized, largely actionable MCP workflow guide with exact tool slugs, parameters, and Coda-specific pitfalls that earns its place in context. Its main gaps are the missing validation step for batch row upserts (a workflow-clarity cap) and duplicated pitfall/rate-limit content that could be consolidated or offloaded to a reference file.

Suggestions

Add an explicit verification step after CODA_UPSERT_ROWS (e.g., re-fetch with CODA_LIST_TABLE_ROWS or inspect the returned added/updated counts) to close the feedback loop on batch writes.

Consolidate the duplicated pitfalls: rate limits and ID formats each appear twice (workflow sections plus Known Pitfalls) — keep a single canonical location and cross-reference it.

Move the 25-row Quick Reference table and per-workflow parameter lists into a references/ file (e.g., references/tool-reference.md) so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and the pitfalls are genuinely Coda-specific, but there is noticeable duplication: rate limits appear in the export pitfalls and again under Known Pitfalls, ID-format pitfalls repeat between section 1 and Known Pitfalls, "Always call RUBE_SEARCH_TOOLS first" appears in both Prerequisites and the description, and the 25-row Quick Reference table restates the tool listings from the workflows. This fits anchor 3 (mostly efficient but could be tightened) better than anchor 4's minor trimmable instances.

3 / 5

Actionability

Tool sequences name exact tool slugs in execution order with Required/Prerequisite/Optional labels, key parameters are enumerated per workflow, and concrete patterns are given (ID resolution chains, the 4-step row upsert pattern with keyColumns). It falls short of anchor 5 only because there are no copy-paste-ready call payloads (e.g., a worked example rows/keyColumns body for CODA_UPSERT_ROWS) covering the common cases.

4 / 5

Workflow Clarity

Sequences are clearly ordered with setup verification ("Confirm connection status shows ACTIVE") and an explicit poll-until-complete loop for exports, but the batch write operation CODA_UPSERT_ROWS has no validation/verification step (e.g., re-fetch rows or check the returned mutation counts). Per the judging guideline, missing validation in batch operations caps workflow clarity at 3, which takes precedence over the otherwise 4-level sequencing.

3 / 5

Progressive Disclosure

Good structure: six clearly headed workflows each with When-to-use, tool sequence, key parameters, and pitfalls, plus Common Patterns and Quick Reference sections; no bundle files exist and no references are dangling. Falls short of anchor 5 because the ~240-line single file inlines a large quick-reference table and full per-workflow parameter/pitfall detail that could live in a references/ file to keep SKILL.md a leaner overview.

4 / 5

Total

14

/

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.

A strong, specific description that clearly identifies its niche and enumerates the object areas it manages, with good natural trigger terms. Its main weakness is the absence of an explicit "Use when..." trigger clause, which both caps completeness and leaves the action verbs generic ("manage" covering everything).

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to search, read, or update Coda docs, tables, or rows, or publish/share a Coda document."

Replace the single generic verb "manage" with a few distinct concrete actions (e.g. "search docs, upsert table rows, export to markdown, share and publish").

Drop the meta-instruction "Always search tools first for current schemas" from the description and keep it in the body — it wastes description tokens without helping trigger selection.

DimensionReasoningScore

Specificity

"manage docs, pages, tables, rows, formulas, permissions, and publishing" names the domain and seven concrete object areas, but a single generic verb ("manage") covers them all rather than listing distinct actions like "search docs, upsert rows, export to markdown". This matches anchor 4 (several specific items, minor gaps) rather than anchor 5, and is clearly above anchor 3's 1-2 concrete actions.

4 / 5

Completeness

The "what" is clear (automate Coda document/data operations), but there is no "Use when..." clause or equivalent trigger guidance; the second sentence ("Always search tools first for current schemas") is a behavioral instruction, not a when-to-use trigger. Per the judging guideline, a missing explicit trigger clause caps completeness at 3 — a clear "what" with "when" only weakly implied.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("Coda", "docs", "tables", "rows", "formulas", "permissions", "publishing") plus integration names ("Rube MCP", "Composio"). Missing common variations a user might say ("Coda doc", "spreadsheet", "share") that would merit anchor 5, but well above anchor 3's sparse keyword coverage.

4 / 5

Distinctiveness Conflict Risk

"Automate Coda tasks via Rube MCP (Composio)" carves out a clear niche — the Coda product accessed through a specific MCP integration — with distinct triggers unlikely to fire for other document/table skills. It does not rely on generic phrasing like anchor 4's "PDF and Word document files"; every trigger term is Coda-qualified.

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.

Validation — 15 / 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

Path

plugins/all-skills/skills/coda-automation/SKILL.md

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.