coda
General-purpose Coda document manager via REST API v1. Supports listing/creating/updating/deleting docs, managing tables/rows/pages, triggering automations, and exploring doc structure. Requires CODA_API_TOKEN environment variable. Delete operations require explicit confirmation; publishing and permission changes require explicit user intent.
78
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
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.
This description excels at specificity and distinctiveness by clearly naming the Coda platform and listing concrete CRUD operations. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when needing Coda help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Coda, needs to manage Coda documents, or wants to interact with Coda tables and automations.'
Include more natural user-facing trigger terms like 'Coda workspace', 'Coda spreadsheet', or task phrases like 'add rows to Coda' or 'create a Coda doc'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'listing/creating/updating/deleting docs, managing tables/rows/pages, triggering automations, and exploring doc structure.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with comprehensive capability listing, but lacks an explicit 'Use when...' clause. The 'when' is only implied through the capability descriptions. | 2 / 3 |
Trigger Term Quality | Includes 'Coda', 'REST API', 'docs', 'tables', 'rows', 'pages', 'automations' which are relevant but misses natural user phrases like 'spreadsheet', 'database', or common task-oriented terms users might say. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct with 'Coda' as a specific product name, 'CODA_API_TOKEN' requirement, and Coda-specific terminology (docs, tables, automations). Unlikely to conflict with other document or API skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent CLI examples and strong safety guardrails for destructive operations. The workflow clarity is particularly good with explicit confirmation requirements and rate limit documentation. However, it could be more concise by removing explanations of concepts Claude already knows and better structured through progressive disclosure to separate reference material from the core overview.
Suggestions
Remove or condense the 'When NOT to Use' section and security considerations that explain obvious concepts (e.g., don't commit tokens)
Consider splitting detailed patterns (batch operations, sync workflows, error handling) into a separate REFERENCE.md or PATTERNS.md file, keeping SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When NOT to Use' that Claude could infer, and the security considerations section explains concepts Claude already knows (e.g., 'Never commit tokens to version control'). | 2 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples throughout. Commands are copy-paste ready with clear parameter placeholders and real-world usage patterns like batch operations and syncing between docs. | 3 / 3 |
Workflow Clarity | Clear workflows with explicit safety guardrails for destructive operations (delete requires confirmation, publish requires --confirm-publish flag). Rate limit handling and async operation polling are well-documented with specific thresholds. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is somewhat monolithic. The reference links at the end are good, but detailed patterns like batch operations and sync workflows could be split into separate reference files for a cleaner overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.