Name: odoo-docker-deployment
Rating: 61.6 (1 reviews)
Author: administrakt0r

odoo-docker-deployment

Production-ready Docker and docker-compose setup for Odoo with PostgreSQL, persistent volumes, environment-based configuration, and Nginx reverse proxy.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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-docker-deployment/SKILL.md

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

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 content is highly actionable, with copy-paste-ready configs and commands and tight, low-padding prose. Its main gap is workflow clarity: the deploy and backup flows lack explicit validation checkpoints, which caps that dimension.

Suggestions

Add a sequenced deploy workflow with a verification checkpoint, e.g. after `docker compose up -d`, run `docker compose ps` / curl the health endpoint and only declare success when Odoo and the DB report healthy.

Add a validation/feedback loop around the backup command, e.g. verify the SQL dump is non-empty and restorable before treating backup as complete.

Consider splitting the tuning/production notes into a short reference file referenced from SKILL.md to demonstrate one-level-deep progressive disclosure for the deeper material.

Dimension	Reasoning	Score
Conciseness	The body is lean executable yaml/ini/bash with high-signal inline comments (worker formula, deprecated version note) rather than concept explanation; only the generic Overview and How-It-Works prose adds minor padding, keeping it just below the every-token-earns-its-place anchor 5.	4 / 5
Actionability	It ships a complete docker-compose.yml, odoo.conf, and a command set with concrete values (pinned images, ports, worker tuning, pg_dump backup), all copy-paste ready and covering the common start/log/restart/stop/backup/update cases.	5 / 5
Workflow Clarity	How It Works gives Activate->Generate->Debug and commands are listed, but there is no sequenced deploy workflow with validation checkpoints, and the pg_dump backup over a live DB is a db operation without verify/feedback steps, triggering the missing-validation cap of 3.	3 / 5
Progressive Disclosure	The skill is self-contained in SKILL.md with clean, navigable sections and a single clearly-signaled one-level external link; no bundle files exist, so it is appropriately organized, though it does not demonstrate the multi-file progressive-disclosure pattern that would reach anchor 5.	4 / 5
	Total	16 / 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.

The description clearly scopes a distinct Odoo-on-Docker niche with concrete component specifics, but lacks any explicit 'when to use' trigger clause, which caps completeness. It is otherwise strong and free of vague fluff.

Suggestions

Add an explicit trigger clause, e.g. 'Use when deploying or containerizing Odoo with Docker, or troubleshooting an Odoo Docker setup.'

Reframe component lists as concrete actions (e.g. 'Deploy Odoo with PostgreSQL, configure persistent volumes and env-based secrets, add an Nginx reverse proxy') to reach the comprehensive-action bar.

Drop or justify the marketing adjective 'production-ready', which adds no triggerable information.

Dimension	Reasoning	Score
Specificity	Names the Odoo/Docker domain plus several concrete components (PostgreSQL, persistent volumes, env-based config, Nginx reverse proxy), but lists parts rather than discrete actions and 'production-ready' is mild puffery, so it sits below the comprehensive-action anchor 5.	4 / 5
Completeness	It has a clear 'what' but no 'Use when...' clause or equivalent trigger guidance, so per the missing-trigger cap it cannot exceed 3 despite the solid capability statement.	3 / 5
Trigger Term Quality	'Docker', 'docker-compose', 'Odoo', 'PostgreSQL', 'Nginx reverse proxy' are natural terms a user would say, but synonyms and situational phrases like 'deploy/host Odoo' or file extensions are missing, fitting the 'good coverage, a few terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	'Production-ready Docker ... setup for Odoo with PostgreSQL ... Nginx reverse proxy' carves a clear niche with distinct triggers and minimal overlap risk; voice is correctly third person.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-docker-deployment/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.