omni-db-backups

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

Quality

55%

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

45%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 a near-empty auto-generated stub: it efficiently states auth requirements and points to an external OpenAPI spec, but provides no executable backup/restore workflow, no validation steps, and only placeholder content for endpoints.

Suggestions

Provide a concrete backup/restore workflow with executable commands (e.g. the backup endpoint, file path, and restore procedure) instead of the 'No endpoints mapped' placeholder.

Add explicit validation checkpoints for destructive operations like restore (e.g. verify backup integrity before overwriting, confirm target before restore).

Inline a few key request/response examples for the most common backup and restore operations rather than deferring entirely to the OpenAPI spec.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean with no concept explanations Claude already knows; every line (auth requirement, OpenAPI pointer) earns its place.	5 / 5
Actionability	Only the auth endpoint and OpenAPI pointer are concrete; the core backup/restore/database tasks have no commands, code, or specific steps to execute.	2 / 5
Workflow Clarity	There is no sequenced workflow for backup or restore and no validation checkpoints despite these being destructive database operations, so steps are effectively missing.	1 / 5
Progressive Disclosure	Section headers exist and it points one level deep to an OpenAPI spec, but the core content is placeholder text ('No endpoints mapped for this area yet') rather than well-organized detail.	3 / 5
	Total	11 / 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 is concrete, third-person, and clearly scoped to a backup/restore niche, but it omits any explicit trigger guidance ('Use when...'), which caps completeness and limits its usefulness for skill selection.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to back up, restore, export, or import the SQLite database, or to manage snapshots.'

Include natural synonyms and file extensions (e.g. 'database dump', '.db', '.sqlite') to improve trigger-term coverage.

Tighten 'manage the SQLite database lifecycle' into more concrete actions to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Trigger system backups, restore from backup files, and manage the SQLite database lifecycle' plus 'export, import, and incremental snapshot strategies' — with only minor coverage gaps.	4 / 5
Completeness	It clearly answers 'what does this do' but contains no 'Use when...' or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural user-facing terms like 'backup', 'restore', 'export', 'import', and 'snapshot', though it omits common synonyms such as 'dump' or file extensions like '.db'.	4 / 5
Distinctiveness Conflict Risk	The SQLite-specific backup/restore/snapshot niche is mostly distinct from other skills, with only minor overlap risk against generic database utilities.	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: ea0cdc5

Reviewed: about 6 hours 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.