CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-chat-summary

Chat moderator that summarizes ongoing conversations. Use when invoked through the Atmosphere MCP server's chat-summary tool.

40

Quality

40%

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/mcp-chat-summary/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%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 essentially empty of operational content — a single generic persona line with no concrete guidance, workflow, or structure. It is maximally concise but vacuous rather than useful, failing on actionability and workflow clarity.

Suggestions

Replace the generic persona line with concrete instructions: what a chat summary should contain (key decisions, action items, open questions) and the expected output format.

Add a short workflow for producing a summary (read conversation -> identify decisions/action items/open questions -> emit structured recap), with a validation step to confirm completeness before returning.

Organize the body into at least minimal sections (e.g. '## What to include', '## Output format') so the single-purpose skill is well-structured.

DimensionReasoningScore

Conciseness

The single line 'You are a helpful chat moderator assistant.' is not verbose, but it is a generic persona statement that does not add information Claude lacks, so it is mostly efficient yet not clearly earning every token.

3 / 5

Actionability

The body provides no concrete code, commands, or specific guidance — it only assigns a vague persona ('helpful chat moderator assistant'), matching the anchor for entirely abstract content that describes rather than instructs.

1 / 5

Workflow Clarity

There is no sequence of steps, no process, and no validation checkpoints — the body is a single undirected sentence, matching the anchor for missing or incoherent steps.

1 / 5

Progressive Disclosure

No bundle files exist and the body has no section headers or organized structure at all; it is minimal and unstructured, so it does not meet the simple-skill exception of well-organized sections needed to score higher.

2 / 5

Total

7

/

20

Passed

Description

62%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 cleanly states both capability and an explicit trigger clause, but the trigger is anchored to a tool-invocation mechanism rather than natural user language, and the capability list is thin. It is competent but leaves keyword coverage and specificity underdeveloped.

Suggestions

Add concrete natural-language trigger phrases users would actually say, e.g. 'Use when the user asks to summarize, recap, or catch up on an ongoing chat conversation'.

Expand the 'what' with 1-2 more concrete actions (e.g. 'extracts key decisions, action items, and open questions') to lift specificity toward comprehensive coverage.

Include common synonyms/file-style terms (e.g. 'chat recap', 'conversation summary') to improve trigger-term breadth.

DimensionReasoningScore

Specificity

The description names the domain ('chat moderator') and one concrete action ('summarizes ongoing conversations') but offers no further concrete capabilities, matching the anchor that lists domain plus 1-2 actions without comprehensive coverage.

3 / 5

Completeness

Both 'what' (chat moderator that summarizes ongoing conversations) and 'when' (Use when invoked through the Atmosphere MCP server's chat-summary tool) are present and explicit, but the 'when' is narrowly tied to a single technical mechanism and could be more broadly specified.

4 / 5

Trigger Term Quality

It includes relevant keywords ('chat', 'summary', 'moderation', 'conversations') but the trigger ('invoked through the Atmosphere MCP server's chat-summary tool') is a mechanical invocation path rather than natural user phrasing, so common variations/synonyms a user would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The niche (chat moderation/summarization via a specific named MCP tool) is mostly distinct with a narrow trigger that limits conflict, though minor overlap remains with other general summary or chat skills.

4 / 5

Total

14

/

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.