CtrlK
BlogDocsLog inGet started
Tessl Logo

product-help

Use this skill when the user asks about my own features, configuration, or usage — installation, skills, Web UI, CLI, API config, memory, sessions, encryption, white-label, publishing, pricing, troubleshooting, or restarting the server. Do NOT trigger for general coding tasks unrelated to me.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable instruction-only skill with a clear workflow and feedback loop for failed fetches. The only weakness is mild redundancy between the self-understanding narrative and the URL table.

DimensionReasoningScore

Conciseness

Mostly efficient and lean, but the "My self-understanding" narrative and the capabilities bullet list partially duplicate topics already covered by the Doc URL Table, so it could be tightened — matching the anchor-2 "mostly efficient but includes some unnecessary explanation."

2 / 3

Actionability

Concrete executable guidance throughout: a 23-row URL table, an explicit fetch call ("web_fetch(url: \"<URL>\", max_length: 5000)"), intent-matching examples ("帮我打开webui → web-server"), and a copy-paste restart command ("kill -USR1 $CLACKY_MASTER_PID") — fully actionable, anchor-3.

3 / 3

Workflow Clarity

Clear three-step sequence (pick URL → fetch → answer) with an explicit fallback loop ("try the next most relevant URL (max 2 fetches)") and a separately branched restart section; no destructive/batch operations exist, so the validation cap does not apply — anchor-3.

3 / 3

Progressive Disclosure

Well-organized into clear sections with content appropriately deferred to one-level-deep external references (the Doc URL Table points to remote docs rather than inlining them), avoiding a monolithic wall of text — anchor-3.

3 / 3

Total

11

/

12

Passed

Description

90%

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, comprehensive trigger description with explicit what/when guidance and a clear negative trigger to avoid misfires. The only knock is the first-person voice ("my own features"), which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

Lists many concrete capability areas ("installation, skills, Web UI, CLI, API config, memory, sessions, encryption, white-label, publishing, pricing, troubleshooting, or restarting the server") which is anchor-3 coverage, but the first-person phrasing "my own features" is penalized one level per the rubric's voice guideline, capping specificity at 2.

2 / 3

Completeness

Explicitly answers both what ("features, configuration, or usage") and when ("Use this skill when the user asks about…"), plus an explicit negative trigger ("Do NOT trigger for general coding tasks unrelated to me").

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say (installation, skills, Web UI, CLI, API config, memory, sessions, pricing, troubleshooting, restarting the server), matching the anchor-3 example of broad natural-term coverage.

3 / 3

Distinctiveness Conflict Risk

Clear niche — questions about the product's own features — reinforced by an explicit exclusion of general coding tasks, making false triggers unlikely; matches the anchor-3 distinct-niche example.

3 / 3

Total

11

/

12

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
clacky-ai/openclacky
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.