CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The body is efficient and highly actionable, with executable CLI/YAML examples and a clear simple workflow. It stays self-contained and well-organized without padding.

DimensionReasoningScore

Conciseness

The body is lean: it gives the domain pattern, executable CLI and YAML examples, and a short notes list, without explaining concepts Claude already knows (e.g., what a gateway is).

3 / 3

Actionability

Examples are copy-paste ready (e.g., "agt apply worker --name alice --model qwen3.5-plus --expose 8080" and a complete Worker/Team YAML), with the exact auto-generated domain pattern spelled out.

3 / 3

Workflow Clarity

The simple apply→verify→remove flow is unambiguous, including a verification step ("agt get worker alice / Look for status.exposedPorts") and a precondition note that the container and service must be listening.

3 / 3

Progressive Disclosure

The skill is a single self-contained file with well-organized sections (Overview, How It Works, Usage, Important Notes); no external references are needed so the clean structure suffices.

3 / 3

Total

12

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 concise, uses third person, and clearly answers both what and when with an explicit trigger. Its only weakness is specificity, since it names one capability rather than a list of distinct actions.

Suggestions

List a couple of distinct concrete actions the skill performs (e.g., publishing ports and generating access domains) to lift specificity from 2 to 3.

Consider adding natural trigger variations like "expose a port" or "get a public URL" alongside "publish".

DimensionReasoningScore

Specificity

"Expose worker HTTP services via Higress gateway" names the domain and a concrete action, but the description describes a single capability (expose/publish) rather than listing multiple distinct concrete actions as the top anchor requires.

2 / 3

Completeness

It states what the skill does ("Expose worker HTTP services via Higress gateway") and gives an explicit "Use when admin asks to publish..." trigger, answering both what and when.

3 / 3

Trigger Term Quality

"Use when admin asks to publish a worker's web app or API to make it externally accessible" covers natural phrasings an admin would say (publish, web app, API, externally accessible).

3 / 3

Distinctiveness Conflict Risk

The niche (worker HTTP services via Higress gateway, auto-generated domains) is specific with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentscope-ai/AgentTeams
Reviewed

Table of Contents

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.