Names the domain (MCP server building) and mentions some areas (tool design, resource patterns, best practices), but these are high-level categories rather than concrete actions like 'create handlers' or 'implement tool schemas'.

Describes what at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak.

Includes 'MCP' and 'Model Context Protocol' which are relevant technical terms, but misses natural user phrases like 'build an MCP server', 'create tools', 'server implementation', or 'protocol integration'.

'MCP' and 'Model Context Protocol' provide some distinctiveness, but 'tool design' and 'best practices' are generic enough to potentially overlap with other development or architecture skills.

The content is reasonably efficient with good use of tables, but includes some explanatory content Claude already knows (e.g., 'What is MCP?' section, basic definitions). Could be tighter by removing conceptual explanations.

Almost entirely descriptive with no executable code examples. Tables describe concepts but don't show how to implement them. Missing concrete code for server setup, tool registration, or resource handling.

No clear workflow for building an MCP server. Content is organized as reference tables but lacks step-by-step guidance, validation checkpoints, or sequenced instructions for creating a working server.

Content is well-organized with clear sections and tables, but everything is inline in one file. No references to external files for detailed implementation guides, API references, or examples that would benefit from separation.