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 identifying the mcporter CLI tool and its concrete capabilities around MCP server management. However, it lacks an explicit 'Use when...' clause, and the trigger terms lean heavily on technical jargon that may not match how users naturally phrase requests.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to interact with MCP servers, configure tool connections, or run mcporter commands.'

Include more natural-language trigger variations such as 'connect to a tool server', 'manage MCP config', or 'call an MCP tool' to improve matching for less technical phrasings.

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 the list of capabilities, but lacks an explicit 'Use when...' clause. The when is only implied by the actions described, 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 well-crafted, concise CLI reference skill that provides highly actionable command examples organized into clear categories. Its main weakness is the lack of a sequenced workflow showing the typical setup-to-usage path (e.g., configure → authenticate → list → call) and any validation or error handling guidance.

Suggestions

Add a brief sequenced workflow section showing the typical first-use path: configure server → authenticate → list tools → call a tool, with a note on how to verify success (e.g., checking output or using --output json).

Include a brief error recovery note, e.g., what to do if auth fails (--reset flag) or if a call returns an error.

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Every line is a concrete command or essential note. No unnecessary explanations of what MCP is or how CLI tools work. Assumes Claude's competence throughout.	3 / 3
Actionability	Provides fully concrete, copy-paste ready CLI commands covering all major use cases: listing, calling with different syntaxes, auth, config, daemon management, and codegen. No vague descriptions—every item is an executable command pattern.	3 / 3
Workflow Clarity	Commands are clearly organized by category (call, auth, config, daemon, codegen), but there's no sequenced workflow showing how to go from setup to first call, no validation steps, and no error recovery guidance. For a CLI tool with auth and config steps, a basic workflow (configure → auth → call → verify) would improve clarity.	2 / 3
Progressive Disclosure	For a simple, single-purpose CLI reference skill under 50 lines with no bundle files, the content is well-organized into clear sections with logical groupings. No need for external references given the scope.	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: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 8 hours 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.