CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

52

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/coda-automation/SKILL.md

The canonical home for this skill is coda-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive reference for Coda automation via Rube MCP with good workflow organization and clear tool sequencing. Its main weaknesses are the lack of concrete, executable examples (relying on pseudocode patterns instead), redundancy across sections (pitfalls repeated, quick reference duplicating workflows), and a monolithic structure that would benefit from splitting into separate reference files. The content is functional but could be significantly tightened and made more actionable.

Suggestions

Add at least one concrete, executable tool invocation example per core workflow showing actual parameter values (e.g., a real CODA_UPSERT_ROWS call with sample row data and keyColumns).

Consolidate pitfalls into the single 'Known Pitfalls' section and remove duplicated warnings from individual workflow sections to reduce redundancy.

Add a verification step to the upsert workflow (e.g., 'Call CODA_LIST_TABLE_ROWS or CODA_GET_A_ROW to confirm the upsert succeeded') to close the feedback loop.

Remove the vacuous 'When to Use' section at the end, as it adds no information beyond the description.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes redundant information across sections. The 'Pitfalls' subsections repeat information (e.g., ID formats mentioned in multiple workflows and again in 'Known Pitfalls'). The quick reference table largely duplicates the workflow sections. The 'When to Use' section at the end is vacuous. However, it avoids explaining basic concepts Claude already knows.

3 / 5

Actionability

The skill provides tool names, parameter lists, and sequenced steps, but lacks executable code examples — the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual API calls with concrete parameter values. There are no copy-paste ready examples showing actual tool invocations with sample data, which limits immediate executability.

3 / 5

Workflow Clarity

Workflows are clearly sequenced with labeled steps, prerequisite markers ([Required], [Optional], [Alternative]), and a setup verification flow. The export workflow includes polling guidance. However, the upsert workflow lacks explicit validation/verification steps (e.g., confirming rows were actually written correctly), and the permission workflow doesn't include verification of the permission being applied. These are minor gaps rather than missing feedback loops for destructive operations.

4 / 5

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's a long monolithic file (~200+ lines) with no bundle files to offload detailed content. The quick reference table, detailed pitfalls, and common patterns could be split into separate reference files. For a skill with this much content, having everything inline reduces navigability.

3 / 5

Total

13

/

20

Passed

Description

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

The description does a reasonable job listing the domain objects it can manage within Coda and identifies the specific integration (Rube MCP/Composio). However, it lacks an explicit 'Use when...' clause, which limits Claude's ability to know when to select this skill. The verb 'manage' is somewhat vague and could be strengthened with more specific operations.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Coda documents, Coda tables, or automating tasks in Coda.'

Replace the generic verb 'manage' with more specific actions like 'create, read, update, and delete' to improve specificity.

Include natural user trigger terms such as 'Coda spreadsheet', 'Coda database', or 'Coda automation' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists several specific actions: manage docs, pages, tables, rows, formulas, permissions, and publishing. These are concrete domain objects, though the verb 'manage' is somewhat generic and doesn't specify exact operations like create/update/delete.

4 / 5

Completeness

Has a clear 'what' (automate Coda tasks via Rube MCP, manage docs/pages/tables/etc.) but lacks an explicit 'when' clause. There is no 'Use when...' guidance telling Claude when to select this skill over others.

3 / 5

Trigger Term Quality

Includes relevant keywords like 'Coda', 'docs', 'pages', 'tables', 'rows', 'formulas', 'permissions', and 'publishing', but misses natural user phrases like 'spreadsheet', 'database', or 'Coda doc'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.

3 / 5

Distinctiveness Conflict Risk

The mention of 'Coda' and 'Rube MCP (Composio)' makes it fairly distinct and unlikely to conflict with generic document or table skills. Minor overlap risk exists with other table/spreadsheet management skills.

4 / 5

Total

14

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.