CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omni-db-backups

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

57%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 lean, executable API reference with copy-paste curl commands, but it suffers from redundant echo lines, version-specific details, and a non-bundle reference for payloads. Critically, none of the documented endpoints (env repair, metrics, version) cover the backup/restore/SQLite operations the description promises, and destructive operations lack any validation guidance.

Suggestions

Document the actual backup, restore, and SQLite export/import endpoints the description promises, including expected request payloads for the POST operations instead of empty '-d "{}"' bodies.

Add validation/verification steps for destructive operations (e.g., verifying a backup file before restore, checking repair results) so restore/repair workflows have explicit checkpoints.

Remove the redundant "GET/POST system › ..." echo lines under each endpoint header and move version-specific details like "(rail 3.8.54)" to a release-notes or deprecated section; reference a real bundle file for payload schemas since docs/openapi.yaml does not exist in the bundle.

DimensionReasoningScore

Conciseness

Curl examples are lean, but each endpoint header is duplicated by a redundant echo line (e.g., "GET system › env › repair" under "### GET /api/system/env/repair") and time-sensitive version info ("rail 3.8.54") appears outside a deprecated/old-patterns section, which the guidelines penalize.

3 / 5

Actionability

Every endpoint has a concrete, copy-paste-ready curl command with auth headers, but POST examples send empty bodies ("-d '{}'") and payload schemas are delegated to an external OpenAPI spec, leaving minor gaps.

4 / 5

Workflow Clarity

The skill's stated purpose includes destructive operations (restore, env repair) and database operations, but the body provides no step sequencing or validation/verification guidance, capping workflow clarity at 3; individual endpoint calls are unambiguous, keeping it above 2.

3 / 5

Progressive Disclosure

Sections are organized with headers and payload detail is deferred, but the main detail pointer "docs/openapi.yaml" is not a file in the bundle, and the inlined endpoint reference content is the kind of material that belongs in a separate reference file.

3 / 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 states concrete capabilities with mostly natural trigger terms, but it entirely lacks a "when to use" clause and misses common synonyms and file extensions. It is reasonably distinct from other skills thanks to its backup/restore/SQLite focus.

Suggestions

Add an explicit trigger clause such as "Use when the user asks to back up, restore, export, or import the SQLite database, or mentions .db/.sqlite files or snapshots."

Include common synonyms and file extensions (e.g., "dump", ".db", ".sqlite", "back up the database") to improve trigger term coverage.

Replace the vague phrase "manage the SQLite database lifecycle" with the specific lifecycle operations actually supported.

DimensionReasoningScore

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 generic, leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clear (backup, restore, export/import, snapshots), 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 keywords like "backups", "restore", "export", "import", and "snapshot" are present, but common variations and file extensions ("dump", ".db", ".sqlite", "back up") are missing.

4 / 5

Distinctiveness Conflict Risk

The backup/restore/SQLite niche is mostly distinct with clear triggers, though the broad phrase "manage the SQLite database lifecycle" creates minor overlap risk with general database skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.