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.

45

Quality

48%

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

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content body is essentially vacuous: a single generic persona line with no concrete instructions, workflow, or structure for actually summarizing chat conversations. It is not verbose, but it fails to provide any actionable guidance.

Suggestions

Replace the generic persona line with concrete instructions on how to summarize a conversation (e.g., what to include, length/format targets, how to handle long histories).

Add a minimal workflow or output format so the single task is unambiguous and actionable.

If summarization has configurable behavior (scope, recency window, tone), document it in organized sections rather than relying on a one-line persona statement.

DimensionReasoningScore

Conciseness

The body is a single brief line, but 'You are a helpful chat moderator assistant' is a generic persona reminder that does not assume Claude's competence and adds no skill-specific value, so not every token earns its place — fitting the level-2 anchor better than the lean-and-purposeful level 3.

2 / 3

Actionability

No concrete guidance, code, or commands are provided; the line describes a role rather than instructing how to summarize, matching the level-1 'vague or abstract; describes rather than instructs' anchor.

1 / 3

Workflow Clarity

There is no sequenced process or unambiguous single action — 'be a helpful chat moderator assistant' does not define what to do, so even the simple-skill allowance for a clear single action does not apply.

1 / 3

Progressive Disclosure

With no bundle files and only one line, there is no monolithic wall of text or nested references, but there are also no organized sections, so it sits at level 2 ('some structure but could be better organized') rather than the well-organized level 3.

2 / 3

Total

6

/

12

Passed

Description

75%

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 well-formed: it states a clear purpose and includes an explicit 'Use when' trigger tied to a specific MCP tool, giving it good completeness and distinctiveness. It is slightly held back by single-action specificity and a somewhat technical trigger framing.

DimensionReasoningScore

Specificity

The description names the domain ('Chat moderator') and one concrete action ('summarizes ongoing conversations'), but does not list multiple specific actions, matching the 'Names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.

2 / 3

Completeness

It answers both 'what' (summarizes ongoing conversations as a chat moderator) and 'when' via an explicit 'Use when invoked through the Atmosphere MCP server's chat-summary tool' clause, satisfying the level-3 anchor for explicit triggers.

3 / 3

Trigger Term Quality

Relevant keywords appear ('chat', 'summarizes', 'conversations', 'chat-summary'), but the trigger is framed around technical invocation ('invoked through the Atmosphere MCP server's chat-summary tool') rather than natural user phrasing, missing common variations like 'summarize the chat'.

2 / 3

Distinctiveness Conflict Risk

The trigger is gated on a specific named tool (the Atmosphere MCP server's chat-summary tool), giving it a clear niche unlikely to fire for unrelated skills, matching the level-3 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

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.