mcporter
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
80
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/skillEvaluation — 85%
↑ 1.73xAgent success when using this skill
Validation for skill structure
Discovery
67%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 communicates specific capabilities of the mcporter CLI tool with good technical detail and clear distinctiveness. However, it lacks an explicit 'Use when...' clause and relies on technical jargon that users may not naturally use when requesting help, which could reduce discoverability.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to connect to MCP servers, manage tool configurations, or interact with external tools via the Model Context Protocol.'
Include more natural trigger terms users might say, such as 'connect to tools', 'server configuration', 'tool authentication', or 'external integrations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'list, configure, auth, and call MCP servers/tools', 'ad-hoc servers, config edits, and CLI/type generation'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (list, configure, auth, call MCP servers/tools, config edits, CLI/type generation) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'mcporter', 'MCP servers', 'stdio', 'HTTP', but these are fairly technical. Missing more natural user phrases like 'connect to tools' or 'manage server connections'. Users may not naturally say 'mcporter' unless they already know the tool. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche around 'mcporter CLI' and 'MCP servers/tools'. The combination of the specific tool name and MCP protocol focus makes it highly 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 CLI reference skill that excels at conciseness and actionability - it's essentially a cheat sheet with real, executable examples. The main weakness is the lack of workflow guidance for multi-step operations (e.g., auth -> call sequences) and no mention of error handling or validation.
Suggestions
Add a brief workflow example showing auth -> call sequence for a new server setup
Include guidance on verifying successful calls (e.g., checking output, using --output json for parsing)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - pure command reference with no unnecessary explanation. Every line is actionable, assumes Claude knows what MCP servers are and how CLIs work. | 3 / 3 |
Actionability | Fully concrete with copy-paste ready commands covering all major use cases. Multiple syntax variations shown (selector, function, URL, stdio, JSON) with real examples. | 3 / 3 |
Workflow Clarity | Commands are listed but no workflow sequencing for multi-step operations. For example, no guidance on when to auth before calling, or how to verify a call succeeded. Missing validation checkpoints for operations that could fail. | 2 / 3 |
Progressive Disclosure | For a CLI reference skill of this size (~30 lines), the flat structure with clear section headers is appropriate. No need for external files; content is well-organized by function (list, call, auth, daemon, codegen). | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 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.