Tessl • The management layer for AI agent skills

SkillPublic

odoo-backup-strategy

Complete Odoo backup and restore strategy: database dumps, filestore backup, automated scheduling, cloud storage upload, and tested restore procedures.

Quality

82%

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

Quality

Content

82%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 strong, actionable skill body: executable scripts for backup, automation, offsite upload, and restore, with real Odoo-specific gotchas and explicit restore verification. The main gaps are missing in-script validation for the backup workflow and a slightly padded meta section.

Suggestions

Add error handling to the backup script (set -e, verify the dump is non-empty or run pg_restore --list) so failures surface immediately.

Trim the 'How It Works' meta section; it duplicates the 'When to Use This Skill' section.

Consider moving advanced topics from Limitations (multi-database looping, restic/rsync incremental backups) to a one-level-deep reference file.

Dimension	Reasoning	Score
Conciseness	The body is lean and focuses on Odoo-specific knowledge Claude can't be assumed to have (filestore path, the pg_restore --clean gotcha, 3-2-1 rule), but the 'How It Works' meta section and emoji-decorated do/don't bullets are minor padding that could be trimmed.	4 / 5
Actionability	Four complete, copy-paste-ready bash examples cover the common cases: manual backup (pg_dump -Fc + tar), cron automation, S3 upload with retention pruning, and a full restore sequence — matching the fully-executable anchor.	5 / 5
Workflow Clarity	The restore sequence is clearly ordered with an explicit verification step (login, records, attachments) and backup integrity checking via pg_restore --list appears in Best Practices. However, the backup script itself has no validation or error handling (no set -e, no dump check) and there is no feedback loop for a failed restore, placing it between anchors 4 and 5.	4 / 5
Progressive Disclosure	Sections are well-organized (Overview, When to Use, Examples, Best Practices, Limitations) and self-contained with no nested references. It misses a 5 because at ~107 lines it exceeds the under-50-line simple-skill exception, and advanced topics noted in Limitations (multi-database setups, restic/rsync) could live in a referenced file.	4 / 5
	Total	17 / 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.

A specific, well-scoped description with concrete enumerated capabilities and strong distinctiveness, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause and a few natural synonyms (PostgreSQL, pg_dump) would raise it further.

Suggestions

Append an explicit trigger clause, e.g., 'Use when setting up or testing Odoo backups, scheduling automated database dumps, or restoring an Odoo instance after failure.'

Add natural synonyms users would say such as 'PostgreSQL' or 'pg_dump' to broaden trigger coverage.

Drop the 'Complete' qualifier to avoid over-claiming; the enumerated capability list already conveys scope.

Dimension	Reasoning	Score
Specificity	Enumerates five concrete capabilities — 'database dumps, filestore backup, automated scheduling, cloud storage upload, and tested restore procedures' — giving comprehensive coverage of the backup/restore lifecycle, matching the score-5 anchor.	5 / 5
Completeness	The 'what' is clear and enumerated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'Odoo', 'backup', 'restore', 'filestore', and 'database dumps' are present, but common variations users would say (e.g., 'PostgreSQL', 'pg_dump', 'disaster recovery') are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	'Complete Odoo backup and restore strategy' is a clearly niched, unambiguous domain with distinct triggers; minimal conflict risk with other skills, matching the score-5 anchor.	5 / 5
	Total	17 / 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-backup-strategy/SKILL.md
Revision: 64adc55

Reviewed: 14 days ago

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.

odoo-backup-strategy

Table of Contents

Is this your skill?