omni-budget

Configure spending limits, token quotas, and rate-limit policies per API key or globally. Inspect current consumption and enforce cost controls across providers.

Quality

66%

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

Quality

Content

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

A compact, well-structured API reference with executable curl examples, but it is held back by an empty POST payload example, deferred schemas, and a missing verify step after config updates. Inlining a real rate-limit payload and a verify-on-update checkpoint would materially improve it.

Suggestions

Replace the empty POST body with a realistic rate-limit payload example (e.g. limits per key/token quotas).

Add a verification step after POST, such as re-running GET /api/rate-limit to confirm the applied config.

Inline 1–2 key request/response fields rather than deferring everything to the OpenAPI spec.

Dimension	Reasoning	Score
Conciseness	Mostly lean with concrete curl commands and no concept padding, but the Overview repeats the description verbatim and could be trimmed; fits the 4 anchor (efficient, minor over-explanation) better than 5.	4 / 5
Actionability	Provides concrete curl commands for GET and POST, but the POST example sends an empty '-d "{}"' body and all request/response schemas are deferred to the external OpenAPI spec, leaving guidance incomplete per the score-3 anchor.	3 / 5
Workflow Clarity	Endpoints are listed but POST /api/rate-limit is a state-changing config update with no validation or verification step (e.g. re-GET to confirm), so workflow clarity is capped at 3 per the destructive/batch guideline.	3 / 5
Progressive Disclosure	Short body with well-organized sections and a clearly signaled one-level reference to the OpenAPI spec for detailed schemas, but the Payloads section is thin and inlines little, keeping it just below the 5 anchor.	4 / 5
	Total	14 / 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 specific, action-oriented description with strong capability coverage, but it lacks any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when…' clause and synonyms like 'budget'/'billing' would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when managing API spend, token quotas, or rate limits per key or across providers.'

Include natural synonyms users say — 'budget', 'billing', 'API costs' — to broaden trigger-term coverage.

Tighten distinctiveness by naming the API-gateway/provider context explicitly to separate it from general finance budgeting skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, comprehensive actions — 'Configure spending limits, token quotas, and rate-limit policies', 'Inspect current consumption', 'enforce cost controls' — covering the domain thoroughly, matching the score-5 anchor rather than the 4 with minor gaps.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when…' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('spending limits', 'token quotas', 'rate-limit', 'cost controls', 'consumption') a user would say, but missing common synonyms like 'budget', 'billing', or 'API costs' that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (per-API-key/provider cost and rate-limit control) with distinct triggers and minimal conflict risk, though it could marginally overlap with general budgeting skills, fitting the 4 anchor better than 5.	4 / 5
	Total	16 / 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-budget/SKILL.md
Commit: ea0cdc5

Reviewed: about 6 hours 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.