new-service

Add a new service to Harbor — scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations. Use this skill whenever the user wants to add a new service to Harbor, integrate a new tool/app/model server, create a compose configuration for a new project, or onboard any software into the Harbor ecosystem. Triggers on phrases like "add X to Harbor", "new service", "integrate Y", "onboard Z", "create a service for", or when the user provides a GitHub repo link and expects it to become a Harbor service. Even if the user just says a project name and implies they want it in Harbor, this skill applies.

Quality

91%

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 strong, highly actionable procedural skill: concrete commands and templates, a clear 9-step sequence, and a final validation checklist. The main weaknesses are minor verbosity in the sidecar/screenshot rationale and validation criteria that are claimed globally rather than made explicit per step.

Suggestions

Make per-step validation explicit instead of relying on the global "Every step has validation criteria" claim — add a concrete pass/fail check for Steps 2, 4, and 5 so the "do not advance until it passes" loop has a defined condition.

Tighten the sidecar rationale (the ~24s empirical apk-add note) and the screenshot framing guidance to the key instruction, removing detail that does not change the action.

Consider moving the full documentation template and screenshot-capture commands into a referenced file so SKILL.md stays a leaner overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	Dense and almost entirely task-specific (Harbor conventions, env-var patterns, file paths) with no padding of concepts Claude already knows, but the sidecar rationale (the empirical ~24s apk-add note) and the screenshot framing guidance carry minor over-explanation that could be trimmed; leans above the 3-anchor but not fully lean at 5.	4 / 5
Actionability	Fully executable throughout — copy-paste-ready commands (harbor dev scaffold, harbor config update, harbor dev add-logos), a complete compose YAML example, env-var and metadata TS templates, and a documentation template covering the common cases, matching the 5-anchor.	5 / 5
Workflow Clarity	Clear Step 0–9 sequence with a final 14-item Validation Checklist and the global "Do not advance until the current step passes" rule, but per-step validation criteria are stated as a claim rather than made explicit for every step (e.g., Steps 2, 4, 5 lack a concrete pass condition), and the fix-and-retry feedback loop is implicit — placing it just below the 5-anchor.	4 / 5
Progressive Disclosure	Good section structure with one clearly signaled one-level-deep reference ("The detailed technical reference lives in `.github/copilot-new-service.md") and a reference example doc (docs/2.3.52-Satellite-Windmill.md); no bundle files exist to offload detail, so the ~390-line body keeps some content (full doc template, screenshot capture) inline that could live in a reference — good but not exemplary.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is excellent: it concisely states concrete capabilities, gives explicit "Use when..." trigger guidance with natural phrasing variants, and is tightly scoped to a distinct Harbor-onboarding niche. Voice is appropriately third person throughout, so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations" — giving comprehensive coverage of what the skill does, matching the 5-anchor example of several specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ("Add a new service to Harbor — scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations") and when ("Use this skill whenever the user wants to add a new service... Triggers on phrases like...") with concrete trigger phrases, matching the 5-anchor.	5 / 5
Trigger Term Quality	Comprehensive natural-language triggers users would actually say — "add X to Harbor", "new service", "integrate Y", "onboard Z", "create a service for", plus the GitHub-repo-link case; not merely 4 because synonyms and paraphrases are well covered.	5 / 5
Distinctiveness Conflict Risk	Harbor-scoped niche with service-onboarding-specific triggers ("add X to Harbor", "onboard Z") makes overlap with unrelated skills minimal; clearly distinct, matching the 5-anchor of a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: av/harbor
Path: .agents/skills/new-service/SKILL.md
Commit: 67cbe66

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