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.

60

Quality

71%

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

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

The content is a well-structured, actionable reference for Coda automation via Rube MCP, with clear tool sequences and parameters. Its main gap is the absence of validation checkpoints for batch and destructive operations, and no full example payloads.

Suggestions

Add explicit verification steps after batch/destructive operations, e.g. 'After CODA_UPSERT_ROWS, call CODA_LIST_TABLE_ROWS to confirm the changes' and 'Verify sharing via CODA_GET_SHARING_METADATA after ADD_PERMISSION'.

Include at least one filled-in example tool call (with realistic argument values) for a common case such as an upsert or URL resolution.

Reduce duplication between the per-workflow Pitfalls, the Known Pitfalls section, and the Quick Reference table to tighten token use.

DimensionReasoningScore

Conciseness

The body is dense, actionable reference material that avoids explaining concepts Claude already knows, though the Quick Reference table and Known Pitfalls section restate some per-workflow content.

4 / 5

Actionability

Concrete tool slugs, named parameters, and ordered sequences give mostly executable guidance, but no filled-in example tool-call payloads with real argument values are provided.

4 / 5

Workflow Clarity

Sequences are clearly numbered, but batch/destructive operations (UPSERT_ROWS, PUBLISH_DOC, ADD_PERMISSION) lack explicit validation/verification checkpoints, capping this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized into Prerequisites, Setup, six Core Workflows, Common Patterns, Known Pitfalls, and a Quick Reference table; as a single-file skill (~240 lines) with no bundle files, structure is good with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

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

The description is specific and distinctive, clearly naming Coda and a comprehensive set of operations. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Coda docs, tables, rows, formulas, permissions, or publishing.'

Consider natural synonyms such as 'Coda docs', 'Coda tables', or 'Coda spreadsheet' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'manage docs, pages, tables, rows, formulas, permissions, and publishing' — giving comprehensive coverage of the skill's scope.

5 / 5

Completeness

The 'what' is clear (automate Coda tasks, listed operations) but there is no 'Use when...' or equivalent explicit trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'Coda' plus docs/pages/tables/rows/formulas/permissions/publishing gives good natural-keyword coverage, but no synonyms or file-style extensions are included.

4 / 5

Distinctiveness Conflict Risk

'Coda' is a specific product niche with distinct triggers, and the listed operations are Coda-specific, yielding minimal conflict risk with other skills.

5 / 5

Total

17

/

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.

Validation15 / 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
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.