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.
77
73%
Does it follow best practices?
Impact
85%
1.73xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/mcporter/SKILL.mdQuality
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 does a good job listing specific capabilities of the mcporter CLI tool and is highly distinctive. However, it lacks an explicit 'Use when...' clause which would help Claude know when to select this skill, and could benefit from more natural trigger terms that users might actually say when needing MCP-related help.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about mcporter, MCP server configuration, connecting to MCP tools, or managing model context protocol servers.'
Include natural language variations users might say, such as 'model context protocol', 'connect to tools', 'server setup', or 'tool discovery'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: list, configure, auth, call MCP servers/tools, ad-hoc servers, config edits, and CLI/type generation. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with the list of capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the actions listed. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'MCP servers', 'CLI', 'stdio', 'HTTP', 'auth', 'config', but 'mcporter' is a specific tool name that users would need to know. Missing common variations a user might say like 'model context protocol', 'tool calling', or 'server management'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'mcporter' and the focused domain of MCP server management via CLI. Unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 10 / 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, concise CLI reference skill that provides highly actionable, copy-paste-ready commands. Its main strength is token efficiency and breadth of coverage. Its weakness is the lack of workflow sequencing (e.g., setup → auth → call flow) and absence of any validation or error-handling guidance.
Suggestions
Add a brief workflow sequence showing the typical setup flow (e.g., config → auth → call) so Claude knows the expected order of operations.
Include a note on how to verify successful auth or config changes (e.g., expected output or a validation command).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, no padding, every line is a concrete command or essential note. Assumes Claude knows what MCP, OAuth, stdio, etc. are. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands covering all major use cases (list, call, auth, config, daemon, codegen). Multiple calling conventions are shown with real examples including different syntaxes. | 3 / 3 |
Workflow Clarity | For a CLI reference skill, the commands are clear, but there's no sequencing guidance (e.g., when to auth before calling, when to start the daemon). The skill is more of a reference card than a workflow, which is appropriate for the tool but lacks validation/verification steps for operations like config changes. | 2 / 3 |
Progressive Disclosure | Well-organized with clear section headers, but everything is inline in a single flat file. For a skill this size (~30 lines) this is acceptable, but there are no references to external docs for advanced topics like config file format, codegen details, or auth flows that could benefit from deeper documentation. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- attilaczudor/Test
- Commit
b4fc4af
- 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.