cli-backup-sync

Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

Quality

48%

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/cli-backup-sync/SKILL.md

Quality

Content

37%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 skill is a flat command reference that lists flags and bare commands but provides no real workflow, validation, or example arguments for destructive operations like restore and sync. It is also a monolithic inlining that should be split into a reference file.

Suggestions

Add a concrete end-to-end workflow with validation checkpoints for the destructive/batch operations (e.g., backup create -> verify status -> restore [backupId] --list -> confirm before restore).

Replace bare-command examples with realistic invocations showing actual flag values (e.g., 'omniroute backup create --name daily --cloud --encrypt --key-file ./key').

Move the bulk command/flag reference into a separate REFERENCE.md file and keep SKILL.md as a concise overview with a clearly signaled link.

Dimension	Reasoning	Score
Conciseness	Mostly lean reference-style listings of subcommands and flags with minimal padding; the only redundancy is the overview duplicating the description verbatim. Falls between 3 and 5, closer to 4.	4 / 5
Actionability	Examples are merely the bare command with no arguments (e.g., 'omniroute backup create' with no example values), and flags are listed without types or example usage; guidance is high-level and missing the specific steps to actually run a backup.	2 / 5
Workflow Clarity	There is no sequenced workflow for the destructive/batch operations (backup, restore, sync); validation/verification steps are entirely absent, and per rubric guidance destructive skills without validation cannot score above 3, placing this at 2 with rough-but-gapped structure.	2 / 5
Progressive Disclosure	No bundle files exist, yet ~350 lines of command reference are inlined monolithically into SKILL.md with no navigation aids; content that clearly belongs in a separate reference file is inlined, matching the score-2 anchor.	2 / 5
	Total	10 / 20 Passed

Description

58%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 but omits any 'Use when...' trigger guidance, capping its completeness. Trigger term coverage is decent but lacks synonyms and natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user wants to back up or restore OmniRoute data, schedule backups, or sync to cloud storage').

Include common synonyms/file extensions users might say, such as 'snapshots', 'archive files (.tar, .zip)', and 'cloud sync' to broaden trigger coverage.

Tighten distinctiveness by referencing the OmniRoute-specific context up front so it does not overlap with generic backup skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files'), which is several specific actions; falls between score 3 (1-2 actions) and 5 (comprehensive), closer to 4.	4 / 5
Completeness	Has a clear 'what' (backup/restore actions) but no 'when' / 'Use when...' clause is present; the rubric caps completeness at 3 when explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	Includes relevant keywords like 'backup', 'restore', 'snapshots', and 'cloud storage', but misses common natural variations/synonyms a user might say (e.g., 'archive files', 'cloud sync', file extensions) and lacks explicit trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	Focused on OmniRoute-specific backup/sync operations, making it mostly distinct with only minor overlap risk against generic backup skills; not quite a 5 because the triggers are not concretely phrased.	4 / 5
	Total	14 / 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/cli-backup-sync/SKILL.md
Commit: ea0cdc5

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.