CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omni-settings

Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

Quality

69%

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/omni-settings/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body follows a sound progressive-disclosure design — a link index plus one deep reference file, one fully worked curl example, and a dense curated section on thinking-budget behavior. Its weaknesses are the undifferentiated 140-line endpoint list that duplicates the reference file's own ToC and the absence of any validation/confirmation guidance for the numerous destructive purge and batch operations it exposes.

Suggestions

Group the endpoint index under domain subheadings (e.g., Memory, Qdrant, Proxy management, Database, Purge operations) and drop the per-line links that duplicate references/endpoints.md's table of contents, cutting tokens while improving navigation.

Add explicit validation guidance for destructive and batch operations, e.g. "Before any purge-* or batch-delete call, confirm the scope with the user and verify the target list via the corresponding GET endpoint first."

Provide a second worked request/response example beyond thinking-budget (e.g., PATCH /api/settings or the proxy pool endpoints) so the common mutation pattern is concrete, not just the one curated case.

DimensionReasoningScore

Conciseness

There is no padded prose or re-explanation of known concepts, but the ~140-line flat endpoint list ("[GET /api/settings/memory](references/endpoints.md#get-apisettingsmemory)" and 139 similar lines) duplicates the table of contents already present in references/endpoints.md and could be grouped or deduplicated to save significant tokens.

3 / 5

Actionability

Concrete, executable guidance is present — a copy-paste curl example for PUT /api/settings/thinking-budget, the auth flow ("Obtain a token via POST /api/auth/login"), and an explicit schema pointer ("full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml"); however, only one endpoint has a worked example and payload details for the rest are entirely deferred, keeping it below anchor 5.

4 / 5

Workflow Clarity

No sequenced multi-step workflow is provided, and the many destructive/batch endpoints ("POST /api/settings/purge-request-history", "POST /api/settings/proxies/batch-delete", "POST /api/settings/purge-quota-snapshots") come with no validation or confirmation guidance, which caps workflow clarity at 3 per the rubric's destructive-operations rule.

3 / 5

Progressive Disclosure

The bundle is well split one level deep — SKILL.md is an index linking every endpoint to a verified anchor in references/endpoints.md, with bulk schemas delegated to the OpenAPI spec; minor gaps keep it below 5: the endpoint list is flat and ungrouped rather than organized by domain, and pointers to out-of-bundle paths ("docs/openapi.yaml", "docs/guides/THINKING_BUDGET.md") are not resolvable within the skill bundle.

4 / 5

Total

14

/

20

Passed

Description

61%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 is concise, third-person, and names concrete settings, but it lacks any 'when to use' trigger clause and understates the skill's actual scope relative to the ~140 endpoints documented in the body. It reads as a clear but incomplete capability summary.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to view or change application settings, system prompts, thinking budget, IP filters, or login requirements."

Broaden the enumerated domains to reflect the full scope (e.g., proxy pools, database maintenance, cache config, model aliases, transfer/export) or state that all settings endpoints are covered.

Include natural synonyms users might say, such as "reasoning budget", "API settings", or "admin configuration", to improve trigger coverage.

DimensionReasoningScore

Specificity

"Read and update" are concrete verbs and six settings are named ("system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration"), but the skill body covers far more domains (proxies, database, cache, transfer, model aliases), so coverage gaps exceed the 'minor' level of anchor 4.

3 / 5

Completeness

The "what" is clear (read/update global application settings with enumerated categories), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Terms like "system prompts", "thinking budget", "IP filters", and "require-login" are natural phrases users would say when managing these settings, matching anchor 4's quality bar; it is above anchor 3 because the keywords are specific rather than generic, but below 5 because synonyms and several whole domains (e.g., proxy management) are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to "global application settings" with niche triggers like "thinking budget" and "require-login" gives a mostly distinct profile with only minor overlap risk against other admin/config skills; it is not a 5 because "settings" itself is broad and the description omits domains that could collide with other skills.

4 / 5

Total

14

/

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