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
Quality
77%
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 ./openclaw/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 effectively communicates specific capabilities around the mcporter CLI tool with good technical detail and clear distinctiveness. However, it lacks an explicit 'Use when...' clause and relies heavily 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 interact with MCP servers, configure tool connections, or generate CLI commands for MCP protocols.'
Include more natural trigger terms users might say, such as 'connect to external tools', 'server configuration', or 'tool authentication'.
| 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 provides comprehensive command coverage with practical examples while respecting token budget. The main weakness is the lack of workflow guidance for multi-step operations like auth setup or config management, which could benefit from explicit validation/verification steps.
Suggestions
Add a brief workflow for auth setup showing how to verify successful authentication (e.g., 'After `mcporter auth`, verify with `mcporter list <server>` to confirm access')
Include error handling guidance for common failure modes (e.g., what to do if daemon isn't running when calling tools)
| 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 | Provides concrete, copy-paste ready commands with multiple syntax variations. Examples cover common use cases (selectors, function syntax, URLs, stdio, JSON payloads) with real-world patterns. | 3 / 3 |
Workflow Clarity | Commands are clearly organized by category, but lacks workflow guidance for multi-step operations. No validation steps mentioned for operations like config changes or auth flows that could fail. | 2 / 3 |
Progressive Disclosure | For a CLI reference skill under 50 lines, the organization is appropriate. Clear section headers group related commands logically, and the content doesn't need external file references. | 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.