CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omni-providers

Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's provider catalog.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

53%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 well-structured navigation index over a real one-level-deep reference file, with a few genuinely executable curl examples. Its weaknesses are the duplicated endpoint catalog, the absence of payload examples for core CRUD operations, and no validation guidance for the destructive and bulk operations it exposes.

Suggestions

Replace the 78-line endpoint link list with a short categorized summary (e.g., CRUD, auth/import, health/metrics) pointing to references/endpoints.md, since that file already contains its own table of contents.

Add minimal request/response payload examples for the core operations (POST /api/providers, PATCH /api/providers/{id}) instead of deferring all schemas to the OpenAPI spec.

Add validation guidance for destructive and batch operations — e.g., verify a provider's health via the test endpoint or health-matrix before and after DELETE or bulk import operations.

DimensionReasoningScore

Conciseness

The 78-line endpoint link catalog duplicates the table of contents that exists inside references/endpoints.md itself, so a large block of the body could be collapsed into a single pointer. There is no concept over-explanation, but the duplication is a significant amount of unnecessary tokens, fitting level 3 (mostly efficient but could be tightened) rather than level 4.

3 / 5

Actionability

The custom section provides fully executable curl examples for three endpoints and the Authentication section gives a concrete login path, but the core CRUD operations (add/update provider) have no request-body examples — payloads are deferred wholesale to the OpenAPI spec. This is concrete guidance that is incomplete for the skill's primary use cases, matching level 3.

3 / 5

Workflow Clarity

The auth prerequisite ("Obtain a token via POST /api/auth/login") establishes a first step, but there is no sequence or validation guidance for the destructive and batch operations the skill exposes (DELETE /api/providers/{id}, bulk imports, apply-local). Per the guidelines, missing validation for destructive/batch operations caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The body is structured as an overview pointing one level deep to a real, verified bundle file (references/endpoints.md with matching anchors), with links clearly signaled and payload detail deferred to the OpenAPI spec. It falls short of level 5 because the "Additional endpoints" custom section duplicates endpoints (refresh, health-matrix) already listed in the main link catalog, a minor organization gap.

4 / 5

Total

13

/

20

Passed

Description

71%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, action-oriented description with concrete verbs and a well-defined niche in OmniRoute's provider catalog. Its main gap is the complete absence of a "Use when..." trigger clause, which caps completeness and slightly weakens trigger discoverability.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "List, add, update, remove, and test AI provider integrations" plus "API keys, OAuth flows, and connection tests" — giving comprehensive coverage of the skill's capabilities. It matches the level-5 anchor (multiple specific concrete actions) and exceeds level 4, which allows coverage gaps.

5 / 5

Completeness

The "what" is clearly and explicitly stated (manage connections, keys, OAuth flows, tests; list/add/update/remove/test), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

It includes good natural keywords users would say — "provider connections", "API keys", "OAuth", "connection tests", "REST API" — but misses common variations like "credentials" or naming specific providers. This fits the level-4 anchor (good coverage, a few natural terms missing) rather than level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Scoping to "OmniRoute's provider catalog" and REST API provider management gives it a clear, named niche with distinct triggers, though it could mildly overlap with generic API-key or credentials-management skills. This sits between level 4 (mostly distinct, minor overlap) and level 5, closer to 4.

4 / 5

Total

16

/

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-providers/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.