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.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./lib/clacky/default_skills/product-help/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is well-structured, actionable, and efficient, with a clean URL-driven workflow and explicit fallback handling. Scores are held at 4 rather than 5 by minor padding, the absence of explicit validate/retry feedback loops, and a restart section that could be further isolated.

DimensionReasoningScore

Conciseness

The body is largely efficient — a compact URL table, terse 3-step workflow, and short rules — with only minor padding such as the 'My self-understanding' preamble restating capabilities; it sits noticeably above the 'mostly efficient but includes some unnecessary explanation' anchor but is not perfectly lean.

4 / 5

Actionability

It provides concrete executable guidance — the web_fetch call form, an exact restart command (kill -USR1 $CLACKY_MASTER_PID), intent-to-URL mapping examples, and numbered output formatting rules — with only minor gaps (no explicit parameter for matching), fitting the 'mostly executable guidance' anchor.

4 / 5

Workflow Clarity

The fetch workflow is clearly sequenced with an explicit fallback checkpoint ('try the next most relevant URL, max 2 fetches') and a terminal escalation message, and the restart path is branched cleanly; it has clear sequence with most checkpoints present, just short of explicit validate-then-retry feedback loops.

4 / 5

Progressive Disclosure

A single self-contained SKILL.md with no nested references and well-organized sections (Doc URL Table, Workflow, Rules, Restart) — the lookup table is appropriate inline content rather than content that belongs in a separate file; minor organization gaps (the restart section is large enough to feel like its own concern) keep it just below a 5.

4 / 5

Total

16

/

20

Passed

Description

85%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 trigger-rich and boundary-aware, with strong completeness and low conflict risk from its explicit anti-trigger clause. Its main weakness is specificity: it lists coverage domains rather than concrete actions the skill performs.

DimensionReasoningScore

Specificity

The description enumerates topic domains ("installation, skills, Web UI, CLI, API config, memory, sessions...") rather than concrete actions; it states the scope the skill covers but not what it does, matching the 'names the domain but actions are minimal or generic' anchor rather than listing specific operations.

2 / 5

Completeness

It explicitly answers both what (its own features/configuration/usage across the listed domains) and when ('Use this skill when the user asks about...') plus an explicit anti-trigger ('Do NOT trigger for general coding tasks unrelated to me'), satisfying the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Comprehensive natural keyword coverage with synonyms and concrete product terms users would actually say — 'installation', 'Web UI', 'API config', 'memory', 'encryption', 'white-label', 'pricing', 'troubleshooting', 'restarting the server' — matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

A clearly defined niche (product self-help) combined with an explicit negative boundary ('Do NOT trigger for general coding tasks unrelated to me') gives minimal conflict risk with other skills, matching the 'clear niche with distinct triggers' anchor.

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