mcporter

Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with executable commands and a clear multi-step workflow. The main gaps are a missing error-recovery feedback loop in the discovery workflow and a slightly long inlined example template.

Suggestions

Add an explicit feedback loop to the discovery workflow (e.g., 'If the new server does not appear in mcporter list, re-run agentteams-sync or ask your coordinator to confirm the config was pushed').

Consider moving the example SKILL.md template into a references/ file (e.g., references/skill-template.md) and linking to it, to keep the main body leaner.

Trim minor over-explanatory phrases such as 'read carefully to understand each tool' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Largely lean with brief commented command blocks and tight notes, but a few phrases like 'read carefully to understand each tool' and the inlined example template could be trimmed, fitting the 'efficient with minor over-explanation' anchor rather than the fully lean 5.	4 / 5
Actionability	Provides copy-paste ready, executable commands covering the common cases — 'mcporter list', 'mcporter list <server-name> --schema', and both key=value and --args JSON call forms — matching the fully executable top anchor.	5 / 5
Workflow Clarity	The new-MCP-server workflow has four clearly sequenced steps with a 'Verify the new server appears' checkpoint, but lacks an explicit error-recovery feedback loop if verification fails, fitting the 'clear sequence with most checkpoints, minor gaps' anchor.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Commands, coordinator workflow, Important Notes) with no nested references and no need for external files, though the inlined example SKILL.md template is somewhat long and could live in a separate reference, keeping it just below the top anchor.	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and when to use it, with concrete actions and natural trigger phrases. The only weakness is the somewhat broad 'external APIs' trigger, which slightly raises overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions — 'Discover and call MCP Server tools via the mcporter CLI' and 'generating skill documentation for new MCP servers' — with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' (discover/call tools, generate skill docs) and 'when' with concrete trigger phrases ('Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs'), matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases appear — 'Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs' — giving good keyword coverage, though a few synonyms/variations are missing, so it stops short of the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The 'MCP Server tools via the mcporter CLI' niche is distinct with clear triggers, but the broad 'call external APIs' trigger carries minor overlap risk with other API-calling skills, placing it just below the minimal-conflict 5.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: agentscope-ai/AgentTeams
Path: manager/agent/worker-agent/skills/mcporter/SKILL.md
Commit: 223ddc2

Reviewed: 5 days 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.