CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golden-chat-single

Use when testing the golden_chat_single golden build

Quality

47%

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 ./tests/golden/phase2/chat_single/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 body is a well-structured but content-light auto-generated overview: it correctly offloads detail to one-level-deep reference files, yet is padded with redundant statistics and gives no concrete instructions for actually using the chat history. The file organization is its strongest aspect.

Suggestions

Remove the duplicated statistics (Total Messages, Channels, etc. appear in multiple sections) and the "Generated by Skill Seeker" footer to cut padding.

Add a short concrete procedure, e.g. 'To find a past decision: open references/index.md, locate the relevant section, then follow the link to main.md.'

Replace the generic 'When to Use' bullets with guidance tied to the actual reference structure so the action is unambiguous.

DimensionReasoningScore

Conciseness

The body is padded with redundant boilerplate ("Total Messages: 1" repeated across sections, emoji headers, a "Generated by Skill Seeker" footer) that adds no value Claude cannot derive, fitting 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

It provides only file navigation pointers ("references/main.md - General Discussion") with no concrete commands or procedures, offering minimal high-level guidance rather than executable steps.

2 / 5

Workflow Clarity

As a simple lookup skill the single action is implied via the 'When to Use' and 'Navigation' sections, but the steps are not crisply sequenced and rely on the reader inferring how to consult the references.

3 / 5

Progressive Disclosure

Detailed content is appropriately split into references/index.md and references/main.md, both clearly signaled one level deep in the Navigation section; only minor organization gaps (inlined statistics) keep it from a 5.

4 / 5

Total

11

/

20

Passed

Description

28%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 too thin to drive reliable activation: it states only a vague trigger and omits what the skill actually does. It relies almost entirely on a proper-noun identifier rather than natural trigger terms. Adding a concrete capability statement and natural-sounding triggers would substantially improve it.

Suggestions

Add a concrete 'what' clause, e.g. 'Searches and surfaces messages, code snippets, and decisions from the golden_chat_single Slack chat history.'

Replace the jargon trigger with natural phrasing a user would say, e.g. 'Use when the user asks about golden_chat_single Slack conversations, team decisions, or shared links.'

Include common synonyms or file/channel references (e.g. #general, Slack export) to improve trigger_term_quality and distinctiveness.

DimensionReasoningScore

Specificity

The phrase "testing the golden_chat_single golden build" names the domain but states only one generic action ("testing") with no concrete capabilities, matching the 'names the domain but actions are minimal' anchor.

2 / 5

Completeness

A 'when' clause is present ("Use when testing...") but the 'what' is entirely missing — it never states what the skill does, matching 'only when is present without what'.

2 / 5

Trigger Term Quality

It offers the generic keyword "testing" plus a technical identifier ("golden_chat_single golden build") but lacks the natural phrases a user would actually say, fitting 'one or two generic keywords; missing the natural phrases users say'.

2 / 5

Distinctiveness Conflict Risk

The unique proper noun "golden_chat_single" gives it a recognizable niche, but the surrounding wording ("testing ... golden build") is generic enough to risk overlap, fitting 'somewhat specific but could still overlap'.

3 / 5

Total

9

/

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

yusufkaraaslan/Skill_Seekers

Path

tests/golden/phase2/chat_single/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.