omni-db-backups

Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.

Quality

60%

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 ./skills/omni-db-backups/SKILL.md

Quality

Content

55%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 reasonably concise and well-structured with executable curl examples, but it documents endpoints unrelated to the skill's stated backup/restore purpose and lacks any sequenced workflow or validation for destructive restore operations. Actionability and workflow clarity are the main weaknesses.

Suggestions

Replace or supplement the env/repair and version examples with the actual backup, restore, and SQLite export/import endpoints including sample payloads.

Add a numbered backup/restore workflow with explicit validation checkpoints (e.g., verify backup integrity before overwrite, confirm restore target) since restore is destructive.

Remove the verbatim duplicate of the description in the Overview section to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean curl commands with little concept over-explanation, but the Overview duplicates the frontmatter description verbatim and the 'GET system › env › repair' breadcrumb lines repeat the headings, offering minor trim opportunities.	4 / 5
Actionability	Concrete, executable curl examples are provided, but they cover env/repair and version endpoints rather than the backup/restore/SQLite endpoints the skill is actually for, and payloads are deferred to the OpenAPI spec, leaving key details missing.	3 / 5
Workflow Clarity	No sequenced backup/restore workflow is presented and validation checkpoints are entirely absent, which is especially problematic given restore is a destructive operation; only a rough endpoint listing exists.	2 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Authentication, Endpoints, Payloads) and bulk schema detail is appropriately delegated to the OpenAPI spec, with only minor organization gaps and no nested references.	4 / 5
	Total	13 / 20 Passed

Description

66%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 communicates concrete capabilities around backups, restore, and SQLite lifecycle, but omits any explicit 'when to use' trigger guidance, capping its completeness. Overall it is solid but would benefit from a trigger clause.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when the user asks to back up, restore, or export the SQLite database').

Replace the broad 'manage the SQLite database lifecycle' with one or two specific actions to push specificity toward a 5.

Include natural synonyms or file extensions users might say (e.g., '.db', '.sqlite', 'snapshot') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Trigger system backups', 'restore from backup files', 'export, import, and incremental snapshot strategies' — but 'manage the SQLite database lifecycle' is broad, leaving minor coverage gaps versus a comprehensive 5.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like 'system backups', 'restore from backup files', 'SQLite database', and 'incremental snapshots' are present and would be said by users, though a few synonyms/extensions and an explicit trigger clause are missing.	4 / 5
Distinctiveness Conflict Risk	The SQLite backup/restore niche is fairly distinct with specific triggers, though 'export/import' and general database management carry minor overlap risk with adjacent skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: diegosouzapw/OmniRoute
Path: skills/omni-db-backups/SKILL.md
Commit: c3945a7

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.