omni-sync-cloud

Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.

Quality

51%

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

Quality

Content

43%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 content is a well-sectioned API reference with concrete curl examples, but it is held back by an empty-payload pattern, duplicated overview text, slug-style headings, and the absence of any workflow sequencing or validation guidance for destructive operations. It offloads schema detail to the OpenAPI spec without inlining the essentials needed to act.

Suggestions

Replace empty `-d '{}'` payloads with representative request bodies (or inline the key fields) so the curl examples are immediately useful.

Add a short sequenced workflow with validation checkpoints for destructive/batch operations (e.g. auth → sync → verify bundle) rather than presenting a flat endpoint list.

Remove the verbatim duplicate of the description in the Overview and replace auto-generated slug headings ("GET sync › bundle") with descriptive labels.

Dimension	Reasoning	Score
Conciseness	The Overview repeats the frontmatter description verbatim and each endpoint pairs a slug-style heading (e.g. "GET sync › bundle", "DELETE sync › tokens › <id>") with a near-duplicate sentence, adding noticeable redundancy that could be tightened; it is not, however, padded with concepts Claude already knows.	3 / 5
Actionability	Each endpoint provides a concrete, copy-pasteable curl command with headers, but every mutating payload is an empty `-d '{}'` and request/response schemas are deferred to the OpenAPI spec, leaving key execution details missing.	3 / 5
Workflow Clarity	The body is a flat endpoint catalog with only loose grouping rather than a sequenced workflow, and destructive/batch operations (DELETE tokens, PUT credentials, sync) include no validation or verification steps.	2 / 5
Progressive Disclosure	Sections are organised and there is a clearly signalled one-level reference to the OpenAPI spec for schemas, but ~100 lines of endpoint reference are inlined in SKILL.md rather than split into a separate reference file.	3 / 5
	Total	11 / 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 what the skill does with several concrete, product-scoped actions, but lacks any explicit "Use when..." trigger guidance and relies on niche jargon over natural user phrases. It is distinct within the OmniRoute ecosystem yet would benefit from trigger phrasing and synonyms.

Suggestions

Add an explicit trigger clause, e.g. "Use when synchronising OmniRoute config to cloud, managing cloud worker auth, or setting up remote backup targets."

Include natural synonyms users might say ("backup", "restore", "sync settings", "cloud sync") alongside the product terms.

Reflect the full capability set (model resolution, aliases, token management) or narrow the description so it is not under-claiming relative to the body.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage" and "Manage cloud worker authentication and remote backup targets" — but omits capabilities shown in the body (model resolve, aliases, token management), so it falls short of comprehensive coverage at 5.	4 / 5
Completeness	The "what" is clear (sync config/connections/settings, manage auth and backup targets) but there is no "Use when..." trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant terms like "Synchronise", "cloud storage", "provider connections", and "remote backup targets" are present but heavily product-jargon-laden (OmniRoute, cloud worker) and lack common synonyms or natural phrasing variations a user might say.	3 / 5
Distinctiveness Conflict Risk	The OmniRoute-specific framing ("OmniRoute configuration", "cloud worker authentication") gives it a clear niche with low conflict risk, though generic terms like "cloud storage" and "backup" leave minor overlap with other cloud/backup skills.	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/omni-sync-cloud/SKILL.md
Commit: c3945a7

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