mcp-patterns
Model Context Protocol (MCP) server patterns for building integrations with Claude Code. Triggers on: mcp server, model context protocol, tool handler, mcp resource, mcp tool.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill mcp-patterns83
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
72%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 effectively identifies its niche with strong trigger terms specific to MCP development, making it easily distinguishable from other skills. However, it lacks concrete action verbs describing what the skill actually helps accomplish (e.g., creating servers, defining tools, handling requests), leaving the capabilities somewhat abstract.
Suggestions
Add specific concrete actions like 'Create MCP servers, define tool handlers, implement resources and prompts' to improve specificity.
Expand the capability description to clarify what patterns are covered (e.g., 'authentication patterns, error handling, resource definitions').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (MCP server patterns) and general purpose (building integrations with Claude Code), but lacks specific concrete actions like 'create tool handlers', 'define resources', or 'implement prompts'. | 2 / 3 |
Completeness | The 'what' is present but vague ('patterns for building integrations'). The 'when' is addressed via 'Triggers on:' which functions as explicit trigger guidance, but the what-component is too weak for a score of 3. | 2 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'mcp server', 'model context protocol', 'tool handler', 'mcp resource', 'mcp tool'. These cover the key variations a user might mention. | 3 / 3 |
Distinctiveness Conflict Risk | MCP is a specific protocol with distinct terminology. The explicit trigger terms ('mcp server', 'model context protocol', 'tool handler') create a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides actionable, executable code examples with excellent progressive disclosure through reference files. The main weakness is the lack of an explicit step-by-step workflow for setting up a new MCP server from scratch, though the troubleshooting table partially compensates for this.
Suggestions
Add a numbered 'Getting Started' workflow with explicit steps: 1. Create project structure, 2. Install dependencies, 3. Implement server, 4. Configure Claude Desktop, 5. Test connection
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code without explaining what MCP is or how Python async works. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable Python code for a complete MCP server, copy-paste ready configuration examples, and a clear project layout. The code is complete and runnable, not pseudocode. | 3 / 3 |
Workflow Clarity | While the content shows what to build, it lacks explicit sequencing for the setup process (install dependencies, create files, configure, test). The troubleshooting table helps but there's no validation checkpoint workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick reference table pointing to detailed patterns, and clearly signaled one-level-deep references to specific pattern files. Navigation is intuitive and well-organized. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.