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

68%

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.

A well-structured, auto-generated API index skill with a genuinely useful curated exception for thinking-budget behavior and a reliable one-level-deep reference file. Its main weaknesses are token duplication (Overview vs. frontmatter, endpoint list vs. the reference's own ToC) and the absence of any warnings or verification guidance for its destructive purge and batch-delete operations.

Suggestions

Group the endpoint list by sub-domain (proxies, database, compression, cache, integrations) or replace it with category-level links to endpoints.md sections, eliminating the duplication of the reference file's own table of contents.

Add a short warning-and-verify note covering the destructive and irreversible endpoints (purge-*, batch-delete, DELETE routes) before Claude invokes them.

Drop or merge the Overview section that duplicates the frontmatter description verbatim, freeing context for the curated guidance that actually adds value.

DimensionReasoningScore

Conciseness

The body avoids concept over-explanation and the thinking-budget section is dense, but the 140-line endpoint list duplicates the reference file's own table of contents line-for-line, the Overview repeats the frontmatter description verbatim, and every link repeats its path as the anchor text — it could be tightened considerably.

3 / 5

Actionability

Concrete and mostly executable: exact auth route ('POST /api/auth/login', 'REQUIRE_API_KEY=false'), a copy-paste-ready curl for the thinking-budget PUT with headers and JSON body, and delegation to references/endpoints.md which carries per-endpoint curl examples. Minor gap: no inline request/response examples for the other ~140 endpoints.

4 / 5

Workflow Clarity

The read/update action itself is unambiguous (authenticate, pick endpoint, curl), but the skill exposes destructive and batch operations ('purge-request-history', 'purge-logs', 'proxies/batch-delete', multiple DELETE endpoints) with no validation, verification, or warning steps, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Bundle structure is sound: one flat reference file one level deep with no nested references, all 140 anchor links resolve, and bulk detail is correctly pushed to endpoints.md and the OpenAPI spec. Minor gaps: the SKILL.md endpoint index is not grouped by sub-domain and duplicates the reference's table of contents.

4 / 5

Total

14

/

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 has a clear, third-person 'what' with a concrete enumerated scope, but it lacks any 'use when' trigger guidance and only covers part of the settings domain it actually serves. Trigger terms are domain-accurate but thin on synonyms and adjacent vocabulary.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to view or change app configuration, proxy settings, quotas, or any /api/settings endpoint'.

Include natural synonyms and adjacent terms users would say (proxy configuration, quotas, cache settings, model aliases) so the description matches the skill's actual endpoint coverage.

Mention destructive operations (purge history/logs, batch delete) in the description so their availability is discoverable at trigger time.

DimensionReasoningScore

Specificity

Names the domain ('global application settings') and enumerates six concrete capability areas ('system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login'), matching the 'lists several specific actions; minor gaps' anchor — not 5 because coverage is partial against the full settings surface (proxies, database, cache, model aliases are absent).

4 / 5

Completeness

The 'what' is clear ('Read and update global application settings: ...') but there is no 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'system prompts', 'thinking budget', and 'IP filters' are natural phrases users would say in this domain, but common variations and adjacent vocabulary (proxy, quota, cache settings) are missing, matching the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

Niche triggers like 'thinking budget', 'combo defaults', and 'require-login' make it mostly distinct from generic settings skills with only minor overlap risk against closely related API-surface 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.