CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golden-chat-empty

Use when testing the golden_chat_empty 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_empty/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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, token-efficient overview with genuine one-level reference files, but it describes a chat archive that is entirely empty (0 messages, 0 sections) and provides no actionable retrieval steps. Its utility is limited because the referenced content holds nothing to retrieve.

Suggestions

Add a concrete retrieval example (e.g., a grep command or a note on how to search references/index.md) so Claude knows exactly how to query the chat archive.

Since the archive is empty (0 messages), either note that the skill has no retrievable content yet or remove the empty statistics/navigation blocks to avoid implying available data.

Turn the 'When to Use' bullet list into a small stepwise workflow (locate section in index.md → open the matching section_NN.md → quote or summarize) with a verification check that the section is non-empty before answering.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation — short labeled sections, statistics lists, and a navigation block, with every section brief; it is efficient though slightly padded by redundant zero-stat blocks, landing just below the fully lean anchor.

4 / 5

Actionability

Guidance like 'Find solutions discussed in chat history', 'Reference code snippets', and 'Look up troubleshooting steps' are high-level hints with no executable steps, queries, or commands — matching the 'minimal concrete guidance; high-level hints but missing specific steps' anchor rather than score 1 (which is purely abstract).

2 / 5

Workflow Clarity

The 'When to Use' list gives rough use cases but there is no sequenced process or validation for retrieving/verifying chat content, fitting the 'rough sequence present but many gaps; validation absent' anchor; it does not quite reach score 3 because no real ordered workflow exists at all.

2 / 5

Progressive Disclosure

Structure is good and shallow: a concise overview with clearly signaled one-level-deep references ('references/section_01.md - Chat Content' and 'See references/index.md for complete chat structure'), both verified as real files; it falls short of 5 only because the body itself repeats statistics already in the index and the single section file is essentially empty.

4 / 5

Total

12

/

20

Passed

Description

20%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 essentially a placeholder wrapped around an internal build codename: it gives a 'when' trigger but no concrete 'what' and no natural user-facing keywords. It reads as auto-generated scaffolding rather than a usable skill description.

Suggestions

State the concrete capabilities (e.g., 'Search indexed Slack chat history, retrieve shared code snippets, and look up past troubleshooting steps') before the trigger clause.

Replace the opaque codename trigger with natural user phrases such as 'Slack chat history', 'team decisions', or 'shared code snippets from chat'.

Add an explicit 'Use when the user asks about golden_chat_empty Slack conversations or needs past team discussions' clause to answer both what and when.

DimensionReasoningScore

Specificity

The description ('Use when testing the golden_chat_empty golden build') names no concrete actions or capabilities whatsoever — it only references an opaque internal build identifier, matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

It has an explicit 'Use when...' (the 'when') but no meaningful 'what' — it never states what the skill does, only when to invoke it, matching the 'only when is present without what' anchor rather than score 3 (which requires a clear 'what').

2 / 5

Trigger Term Quality

'testing the golden_chat_empty golden build' offers a single generic 'testing' trigger tied to a build codename rather than natural phrases a user would actually say, placing it just above the no-keywords anchor but well below genuine natural-term coverage.

2 / 5

Distinctiveness Conflict Risk

'Testing the golden_chat_empty golden build' is extremely broad and would overlap with any testing-oriented skill; only the opaque codename gives it any specificity, fitting the 'very broad; high overlap risk' anchor.

2 / 5

Total

7

/

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