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
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 is strong on specificity and distinctiveness, clearly naming the mcporter CLI tool and listing concrete actions like listing, configuring, authenticating, and calling MCP servers. However, it lacks an explicit 'Use when...' clause and relies on somewhat technical jargon that may not match natural user language patterns.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to interact with MCP servers, manage MCP tool configurations, or invoke MCP tools from the command line.'
Include more natural trigger terms users might say, such as 'connect to MCP', 'run MCP tool', 'manage tool servers', or 'MCP configuration'.
| 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 distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause. The when is only implied by the action descriptions, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'mcporter', 'MCP servers', 'CLI', 'stdio', 'HTTP', 'auth', but these are fairly technical. Missing natural user phrases like 'connect to a tool server' or 'manage MCP connections'. Users might say 'MCP' but many trigger terms are jargon-heavy. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — 'mcporter CLI' and 'MCP servers/tools' are highly specific identifiers that are unlikely to conflict with other skills. The combination of the tool name and protocol makes this clearly distinguishable. | 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 strong, concise CLI reference skill that provides highly actionable, copy-paste ready commands organized into clear sections. Its main weakness is the lack of a sequenced workflow showing the typical setup-to-usage path (configure → auth → list → call), which would help Claude understand the expected order of operations for first-time setup.
Suggestions
Add a brief sequenced workflow section showing the typical first-time setup flow: configure server → authenticate → list tools → call a tool, so Claude knows the expected order of operations.
Consider adding a note about how to verify a successful call or diagnose failures (e.g., checking daemon status before calls, interpreting error output).
| 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 fully 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 | Commands are clearly listed but there's no sequenced workflow showing how to go from setup to first call (e.g., configure → auth → list → call). For a CLI reference skill this is acceptable, but a brief workflow showing the typical sequence would improve it. No validation/verification steps are mentioned. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single-purpose CLI reference, the content is well-organized into logical sections (Quick start, Call tools, Auth + config, Daemon, Codegen, Notes) with clear headers. No need for external file references given the scope. | 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
af8bd5f
- 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.