CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golden-chat

Use when testing the golden_chat golden build

Quality

36%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/golden/phase2/chat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

7%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 verbose auto-generated data dump with no actionable instructions, workflow, or executable guidance; it pads the context with trivial code and placeholder links. Its only redeeming quality is a correctly signaled set of one-level reference files.

Suggestions

Replace the inlined snippet dump and 21 placeholder links with a concise overview that points to references/index.md for detail, keeping SKILL.md lean.

Add concrete usage guidance or a short workflow describing how to query the chat history (e.g. open index.md, locate the channel section, read the corresponding reference file).

Remove the trivial variable-assignment code sample and redundant statistics sections that restate information already in the index reference.

DimensionReasoningScore

Conciseness

The body is severely padded: a 38-line trivial variable-assignment snippet, 21 placeholder example.com links, and duplicated statistics sections, all of which assume no intelligence and waste tokens.

1 / 5

Actionability

There is no executable guidance, command, or instruction—only a static inventory of snippets, links, and statistics that describes data rather than instructing action.

1 / 5

Workflow Clarity

No sequenced process or validation is present; the body is a generated reference dump with no steps or checkpoints for using the chat history.

1 / 5

Progressive Disclosure

Real one-level-deep reference files (index.md, engineering_s1-s2.md, random_s3-s3.md) are signaled in a Navigation section, but much content that belongs in those references (the long snippet and full link list) is inlined in SKILL.md.

3 / 5

Total

6

/

20

Passed

Description

32%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 a bare trigger clause naming a project-specific build with no capability statement and no natural-language keywords. It is narrowly scoped but tells neither the user nor Claude what the skill actually does.

Suggestions

Add a concrete 'what' clause before the trigger, e.g. 'Searches and summarizes the golden_chat Slack history. Use when testing the golden_chat golden build.'

Include natural user-facing trigger terms (e.g. 'Slack chat history', 'team conversations', 'golden_chat messages') rather than only the internal 'golden build' jargon.

List 1-2 specific capabilities such as finding code snippets or troubleshooting steps so the description conveys actionable value.

DimensionReasoningScore

Specificity

The phrase 'testing the golden_chat golden build' names a domain but lists no concrete actions or capabilities, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

It provides a 'when' ('Use when testing...') but entirely lacks a 'what does this do' statement, matching the anchor 'only when is present without what'.

2 / 5

Trigger Term Quality

Only project-specific jargon ('golden_chat golden build') appears with no natural user-facing keywords or synonyms, falling below the 'Some relevant keywords' anchor at 3.

2 / 5

Distinctiveness Conflict Risk

The narrow project-specific identifier 'golden_chat golden build' creates a distinct niche with minimal overlap risk against other skills, though the vagueness keeps it just below a 5.

4 / 5

Total

10

/

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