CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-automated-tests

Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests. Covers test data setup, mocking, and CI integration.

63

Quality

75%

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-automated-tests/SKILL.md

The canonical home for this skill is odoo-automated-tests in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 body is highly actionable with complete, executable examples and a clean structure, but its workflow sequencing lacks explicit validation checkpoints for the run-and-debug loop, and a little meta-process prose could be trimmed.

Suggestions

Add an explicit feedback loop in the run/debug flow: run tests, inspect failures, fix, re-run until green.

Tighten the 'Overview' and 'How It Works' sections to remove restatement of the description and skill-usage meta-steps.

Consider moving the longer example classes into a references/ file, leaving the key pattern inline in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and commands, but the Overview partly restates the description and 'How It Works' (Activate/Generate/Run) is meta-process padding that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TransactionCase and HttpCase classes with imports/setup/assertions and complete CLI commands covering module-, tag-, and class-level test runs.

5 / 5

Workflow Clarity

A rough write-run-debug sequence is implied, but there are no explicit validation checkpoints or a feedback loop for interpreting failures and retrying — matching the 'steps present but checkpoints missing' anchor.

3 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections and no nested references; minor gap that the ~118-line Examples block could be externalized into reference files.

4 / 5

Total

16

/

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 distinct, naming concrete test types and capabilities, but it is missing an explicit 'Use when...' trigger clause, which caps completeness. Adding natural-language trigger phrases would round it out.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when writing Odoo unit tests, HTTP controller tests, or running tests in CI').

Include common user-facing synonyms like 'Odoo unit tests', 'Odoo test cases', or 'Odoo CI tests' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — write/run tests with TransactionCase, HttpCase, and browser tour tests, plus test data setup, mocking, and CI integration — matching the 'comprehensive coverage' anchor.

5 / 5

Completeness

Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good keyword coverage (Odoo automated tests, TransactionCase, HttpCase, CI integration), but leans technical and misses common natural variations like 'Odoo unit tests' or 'how to test an Odoo module'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Odoo test framework with named TestCase classes) with distinct triggers and minimal overlap 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.