mcporter
Interact with MCP (Model Context Protocol) servers using the mcporter CLI. Use this skill when you need to list available MCP servers, view tool schemas, call MCP tools, manage OAuth authentication, or generate CLI wrappers and TypeScript types for MCP servers.
90
89%
Does it follow best practices?
Impact
88%
1.29xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 well-crafted skill description that clearly identifies the tool (mcporter CLI), the domain (MCP/Model Context Protocol servers), and lists specific capabilities. It includes an explicit 'Use this skill when...' clause with multiple concrete trigger scenarios, making it easy for Claude to select appropriately. The description is concise yet comprehensive, with strong trigger terms and minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: list available MCP servers, view tool schemas, call MCP tools, manage OAuth authentication, generate CLI wrappers, and generate TypeScript types. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (interact with MCP servers using mcporter CLI, with specific capabilities listed) and 'when' (explicit 'Use this skill when you need to...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'MCP', 'Model Context Protocol', 'mcporter', 'MCP servers', 'tool schemas', 'OAuth authentication', 'CLI wrappers', 'TypeScript types'. Good coverage of both the acronym and full name, plus specific feature terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: MCP server interaction via the mcporter CLI tool. The combination of MCP-specific terminology and the named CLI tool makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%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 CLI reference skill that excels at conciseness and actionability, providing concrete, executable commands throughout without unnecessary explanation. Its main weakness is the lack of validation steps or error handling guidance—there's no mention of what to do when commands fail, how to verify successful authentication, or how to troubleshoot daemon issues. The structure is clean but could benefit from light progressive disclosure for advanced topics.
Suggestions
Add brief validation/verification guidance after key operations (e.g., 'After `mcporter auth <server>`, verify with `mcporter list <server>` to confirm access')
Include a brief troubleshooting note or error recovery hint, especially for auth and daemon operations (e.g., what to check if `mcporter call` returns an auth error)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows what MCP servers, CLI tools, OAuth, and TypeScript are without explaining any of these concepts. Every section delivers concrete commands without filler. | 3 / 3 |
Actionability | Every section provides copy-paste ready CLI commands with concrete examples including realistic arguments (e.g., team=ENG, limit:5, title="Bug"). Multiple calling syntaxes are demonstrated with executable examples. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear 3-step sequence for basic usage, but there are no validation checkpoints or error recovery guidance. For operations like auth reset, config changes, or daemon management, there's no feedback loop (e.g., verify auth succeeded, check config after import). | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but everything is inline in a single file. For a skill of this size (~80 lines), some sections like code generation or daemon management could be referenced as separate files, though the current organization is still navigable. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.