CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

63%

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

Quality

Content

32%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 an auto-generated CLI catalog that is concrete in naming commands and flags but fails as skill guidance: examples duplicate their headings without real invocations, no workflows are sequenced or validated, and the entire API reference is inlined rather than progressively disclosed. It reads as raw generator output rather than a curated skill.

Suggestions

Move the bulk of the subcommand/flag reference into a references/ file (e.g., CLI_REFERENCE.md) and keep SKILL.md as a concise overview with pointers.

Replace the placeholder examples with real executable invocations that demonstrate flag usage, e.g. "omniroute backup create --name daily --encrypt --key-file ~/.backup.key --retention 7".

Add a sequenced workflow for the core backup/restore and sync bundle/import paths with explicit validation steps (e.g., run "omniroute backup status" or "--list" before "backup restore", use "sync import --dry-run" first), especially since restore/revoke are destructive.

DimensionReasoningScore

Conciseness

Nearly every "Example:" block merely restates its heading (e.g., "### backup disable" followed by "omniroute backup disable") and unrelated cloud task-management commands pad the file, so roughly half the ~315 lines add no information.

2 / 5

Actionability

The install command and flag lists are concrete, but the examples are placeholder-laden and not executable as written ("omniroute backup restore [backupId]", "omniroute cloud get <taskId>", "omniroute backup create" with no flags shown), and flag semantics are never explained.

3 / 5

Workflow Clarity

The document is a flat command catalog with no sequencing for multi-step flows (backup → verify → restore; bundle → import), and destructive/batch operations like "backup restore", "sync revoke", and "cloud cancel" have no validation or verification guidance beyond a bare --yes flag.

2 / 5

Progressive Disclosure

There are no bundle files or external references; ~300 lines of full CLI API reference are inlined directly in SKILL.md, matching the anchor example of API reference content that clearly belongs in a separate file (headers exist, so not a 1).

2 / 5

Total

9

/

20

Passed

Description

75%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.

A strong, specific description that clearly states what the skill does with concrete verbs and product-scoped triggers. Its main weakness is the complete absence of a "Use when..." clause, which both caps completeness and leaves triggering to inference.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions backing up, restoring, exporting, or syncing OmniRoute data, or asks about backup schedules or snapshots."

Add common user-facing synonyms such as "export", "import", and "incremental backup" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists five concrete actions ("Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files"), matching the comprehensive multi-action anchor; coverage within the stated scope has no minor gaps that would justify a 4.

5 / 5

Completeness

The "what" is clearly stated (backup/restore/sync/schedule OmniRoute data), 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 terms like "backup", "restore", "snapshots", "sync", and "archive files" give good keyword coverage, but common variations users might say (e.g., "export/import", "incremental backup", "migration") are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a named product ("Backup and restore OmniRoute data from the CLI") with distinct backup/restore/snapshot triggers, giving it a clear niche with minimal conflict risk against generic file or cloud-sync skills.

5 / 5

Total

17

/

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

Revision

5b3be70

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill