CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-assistant

Streaming chat assistant with conversation memory. Use as a general-purpose assistant for multi-turn conversations where streaming output and context retention matter.

53

Quality

60%

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 ./modules/skills/src/main/resources/META-INF/skills/ai-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-organized instruction-only skill with clear sections and no token waste, weakened mainly by high-level bullets that describe behaviors rather than give concrete, actionable guidance.

Suggestions

Make the Skills bullets actionable rather than descriptive (e.g., "Answer factual questions in under 500 words; cite uncertainty when unsure" instead of "Answer general knowledge questions").

Deduplicate the conciseness rule so it appears once, either in the intro or Guardrails, not both.

Add one or two concrete behavioral examples (e.g., a short sample exchange) to ground the guardrails.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; the only minor trim is the near-duplicate conciseness rule in the intro ("Keep responses under 500 words") and Guardrails ("Keep responses concise").

4 / 5

Actionability

A few concrete rules ("under 500 words", "Acknowledge uncertainty rather than guessing") exist, but most bullets ("Answer general knowledge questions", "Help with writing, editing, and brainstorming") are high-level descriptions rather than executable guidance.

3 / 5

Workflow Clarity

As a simple single-purpose behavioral skill it is clear and well-organized with Skills and Guardrails sections; no multi-step validation is needed since it is not destructive or batch-oriented.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, it is well-organized into clearly labeled sections (Skills, Guardrails), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

16

/

20

Passed

Description

50%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 answers both what and when with an explicit trigger clause and stays in third person, but is dragged down by vague, generic capabilities and a broad general-purpose framing that invites conflict with other skills.

Suggestions

Replace "general-purpose assistant" with concrete capabilities (e.g., "answers multi-turn questions, drafts and edits text, explains technical concepts while retaining conversation context").

Add concrete user trigger phrases (e.g., "Use when the user wants a continuous chat, follow-up questions, or long-running context across turns").

Narrow the niche with file-format or platform cues so it does not collide with other conversational skills.

DimensionReasoningScore

Specificity

It names the domain ("Streaming chat assistant with conversation memory") but the actions are generic descriptors rather than concrete capabilities; "general-purpose assistant" adds no specific action.

2 / 5

Completeness

Both what ("Streaming chat assistant with conversation memory") and when ("Use as a general-purpose assistant for multi-turn conversations where...") are present, though the when clause could be more specific about concrete triggers.

4 / 5

Trigger Term Quality

Relevant natural keywords appear ("multi-turn conversations", "streaming output", "context retention") but common synonyms and phrasings a user would naturally say are missing.

3 / 5

Distinctiveness Conflict Risk

The explicit "general-purpose assistant" framing makes it very broad with high overlap risk against many other conversational skills.

2 / 5

Total

11

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Atmosphere/atmosphere
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.