service-publishing

Expose worker HTTP services via Higress gateway. Use when admin asks to publish a worker's web app or API to make it externally accessible.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 tight, highly actionable skill body with copy-paste CLI and YAML examples and a sensible verification hint. The main improvements are trimming the longer worked examples and adding an explicit post-apply validation step.

Suggestions

Add an explicit post-apply verification step (e.g., curl the generated domain or confirm status.exposedPorts is Ready) to form a validate-and-recover feedback loop.

Consider moving the full multi-document Team example behind a brief inline summary to reduce length while retaining the common single/multi-port cases up front.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence (no preamble explaining Higress or containers), but the dual CLI/YAML treatment plus the multi-document Team example add length that could be trimmed. Not a 5 because a few sections (e.g., the full Team YAML) are more elaborate than essential.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands and complete YAML covering single port, multiple ports, inspection, removal, and Team references. Matches the 'fully executable, specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	Clear sequence (add expose -> controller provisions domain/route -> check via `agt get worker` / status.exposedPorts) with a verification checkpoint and a prerequisite checklist in Important Notes. Not a 5 because there is no explicit validate-and-recover feedback loop, and not capped at 3 since exposing a port is not a destructive or batch operation.	4 / 5
Progressive Disclosure	Single self-contained file organized into clear sections (Overview, How It Works, Usage, Important Notes) with no nested references, which is appropriate for this scope. Not a 5 because it slightly exceeds the simple-skill line count and the inlined Team example is content that could live in an optional advanced section.	4 / 5
	Total	17 / 20 Passed

Description

82%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 concise, well-constructed description that clearly states capability and trigger conditions with strong distinctiveness. It is only slightly limited on specificity (single action) and could add a couple of synonyms to round out trigger terms.

Suggestions

Expand the capability clause with one or two more concrete actions (e.g., 'auto-generates a domain and routes traffic') to lift specificity.

Add a natural synonym such as 'deploy' or 'ingress' alongside 'publish'/'expose' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (worker HTTP services, Higress gateway) and one concrete action ('Expose'), but does not enumerate multiple specific capabilities, matching the '1-2 concrete actions, not comprehensive' anchor. Not a 4 because only a single action is described rather than several.	3 / 5
Completeness	Explicitly answers both 'what' ('Expose worker HTTP services via Higress gateway') and 'when' ('Use when admin asks to publish a worker's web app or API to make it externally accessible') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('publish a worker's web app or API', 'make it externally accessible') alongside 'expose', giving good keyword coverage. Not a 5 because synonyms like 'deploy'/'ingress' and an explicit file/CR extension are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Higress gateway publishing for worker containers) with distinct, specific triggers and minimal overlap risk with generic deploy skills.	5 / 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/skills/service-publishing/SKILL.md
Commit: 223ddc2

Reviewed: 11 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.