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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, actionable CLI reference with concrete commands and a clear inspect-then-call workflow, held back from a perfect score only by the verbose Credential handling prose.

Suggestions

Tighten the Credential handling section: consolidate the successive 'Do not...' clauses into a short bulleted list of rules so the guidance stays actionable without the prose padding.

Collapse the repeated explanations that --config is the credential-bearing source of truth into a single stated rule, since the same point is made across two paragraphs.

Dimension	Reasoning	Score
Conciseness	The command reference sections are lean, but the Credential handling section runs to dense multi-clause prose with repeated 'Do not...' guidance and re-explained --config/source-of-truth points that could be tightened, fitting the score-2 'mostly efficient but could be tightened' anchor rather than 'every token earns its place'.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands across every section (e.g. 'mcporter call linear.list_issues team=ENG limit:5', 'mcporter --config path/to/skill/mcp.json list <server> --schema --output json'), matching the score-3 anchor for concrete, specific examples.	3 / 3
Workflow Clarity	The durable-skill workflow is a clear, unambiguous sequence — 'first inspect the server schema' then 'call the selected tool with explicit arguments' — where the schema inspection acts as the checkpoint; for this simple workflow the scoring note permits a 3 without an elaborate validate/retry loop.	3 / 3
Progressive Disclosure	Content is well-organized into clearly labeled sections (Quick start, Call tools, Auth + config, Daemon, Codegen, Notes) with no nested references; as a self-contained CLI cheat-sheet it needs no external file splits, satisfying the well-organized-sections allowance.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 specific and distinctive, naming concrete mcporter actions and natural MCP trigger terms, but it omits an explicit 'Use when...' activation clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to call, configure, or auth an MCP server/tool, or needs a durable command path for an MCP-backed skill,' so the activation condition is unambiguous.

State the 'when' contrastively — e.g. prefer mcporter when an MCP capability must be repeatable/durable vs. a one-off ad-hoc call — to make Claude's routing decision explicit.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "list, configure, auth, and call MCP servers/tools directly", "config edits", "CLI/type generation" — matching the anchor for multiple specific concrete actions rather than the partial score-2 anchor.	3 / 3
Completeness	It clearly answers "what" (use mcporter to list/configure/auth/call MCP servers) but lacks an explicit "Use when..." trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 2, so it is not the score-3 level.	2 / 3
Trigger Term Quality	Natural domain terms a user would say are well covered — "mcporter CLI", "MCP servers/tools", "call", "configure", "auth", "list" — rather than generic or jargon-only phrasing; not the score-2 case of missing common variations.	3 / 3
Distinctiveness Conflict Risk	It targets a clear niche (the mcporter CLI for MCP servers/tools) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 anchor rather than the overlapping score-2 case.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 16 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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Commit: 737835b

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