CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-analyze-topic

Expert analyst persona used by the MCP analyze-topic tool to produce structured topic analyses. Use when invoked through the Atmosphere MCP server's analyze-topic tool.

50

Quality

56%

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-analyze-topic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

37%

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

The body is token-efficient to a fault but carries no actionable guidance, no workflow, and no structure — it functions as a persona assignment rather than a usable skill body.

Suggestions

Add concrete guidance for what an expert analyst should produce and how (e.g. the structure of a topic analysis, the steps to build one).

Include a minimal workflow or sequencing of the analysis task so the single action is unambiguous.

Add at least a section header or two to give the body minimal organization, even if no external references are needed.

DimensionReasoningScore

Conciseness

The single line 'You are an expert analyst.' is maximally lean with no padding, assuming Claude's competence; every token earns its place even if the result is sparse.

3 / 3

Actionability

The body provides no concrete code, commands, or specific guidance — it only states a persona ('You are an expert analyst.') rather than instructing any action.

1 / 3

Workflow Clarity

There are no steps, no sequence, and no validation checkpoints at all; the body offers no workflow to follow.

1 / 3

Progressive Disclosure

The skill needs no external references and is minimal, but the body has no organized sections or structure to navigate, so it sits between the disorganized anchor and a well-organized overview.

2 / 3

Total

7

/

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-scoped to a specific MCP tool and answers both what and when explicitly, but it relies on system/tool identifiers as triggers and describes only one vague action rather than a concrete action set.

Suggestions

List the concrete actions the analyst performs (e.g. 'break down, compare, and summarize topics') rather than the single vague phrase 'produce structured topic analyses'.

Add natural user-facing keywords alongside the tool identifiers so users who reference 'topic analysis' or 'break down this topic' trigger the skill.

Keep the explicit 'Use when...' clause but pair it with at least one everyday phrasing of the trigger.

DimensionReasoningScore

Specificity

It names a domain ('structured topic analyses') and a single action ('produce') but does not list multiple specific concrete actions, so it lands above the vague anchor and below the multi-action anchor.

2 / 3

Completeness

It explicitly states what it does ('produce structured topic analyses') and when to use it ('Use when invoked through the Atmosphere MCP server's analyze-topic tool'), answering both what and when with an explicit trigger.

3 / 3

Trigger Term Quality

It references relevant terms ('analyze-topic', 'topic analyses', 'Atmosphere MCP server') but these are system/tool identifiers rather than natural phrasings a user would say, and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

It is tied to a specific named MCP tool, giving it a clear niche unlikely to collide with other skills' triggers.

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.