CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-configurator

Add or update workspace MCP servers using holaOS mcp_registry syntax.

66

Quality

78%

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 ./runtime/harnesses/src/embedded-skills/mcp-configurator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is lean, highly actionable, and well-structured with executable YAML examples and an explicit verification checklist. It is a strong, self-contained skill body with no significant weaknesses.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what MCP is or how YAML works, and every block (Core Rules, server shapes, Verification) carries actionable content. It is not 2 because there is no padded explanation or filler to trim.

3 / 3

Actionability

It provides complete, copy-paste-ready YAML for remote, local, and catalog server shapes plus explicit syntax rules ('strict server.tool', '{env:ENV_VAR_NAME}'). It is not 2 because the examples are fully executable rather than pseudocode or partial guidance.

3 / 3

Workflow Clarity

Core Rules give an ordered procedure and the Verification section is an explicit 5-step checklist with validation checkpoints ('Re-open workspace.yaml and confirm the final shape'). It is not 2 because validation steps are explicit and sequenced rather than implicit or missing.

3 / 3

Progressive Disclosure

With no bundle files present, the skill is a single self-contained document organized into clearly labeled sections (Remote/Local/Catalog/App-Managed/Verification) with no nested references. It is not 2 because the organization is clean and there is no monolithic wall or multi-level reference chain.

3 / 3

Total

12

/

12

Passed

Description

57%

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 concrete and third-person with a distinctive niche, but it lacks an explicit 'Use when...' trigger and relies on technical jargon over natural user phrasing. Adding trigger terms and a use-when clause would lift the weakest dimensions.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when adding, removing, or updating MCP servers in a holaOS workspace, or when the user asks to connect an MCP server.'

Include common user-facing phrasings such as 'MCP config' or 'connect an MCP server' alongside 'mcp_registry' to improve trigger term quality.

Reflect the full action set the skill supports (add, remove, update) rather than only 'add or update'.

DimensionReasoningScore

Specificity

The phrase 'Add or update workspace MCP servers' names a clear domain and two concrete actions (add, update), matching the score-2 anchor of naming some but not comprehensive actions. It does not reach 3 because it lists only two actions and omits operations like 'remove' that the skill actually supports.

2 / 3

Completeness

It states what the skill does ('Add or update workspace MCP servers using holaOS mcp_registry syntax') but includes no 'Use when...' clause or equivalent explicit trigger, so completeness is capped at 2 per the guidelines. It is above 1 because the 'what' is clearly stated.

2 / 3

Trigger Term Quality

'workspace MCP servers' is a relevant natural term, but 'holaOS mcp_registry syntax' is technical jargon and common variations a user might say (e.g. 'MCP config', 'connect an MCP server') are missing. It is above 1 because at least one genuinely natural keyword is present.

2 / 3

Distinctiveness Conflict Risk

The combination of 'workspace MCP servers' and 'holaOS mcp_registry syntax' carves out a clear niche unlikely to trigger for unrelated skills. It is not 2 because the holaOS/mcp_registry scoping is distinctive rather than merely 'somewhat specific'.

3 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
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.