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 known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/omni-db-backups/SKILL.md

Quality

Content

52%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise but mostly a stub: it lacks the executable backup/restore guidance and sequenced workflow that the description promises, and the endpoints section is explicitly empty. It needs concrete commands, a documented workflow, and validation steps to be genuinely actionable.

Suggestions

Document the actual backup/restore workflow with concrete commands (e.g. export/import invocation, snapshot creation) replacing the '_No endpoints mapped for this area yet._' placeholder.

Add validation/verification checkpoints for these destructive/batch database operations so workflow clarity is not capped at 2.

Provide at least one example request/response or payload to move actionability from guidance toward copy-paste-ready instruction.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of padded concept explanations, adding only authentication and pointer notes; every section earns its place without restating what Claude already knows.	3 / 3
Actionability	Some concrete guidance exists (the auth endpoint, the OpenAPI spec path), but there is no executable backup/restore command or example payload for the skill's core actions, leaving key details missing.	2 / 3
Workflow Clarity	The core backup/restore workflow is essentially absent — the Endpoints section says '_No endpoints mapped for this area yet._' — with no sequenced steps and no validation checkpoints for these destructive/batch operations.	1 / 3
Progressive Disclosure	Sections are present and point one level deep to the OpenAPI spec, but the references are external API/CLI paths rather than organized bundle files, and the content is too thin to demonstrate well-signaled navigation.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 clearly scoped to SQLite backups/restores, but it lacks an explicit 'when to use' trigger clause and relies on somewhat technical language rather than natural user terms. Adding a 'Use when...' sentence would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when backing up or restoring a SQLite database, importing/exporting data, or creating incremental snapshots.'

Add natural user phrasings like 'dump', 'rollback', or '.db files' alongside the technical 'incremental snapshot strategies'.

Keep the concrete action list — it is already strong on specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Trigger system backups, restore from backup files, and manage the SQLite database lifecycle' plus 'export, import, and incremental snapshot strategies' — matching the top anchor for several specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' or equivalent trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant terms like 'backups', 'restore', 'SQLite database', and 'export/import' are present, but common natural user phrasings ('backup my database', 'rollback', '.db files', 'dump') are missing and 'incremental snapshot strategies' reads as technical jargon.	2 / 3
Distinctiveness Conflict Risk	The SQLite-database-backup niche with explicit lifecycle and snapshot language is clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: 3070925

Reviewed: 2 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.