CtrlK
BlogDocsLog inGet started
Tessl Logo

api-server-mcp

REST API server and MCP protocol integration

44

Quality

45%

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 ./.ai-rulez/skills/api-server-mcp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 a dense, reasonably concise architecture reference with concrete handler/env details and a usable Claude Desktop config, but its main code example is pseudocode, batch workflows lack validation loops, and all reference material is inlined with no separate files.

Suggestions

Replace the commented pseudocode tool-registration example with real, executable Rust showing the handler signature and a complete ToolResult return.

Add explicit validation/verification steps for batch and async extraction (e.g., validate inputs, check feature gates, retry/abort handling) to raise workflow clarity above the batch cap.

Move the full endpoint reference and env-var catalog into separate files under references/ and link to them one level deep, keeping SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

The body is mostly lean reference material (tables, env vars, rules) that assumes Claude's competence and avoids explaining known concepts, with only minor trimmable redundancy like the ASCII flow diagram and repeated Location lines.

4 / 5

Actionability

It gives concrete handler names, env vars, and a copy-paste Claude Desktop JSON config, but the main Rust tool-registration example is pseudocode in comments and much of the body is descriptive rather than executable, fitting the score-3 anchor.

3 / 5

Workflow Clarity

A server-setup sequence exists but lacks validation checkpoints, and because the skill covers batch operations without a validate/verify loop, workflow clarity is capped at 3 per the feedback-loops guidance.

3 / 5

Progressive Disclosure

No bundle reference files exist and the full endpoint/env-var API reference is inlined in SKILL.md; section headers provide some structure but content that belongs in separate files is not split out, matching the score-2 anchor.

2 / 5

Total

12

/

20

Passed

Description

37%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 is a terse domain label that conveys what the skill covers but provides no concrete actions, no natural trigger terms, and no 'Use when' guidance. It is too sparse to confidently route the right users to it.

Suggestions

Add concrete verbs, e.g. 'Builds REST endpoints and MCP tools for document extraction, wires middleware, caching, and error handling.'

Append a 'Use when...' clause with natural triggers, e.g. 'Use when adding REST endpoints or MCP tools to the Xberg extraction server, or when integrating Claude Desktop with Xberg.'

Include synonyms and concrete nouns users actually say (REST endpoints, MCP tools, Claude Desktop, extraction API) to improve trigger term quality and distinctiveness.

DimensionReasoningScore

Specificity

The description names two domains ('REST API server', 'MCP protocol integration') but lists no concrete actions such as build, expose, or configure, matching the score-2 anchor of naming the domain with minimal actions.

2 / 5

Completeness

It gives a clear 'what' (REST API server and MCP protocol integration) but entirely omits any 'when'/'Use when...' trigger guidance, matching the score-3 anchor and capped there per the missing-trigger guidance.

3 / 5

Trigger Term Quality

Only the technical terms 'REST API server' and 'MCP protocol' appear; there are no natural user phrases, synonyms, or extensions a user would actually say, fitting the score-2 anchor of one or two generic/jargon keywords.

2 / 5

Distinctiveness Conflict Risk

The MCP + REST API server niche is somewhat specific but the terse description lacks distinguishing trigger phrases and could overlap with general API skills, matching the score-3 anchor.

3 / 5

Total

10

/

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.

Validation15 / 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
xberg-io/xberg
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.