CtrlK
BlogDocsLog inGet started
Tessl Logo

settings-guide-skill

Triggers when the user asks about settings, preferences, API keys, model switching, theme / language / shortcuts / proxy / backup, or related failures (key invalid, model not found) within the OpenLoaf desktop product — where to configure and how to configure them. **Not for**: code configuration files inside a project such as tsconfig / .env (→ use Read/Edit directly), general programming questions (→ answer directly), or system-level OS settings.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent manual-style skill body: dense, product-specific, and fully actionable with exact UI paths, a worked troubleshooting tree, and concrete good/bad answer examples, all at lean token cost and with clean section structure. The only gap is the absence of any validation or feedback checkpoint in the answering workflow, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and entirely product-specific: a lookup table, a compact decision tree, and terse "Why?" one-liners ("the model connection pool is initialized at startup") that capture knowledge Claude cannot know on its own. No section explains concepts Claude already knows, no padding — every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable in its domain: exact UI paths ("Settings → AI Models → Provider Management → click the Provider → Edit API Key"), a concrete example value ("http://127.0.0.1:7890"), a step-by-step troubleshooting tree, and a bad-vs-good answer table showing precisely what to say instead. The scoring note about instruction-only skills applies — this guidance is copy-paste ready.

5 / 5

Workflow Clarity

The "Answering Strategy" gives a clear 4-step sequence (identify need → look up in Configuration Map → give exact path → walk decision tree) with an explicit fallback rule ("If the user's need is not in the table above, point them to the Settings home page and tell them to use its search"), which matches the 4 anchor's clear sequence with most checkpoints. It falls short of 5 because there is no verification/feedback step (e.g., confirming the resolved path against the current product version or handling an outdated path); no workflow-clarity cap applies since the skill performs no destructive or batch operations.

4 / 5

Progressive Disclosure

A single self-contained ~90-line page with well-organized sections (Configuration Map, decision tree, security principles, privacy notes, anti-patterns, answering strategy), clear headers, and no content that warrants a separate reference file — the overview is the entire skill, and navigation is trivial. No nested or buried references exist.

5 / 5

Total

19

/

20

Passed

Description

95%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 description: explicit trigger clause with concrete natural terms (including synonyms and failure phrasings), a clear product-scoped what, and a well-drawn "Not for" boundary that sharply reduces conflict risk. The only weakness is that the capability side is a single compact phrase rather than several distinct concrete actions, which keeps specificity just short of the top anchor.

DimensionReasoningScore

Specificity

The description enumerates concrete, specific scope items — "settings, preferences, API keys, model switching, theme / language / shortcuts / proxy / backup, or related failures (key invalid, model not found)" — but the capability itself is compressed into one phrase, "where to configure and how to configure them", rather than multiple distinct concrete actions as in the 5 anchor. It exceeds the 3 anchor because the enumerated coverage of settings areas and failure modes is comprehensive, leaving only minor gaps.

4 / 5

Completeness

It explicitly answers "when" via "Triggers when the user asks about settings, preferences, API keys, model switching..." — a concrete trigger clause — and "what" via "where to configure and how to configure them within the OpenLoaf desktop product". Both are explicit and concrete, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms with synonyms and failure phrasings users would actually say: "settings", "preferences", "API keys", "model switching", "theme", "language", "shortcuts", "proxy", "backup", plus error-report language like "key invalid" and "model not found". Nothing natural for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

The scope is pinned to a clear niche — "within the OpenLoaf desktop product" — and it adds explicit exclusions ("**Not for**: code configuration files inside a project such as tsconfig / .env..., general programming questions..., or system-level OS settings") that prevent triggering for adjacent but wrong skills. Minimal conflict risk.

5 / 5

Total

19

/

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
itsablabla/openloaf-web
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.