CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-rpc-api

Expert on Odoo's external JSON-RPC and XML-RPC APIs. Covers authentication, model calls, record CRUD, and real-world integration examples in Python, JavaScript, and curl.

59

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-rpc-api/SKILL.md

The canonical home for this skill is odoo-rpc-api 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.

A well-organized, mostly executable skill body with solid examples and best practices, weakened by missing validation steps around destructive record operations and incomplete CRUD example coverage relative to the description's promise.

Suggestions

Add a validation/verification step to the create workflow (e.g. check the returned ID is truthy and handle Odoo AccessError), and show update (write) and delete (unlink) examples to fulfill the promised CRUD coverage.

Trim the redundant note about /web/dataset/call_kw (the sentence says Odoo 16+ "also supports" it and then says to "prefer" the same endpoint) and remove the JSON-RPC 2.0 spec comment that Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly lean and well-organized with minimal over-explanation, but contains minor padding such as the contradictory/redundant note on /web/dataset/call_kw and the JSON-RPC-spec comment Claude already knows, keeping it just below a 5.

4 / 5

Actionability

Three copy-paste-ready executable examples (xmlrpc auth+search_read, create, curl JSON-RPC) cover the common cases, but the description promises full CRUD while examples only demonstrate Create and Read — a minor gap versus the comprehensive coverage of a 5.

4 / 5

Workflow Clarity

The Activate→Generate→Debug sequence and inline numbered steps are present, but state-changing record operations (create/update/delete) have no validation checkpoint (e.g. verify the returned ID, check for errors), so the destructive/batch cap holds workflow clarity at 3.

3 / 5

Progressive Disclosure

Clear section structure (Overview, When to Use, How It Works, Examples, Best Practices, Limitations) with no nested references and easy navigation, but the ~95-line body keeps everything inline with no one-level-deep references, so it does not reach the ideal split structure of a 5.

4 / 5

Total

15

/

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 specific, well-targeted description of Odoo RPC capabilities, but it omits an explicit "Use when…" trigger clause, which caps completeness at 3 and is the main weakness.

Suggestions

Add an explicit trigger clause, e.g. "Use when integrating an external app with Odoo via JSON-RPC/XML-RPC, or when the user mentions Odoo API, Odoo RPC, or external Odoo integration."

Include a couple of natural synonyms ("web service", "remote procedure call") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names several concrete capabilities — "authentication, model calls, record CRUD" plus integration examples in three languages — which is "several specific actions; minor gaps" rather than the comprehensive, non-overlapping action list of a 5 (model calls and CRUD partially overlap).

4 / 5

Completeness

The "what" is clear (Odoo external RPC APIs covering auth/model calls/CRUD), but there is no "Use when…" clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "Odoo", "JSON-RPC", "XML-RPC", "API", "integration", "Python", "JavaScript", "curl" — that a user would plausibly say, but misses common synonyms like "web service" or "remote procedure call" that would merit a 5.

4 / 5

Distinctiveness Conflict Risk

"Odoo's external JSON-RPC and XML-RPC APIs" is a clear, narrowly-scoped niche with distinct triggers and minimal realistic overlap with other skills.

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.

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.