mcporter
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, CLI/type generation, and MCP-backed skills that need a durable command path.
76
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 technically detailed and specific about what the mcporter CLI skill does, covering a good range of concrete actions. Its main weakness is the lack of an explicit 'Use when...' clause and reliance on technical jargon that users may not naturally use. The skill is highly distinctive due to its narrow focus on MCP server management via a specific CLI tool.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with MCP servers, connect to tool providers, manage MCP configurations, or invoke remote tools via the mcporter CLI.'
Include more natural trigger terms that users might say, such as 'connect to a tool server', 'manage MCP config', 'call a remote tool', or 'set up MCP authentication'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'list, configure, auth, and call MCP servers/tools', 'ad-hoc servers, config edits, CLI/type generation'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | The 'what' is well-covered (list, configure, auth, call MCP servers/tools, config edits, CLI generation). However, there is no explicit 'Use when...' clause. The phrase 'MCP-backed skills that need a durable command path' hints at when, but it's not a clear trigger guidance statement. Per rubric, missing 'Use when' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'MCP servers', 'MCP tools', 'stdio', 'HTTP', 'CLI', 'auth', and 'mcporter', but these are fairly technical. Missing natural user phrases like 'connect to a tool server' or 'run MCP command'. Users may not naturally say 'mcporter' or 'durable command path'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to the 'mcporter CLI' tool and MCP protocol interactions. The combination of MCP servers, stdio/HTTP transport, and CLI generation creates a clear niche that is unlikely to conflict with other skills. | 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 skill that provides highly actionable CLI command patterns for mcporter. Its main strengths are token efficiency and concrete executable examples covering diverse usage patterns. The primary weaknesses are the lack of validation/error-recovery steps in workflows and the absence of actual cross-references to deeper documentation despite defining a multi-file skill structure.
Suggestions
Add validation/error-recovery guidance after tool calls, e.g., checking exit codes, verifying output with --output json, and retry patterns for auth failures.
Include links to actual reference files or note which files should be consulted for extended schemas, troubleshooting, or advanced configuration patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what MCP is, doesn't explain basic concepts, and every section delivers actionable information without padding. The skill-first MCP shape section is dense but earns its place by defining a clear project structure pattern. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands for every operation: listing, calling tools, auth, daemon management, and codegen. Multiple call syntax variants (selector, function, URL, stdio, JSON payload) give Claude specific executable patterns for different scenarios. | 3 / 3 |
Workflow Clarity | The 'durable MCP skill' workflow (inspect schema then call tool) is clear but lacks validation/error recovery steps. For operations like creating skills with mcp.json configs or calling tools that may fail, there are no explicit checkpoints or feedback loops for verifying success or handling errors. | 2 / 3 |
Progressive Disclosure | The skill defines a good file structure pattern (mcp.json, references/, scripts/) suggesting content should be split, but the SKILL.md itself doesn't link to any actual reference files or deeper documentation. The content is well-organized with clear sections but could better signal where to find extended information. | 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
- trpc-group/trpc-agent-go
- Commit
fcc550d
- 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.