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.
79
72%
Does it follow best practices?
Impact
87%
1.81xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/0x7466/coda/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 in specificity and distinctiveness, clearly identifying Coda as the target platform and listing concrete CRUD operations across multiple entity types. However, it lacks an explicit 'Use when...' clause, which is important for Claude's skill selection, and could benefit from more natural user-facing trigger terms beyond technical API language.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Coda documents, Coda tables, or wants to interact with the Coda API.'
Include more natural trigger terms users might say, such as 'Coda doc', 'Coda spreadsheet', 'Coda workspace', or 'coda.io'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: listing/creating/updating/deleting docs, managing tables/rows/pages, triggering automations, exploring doc structure. Also mentions specific requirements like CODA_API_TOKEN and behavioral constraints around delete and publishing operations. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the capabilities described, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Coda', 'docs', 'tables', 'rows', 'pages', 'automations', and 'REST API', but misses common user-facing variations like 'spreadsheet', 'Coda doc', or file-type references. Users might say 'Coda' but the description lacks a broader set of natural trigger phrases. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Coda documents via REST API v1, with specific mention of CODA_API_TOKEN. The 'Coda' platform reference and API-specific details make this highly distinctive and unlikely to conflict with other document management 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 concrete CLI examples and good safety guardrails for destructive operations. Its main weaknesses are moderate verbosity (some sections explain things Claude already knows, like HTTP status codes and basic security practices) and a monolithic structure that could benefit from splitting detailed patterns and reference material into separate files.
Suggestions
Remove or significantly trim the Error Handling section (standard HTTP codes) and Security Considerations (basic token hygiene) as these are things Claude already knows.
Split Common Patterns, Examples, and Rate Limit details into separate reference files, keeping SKILL.md as a concise overview with links to those files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some sections that could be tightened—e.g., the 'When to Use' and 'When NOT to Use' sections are somewhat obvious given the description, and the Security Considerations section states things Claude already knows (don't commit tokens to version control). The error handling section listing standard HTTP codes is also largely redundant. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every operation, with specific flags, arguments, and realistic examples including doc IDs, table IDs, and JSON data payloads. The commands are fully executable assuming the CLI tool exists. | 3 / 3 |
Workflow Clarity | Multi-step workflows like sync between docs and batch operations are clearly sequenced. Safety guardrails include explicit confirmation requirements for destructive operations, and the rate limit section documents automatic backoff. The delete operations have clear validation checkpoints (confirmation required, preview shown). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, but it's a fairly long monolithic file. The API reference, common patterns, and detailed examples could be split into separate files. The Reference section at the bottom links to external docs, but there are no internal file references for advanced topics. | 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.
- Repository
- openclaw/skills
- Commit
07a4057
- 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.