CtrlK
BlogDocsLog inGet started
Tessl Logo

deepchat-settings

DeepChat app settings modification (DeepChat 设置/偏好) skill. Activate ONLY when the user explicitly asks to change DeepChat's own settings/preferences (e.g., theme, language, font size...). Do NOT activate for OS/system settings, editor settings, or other apps.

63

Quality

75%

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

Quality

Content

71%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-organized instruction-only skill with clear tool-to-setting mappings and a sensible fallback for unsupported settings. Its main weakness is a missing explicit verification checkpoint in the workflow before reporting a change as applied.

Suggestions

Add an explicit verification checkpoint in the workflow (e.g., 'Confirm the tool returned success and the setting reflects the intended value before reporting back') to strengthen the mutation workflow.

Show one concrete worked invocation with arguments (e.g., deepchat_settings_set_theme with theme=dark) so the actionability is fully copy-paste ready.

Tighten the duplicated skill-activation explanation that appears in both Core rules and Workflow step 2 to remove a small amount of redundancy.

DimensionReasoningScore

Conciseness

The body is efficient and avoids explaining concepts Claude already knows; nearly every line is operational (rules, allowlist, workflow, examples). A small amount could be tightened (e.g., the repeated skill-activation explanation in Core rules vs. Workflow), but it stays lean.

4 / 5

Actionability

It maps each supported setting to a specific tool call (toggle/set_language/set_theme/set_font_size/open) and lists concrete enum values and section hints, so guidance is mostly executable. The gap is the lack of an explicit worked example showing the tool invocation with arguments, leaving a minor detail gap.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced and includes a conditional fallback branch for unsupported settings, but it lacks an explicit validation/confirmation checkpoint verifying the change actually applied before reporting success. The confirmation step ('Confirm back to the user what changed') states the report rather than a verify-before-confirm loop, which is a validation gap for a settings-mutation skill.

3 / 5

Progressive Disclosure

This is a short single-purpose skill (under 50 lines) with no bundle files and no need for external references; it is organized into well-signaled sections (Core rules, Supported settings, Workflow, Examples activate / do NOT activate), which per the simple-skills guidance warrants a 5.

5 / 5

Total

16

/

20

Passed

Description

80%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, well-scoped description with explicit activate/anti-activate guidance that answers both what and when. It is held back from perfection only by moderate action specificity and slightly incomplete keyword synonyms in the description text itself.

Suggestions

Add 1-2 more concrete actions inline in the description (e.g., 'toggles, theme, language, font size') to lift specificity beyond naming the domain.

Include a natural synonym a user might say (e.g., 'preferences' as well as 'settings') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (DeepChat settings modification) and a few concrete actions via the tool list (set theme/language/font size, toggle), but the description text itself states only high-level categories ('theme, language, font size...') rather than enumerating concrete actions, so coverage is moderate rather than comprehensive.

3 / 5

Completeness

It explicitly answers 'what' (DeepChat app settings modification) and 'when' with concrete trigger guidance ('Activate ONLY when the user explicitly asks to change DeepChat's own settings/preferences'), including a counter-condition ('Do NOT activate for OS/system settings'), satisfying both halves with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('theme, language, font size') plus concrete activate/do-not-activate framing; it misses common synonyms and file extensions, but the listed keywords are ones a user would plausibly say, giving good (not full) coverage.

4 / 5

Distinctiveness Conflict Risk

The skill is scoped to a clear niche (DeepChat's own application settings) and explicitly disambiguates against OS, editor, and other-app settings, giving distinct triggers and minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ThinkInAIXYZ/deepchat
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.