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.

1.73x

Quality

77%

Does it follow best practices?

Impact

85%

1.73x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/mcporter/SKILL.md

Quality

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 tool (mcporter) and listing concrete actions like listing, configuring, authenticating, and calling MCP servers. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms lean technical without covering natural user language variations.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to interact with MCP servers, manage MCP tool configurations, or run MCP tools from the command line.'

Include more natural trigger terms users might say, such as 'connect to MCP', 'run MCP tool', 'MCP setup', or 'manage tool servers'.

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 specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the capabilities listed.	2 / 3
Trigger Term Quality	Includes relevant terms like 'MCP servers', 'CLI', 'stdio', 'HTTP', 'auth', 'config', but these are somewhat technical. Missing natural user phrases like 'connect to a tool server' or 'set up MCP'. The tool name 'mcporter' is specific but niche.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific tool name 'mcporter' and the narrow domain of MCP server management via CLI. Unlikely to conflict with other skills given the specific technology and tool references.	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, highly concise CLI reference skill that provides excellent actionability through concrete command examples covering multiple invocation patterns. Its main weakness is the lack of workflow sequencing—there's no guidance on the typical order of operations (setup → auth → use) or error handling. For a reference-style skill, this is a strong entry.

Suggestions

Add a brief typical workflow sequence (e.g., 'First run: config add → auth → list → call') to help Claude understand the expected order of operations.

Add a brief note on error handling or common failure modes (e.g., 'If auth fails, run mcporter auth --reset <server>; if daemon not running, start it first').

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 (call, auth, config, daemon, codegen). Multiple invocation patterns are shown with real examples including different syntaxes.	3 / 3
Workflow Clarity	Commands are clearly listed but there's no sequenced workflow showing how steps connect (e.g., configure → auth → call). For a CLI reference skill this is mostly fine, but there's no guidance on what to do if a call fails, auth expires, or daemon isn't running.	2 / 3
Progressive Disclosure	For a simple, concise CLI reference skill under 50 lines, the content is well-organized into logical sections (Quick start, Call tools, Auth, Daemon, Codegen, Notes) with clear headers. No need for external file references given the brevity.	3 / 3
	Total	11 / 12 Passed

Validation

72%

Warnings & errors only

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: Hung-Reo/hungreo-openclaw
Commit: e893157

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.