CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mcp

Model Context Protocol server management and tool integration

51

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/mcp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is an efficient, actionable API reference with concrete code and commands, but it is a monolithic catalog with no multi-step workflow validation checkpoints and no progressive disclosure into separate reference files.

Suggestions

Add a short sequenced 'workflow' section with validation checkpoints for risky operations (e.g. connect -> listTools -> callTool -> verify result -> disconnect).

Move the full TypeScript API reference and popular-servers table into separate reference files (e.g. references/api.md, references/servers.md) and link to them from the body to improve progressive disclosure.

Trim the overlap between the Chat Commands, CLI Commands, and TypeScript API sections by cross-referencing instead of repeating list/add/remove coverage.

DimensionReasoningScore

Conciseness

The body is dense reference tables and code blocks with minimal prose and no over-explanation of MCP or library concepts, though some overlap between the chat-command, CLI, and TypeScript sections keeps it just below fully lean.

4 / 5

Actionability

It provides concrete, executable code (createMCPClient, listTools, callTool) and real CLI commands with actual package names and arguments, covering common cases copy-paste ready with only minor gaps like error handling.

4 / 5

Workflow Clarity

This is a reference catalog rather than a sequenced workflow, and server add/remove/restart and tool-call operations lack any validation or verification checkpoints; per the batch/destructive-operations guidance this caps workflow clarity at 3.

3 / 5

Progressive Disclosure

All content is inlined into a single ~130-line file with good headers but no bundle files, and the large API reference, server table, and config JSON are material that would be better split into separate reference files.

3 / 5

Total

14

/

20

Passed

Description

48%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 names a clear, distinct domain but relies on generic action verbs and omits any explicit 'Use when…' trigger guidance, capping completeness at 3. Adding concrete capabilities and a trigger clause would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Add, remove, and restart MCP servers; call server tools and list resources from chat or the TypeScript API.'

Append an explicit trigger clause such as 'Use when managing MCP servers, integrating external tools, or when the user mentions Model Context Protocol / MCP.'

Include natural synonyms users say (e.g. 'MCP server', 'connect a tool', 'MCP integration') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'server management and tool integration' names the MCP domain but the actions are generic ('management', 'integration') with no concrete verbs like add/remove servers or call tools, matching the 'names the domain but actions are minimal' anchor.

2 / 5

Completeness

It gives a clear 'what' (server management and tool integration) but has no 'Use when…' trigger clause, so per the missing-trigger guidance completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes relevant domain keywords ('Model Context Protocol', 'MCP', 'servers', 'tools') but lacks common natural phrasings a user would actually say, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

MCP server management is a fairly distinct niche with low conflict risk, though the generic 'tool integration' wording leaves minor overlap with general tooling skills, placing it just below the fully-distinct anchor 5.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/mcp/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill