CtrlK
BlogDocsLog inGet started
Tessl Logo

add-app-to-server

This skill should be used when the user asks to "add an app to my MCP server", "add UI to my MCP server", "add a view to my MCP tool", "enrich MCP tools with UI", "add interactive UI to existing server", "add MCP Apps to my server", or needs to add interactive UI capabilities to an existing MCP server that already has tools. Provides guidance for analyzing existing tools and adding MCP Apps UI resources.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A thorough, highly actionable skill with executable code, a clear six-step workflow, and well-organized references to a cloned SDK repo. Its only real weakness is mild verbosity and redundancy across examples that could be tightened without losing clarity.

Suggestions

Define shared values like `resourceUri` once and reference them across steps instead of re-declaring the same constant in Step 4, Step 5, and the CSP example.

Collapse the framework-template table's near-identical rows by noting the common `server.ts` + UI entry pattern once and listing only the framework-specific entry file differences.

In the CSP section, show only the `_meta.ui` domain fields rather than re-stating the full `registerAppResource` boilerplate already covered in Step 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no explanations of what an iframe, vite, or MCP is), but at roughly 390 lines it carries avoidable redundancy — `resourceUri` is redefined in Step 5 right after Step 4, the CSP example re-registers the full resource block, and the framework-template table repeats near-identical file sets — so it could be tightened; it is not level 3 because not every token earns its place, and not level 1 because it avoids concept padding.

2 / 3

Actionability

Provides complete, copy-paste-ready TypeScript and bash blocks including a before/after tool conversion, vite config, HTML entry, resource registration, and handler wiring; it is not level 2 because the code is executable rather than pseudocode and key details are present.

3 / 3

Workflow Clarity

Six numbered steps are clearly sequenced with checkpoints (Step 1 says to "Present the analysis to the user and confirm which tools to enhance"), plus a "Common Mistakes to Avoid" checklist and a Testing "Verify" checklist; it is not level 2 because validation/verification steps are explicit rather than implicit.

3 / 3

Progressive Disclosure

The SKILL.md is an overview that points one level deep to clearly signaled external references (tables mapping source files, example servers, and framework templates in the cloned repo), and optional material is split into its own section; it is not level 2 because references are clearly signaled and content is appropriately separated rather than dumped inline.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description with explicit third-person trigger guidance, multiple natural phrasings, and a clearly scoped niche. It cleanly answers both what the skill does and when to use it without vague fluff.

DimensionReasoningScore

Specificity

Names a concrete domain (MCP server/tools) and multiple distinct actions such as "analyzing existing tools and adding MCP Apps UI resources" and "add interactive UI capabilities", matching the level-3 anchor for listing multiple specific concrete actions; it is not level 2 because the actions are concrete rather than merely naming a domain.

3 / 3

Completeness

Explicitly answers both questions: the "when" via "This skill should be used when the user asks to ... or needs to add interactive UI capabilities" and the "what" via "Provides guidance for analyzing existing tools and adding MCP Apps UI resources"; the explicit trigger clause keeps it at 3 rather than the level-2 cap for missing trigger guidance.

3 / 3

Trigger Term Quality

Provides six quoted natural phrasings users would actually say ("add an app to my MCP server", "add UI to my MCP server", "add a view to my MCP tool", "enrich MCP tools with UI", "add interactive UI to existing server", "add MCP Apps to my server"), giving good coverage of natural terms; it is not level 2 because common variations are well represented.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (enriching an existing MCP server that already has tools with MCP Apps UI) with distinctive triggers unlikely to fire for unrelated skills; it is not level 2 because the scope is too specific to overlap broadly with other skills.

3 / 3

Total

12

/

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
modelcontextprotocol/ext-apps
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.