omni-auth

Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the OmniRoute API.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/omni-auth/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable for core auth operations and points clearly to external references, but it mixes in a broad migrated OmniRoute overview, repeats the description, and lacks an explicit sequenced auth workflow with verification checkpoints.

Suggestions

Remove the duplicated Overview text and trim marketing fluff in the differentiators section to keep the auth skill focused and token-efficient.

Add a numbered authenticate→use→verify workflow that shows how to obtain the initial token and confirm it with the health check before proceeding.

Move the general OmniRoute overview, capability skills, and CLI skills tables out of this auth skill (or behind a single clearly-signaled reference) so the body stays scoped to authentication.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete curl examples, but the Overview duplicates the description and the differentiators section carries marketing fluff ('this is the only AI router...', 'never stop coding'), so it could be tightened rather than earning a lean 3.	2 / 3
Actionability	Provides concrete, executable curl commands for login/logout/health/models and error→action mappings, but the described initial-token and session-cookie acquisition flows lack executable support (the login example already requires a Bearer token), leaving key details incomplete.	2 / 3
Workflow Clarity	There are validation signals (the health check returning {"ok":true} and error→retry mappings), but there is no sequenced authenticate→use→verify workflow, so checkpoints are implicit rather than an explicit numbered flow.	2 / 3
Progressive Disclosure	External capability/CLI skill URLs are well-signaled via one-level-deep tables, but general OmniRoute overview content (differentiators, capability skills) is inlined inside an auth skill that should be a focused overview, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	8 / 12 Passed

Description

75%

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 is specific and uses natural trigger terms, but it lacks an explicit 'Use when...' trigger clause and its action vocabulary is generic enough to risk overlap with similar skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when authenticating to the OmniRoute API, obtaining or refreshing Bearer tokens, or managing session cookies.'

Include common natural variations users might say ('auth', 'log in', 'get a token') to broaden trigger coverage.

Tie the trigger terms more tightly to the OmniRoute-specific scope to reduce overlap with generic auth skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions ('Manage API key authentication', 'obtain session cookies', 'configure login requirements', 'authenticate requests via Bearer token'), matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage of a 2.	3 / 3
Completeness	Clearly states what the skill does, but the 'when' is only implied via 'Start here' rather than an explicit 'Use when...' clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Uses natural developer-facing keywords a user would say when needing auth ('API key', 'authentication', 'session tokens', 'Bearer token', 'login'), giving good coverage; it leans slightly technical but stays below jargon-only language.	3 / 3
Distinctiveness Conflict Risk	Scoping to 'the OmniRoute API' gives a niche, but the action terms (authenticate, API key, tokens) are generic and could overlap with sibling OmniRoute or general auth skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	10 / 12 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-auth/SKILL.md
Commit: 3070925

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.