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.

48

Quality

51%

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

41%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 maximally concise but substantively empty: it sets a persona without giving any concrete, actionable, or sequenced guidance for producing a structured topic analysis. The skill leans entirely on the description and Claude's prior knowledge, leaving the body to do little instructional work.

Suggestions

Add a short, concrete outline of the expected analysis structure (e.g., sections for overview, key themes, evidence, and open questions) so the body gives actionable guidance rather than only a persona.

Include an explicit single-step workflow or a brief worked example of the output format so the action and result are unambiguous.

If analysis conventions exist, reference them with a one-level-deep pointer (e.g., a reference file) so the overview stays lean while remaining navigable.

DimensionReasoningScore

Conciseness

The single line "You are an expert analyst." contains zero padding or over-explanation and fully assumes Claude's competence, matching the 'lean and efficient; every token earns its place' anchor on the verbosity axis.

5 / 5

Actionability

The body provides no concrete code, commands, or specific guidance on how to produce a structured analysis; it only declares a persona, matching the 'entirely vague or abstract; only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

No steps or sequence are present in the body, and the simple-skill exception does not apply because the single action is not stated unambiguously here, fitting the 'steps missing or incoherent; no sequence' anchor.

1 / 5

Progressive Disclosure

With no bundle files and nothing inlined that belongs elsewhere, there are no progressive-disclosure violations, but the body also lacks any organized sections or signaled references that would mark the score-5 'clear overview with well-signaled references' anchor.

4 / 5

Total

11

/

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 clearly answers both what the skill does and when to use it, anchored to a specific MCP tool that gives it strong distinctiveness. Its main weakness is thin trigger-term coverage and limited action specificity, relying on a single technical invocation phrase rather than natural keywords.

Suggestions

Add 1-2 more concrete actions (e.g., 'synthesize sources, outline key themes, and surface open questions') to lift specificity from a single action to comprehensive coverage.

Include natural-language trigger variations a user might say (e.g., 'analyze this topic', 'give me a topic breakdown') alongside the tool-invocation trigger to improve trigger term quality.

Add a brief hint of the output structure (e.g., 'returns a structured analysis with themes and gaps') so the 'what' is more concrete and less generic to the broad analysis domain.

DimensionReasoningScore

Specificity

"produce structured topic analyses" names the domain and one concrete action, but offers no further actions or detail, matching the anchor for a single concrete action rather than the several listed at score 4.

3 / 5

Completeness

It states both what ("produce structured topic analyses") and when ("Use when invoked through the Atmosphere MCP server's analyze-topic tool") explicitly, but the single trigger phrase lacks the multiple concrete variations seen at score 5.

4 / 5

Trigger Term Quality

Relevant terms like "analyze-topic", "topic analyses", and "MCP" appear, but they are technical jargon tied to a tool name with no natural synonyms or variations a user would say, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Binding the skill to a specific named MCP tool gives it a clear, mostly-distinct niche with minimal conflict risk, though the conceptual domain of "analysis" could overlap with related analysis skills, keeping it just below score 5.

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.