mcp-developer
Use when building MCP servers or clients that connect AI systems with external tools and data sources. Invoke for MCP protocol compliance, TypeScript/Python SDKs, resource providers, tool functions.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill mcp-developer67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and clear when/what guidance for the MCP domain. The main weakness is that it lacks specific concrete actions (verbs describing what the skill actually does), instead relying on domain terminology. Adding action verbs like 'implement', 'configure', 'debug' would strengthen specificity.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Implement MCP servers, configure resource providers, create tool functions, debug protocol compliance issues.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MCP servers/clients, AI systems, external tools) and mentions some technical elements (TypeScript/Python SDKs, resource providers, tool functions), but doesn't list concrete actions like 'create', 'configure', 'debug', or 'implement'. | 2 / 3 |
Completeness | Explicitly answers both what ('building MCP servers or clients that connect AI systems with external tools and data sources') and when ('Use when building MCP servers or clients', 'Invoke for MCP protocol compliance'). Has clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'MCP servers', 'MCP clients', 'MCP protocol', 'TypeScript/Python SDKs', 'resource providers', 'tool functions', 'external tools and data sources'. Good coverage of technical terms developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | MCP (Model Context Protocol) is a specific niche with distinct terminology. The combination of 'MCP protocol', 'resource providers', and 'tool functions' creates a clear, unique trigger profile unlikely to conflict with general coding or API skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization and progressive disclosure through its reference table, but critically lacks actionable content. It reads more like a role description than a skill that teaches Claude how to perform specific tasks. The absence of any code examples, concrete commands, or executable guidance significantly limits its utility.
Suggestions
Add concrete code examples for at least one TypeScript and one Python MCP server implementation showing basic tool/resource setup
Replace abstract constraints like 'Implement JSON-RPC 2.0 protocol correctly' with specific patterns or code snippets showing correct implementation
Add validation checkpoints to the workflow with specific commands (e.g., 'Test with: npx @modelcontextprotocol/inspector')
Remove or condense the 'Role Definition' and 'Knowledge Reference' sections which don't provide actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'Role Definition' that restates what Claude already knows, and 'Knowledge Reference' which is essentially a keyword list that doesn't add actionable value. | 2 / 3 |
Actionability | The skill provides no concrete code examples, commands, or executable guidance. It describes what to do at a high level ('Implement JSON-RPC 2.0 protocol correctly') but never shows how. The workflow is abstract and the constraints are vague directives without implementation details. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence but lacks validation checkpoints, specific commands, or feedback loops. For a protocol implementation skill involving security and compliance, the absence of explicit verification steps is a gap. | 2 / 3 |
Progressive Disclosure | The skill effectively uses a reference table with clear one-level-deep links to detailed guidance files, organized by topic with clear 'Load When' conditions. This is well-structured progressive disclosure. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.