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

92%

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

85%

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

A thorough, highly actionable onboarding workflow with concrete executable examples, explicit validation checkpoints, and clean single-level reference structure. Its only weakness is length — some advisory guidance could be trimmed for token efficiency.

Suggestions

Tighten the screenshot guidance in Step 6 to the essential rule (one UI screenshot at docs/harbor-${handle}.png, captured via agent-browser during Test) and drop the framing/1280×800 advisory prose.

The opening blockquote subagent instruction and the 'Harbor is a modular Docker Compose project' preamble overlap with the description; consider trimming the preamble to one line.

Condense the sidecar section's narrative (the 24s apk-add timing anecdote) into a one-line rationale plus the two patterns, keeping the empirical detail only if it changes behavior.

Dimension	Reasoning	Score
Conciseness	Content is dense and Harbor-specific with no basic-concept padding, but at ~400 lines some advisory prose (e.g. screenshot framing: '1280×800 is standard. Avoid login screens devoid of branding') could be tightened; not every token is load-bearing.	2 / 3
Actionability	Provides fully executable bash, YAML, and TypeScript snippets throughout (scaffold, validate, compose skeleton, metadata entry, logo resolution) that are copy-paste ready, matching the score-3 anchor.	3 / 3
Workflow Clarity	Steps 0–9 are clearly sequenced with 'Do not advance until the current step passes', inline validation commands, a final Validation Checklist, and a Common Pitfalls feedback section — explicit checkpoints for a risky multi-step operation.	3 / 3
Progressive Disclosure	Well-organized into clearly labeled steps with a one-level-deep external reference ('The detailed technical reference lives in .github/copilot-new-service.md') and a single reference example doc; no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, third-person description that names concrete actions, provides explicit 'Use when...' trigger guidance with natural user phrases, and occupies a clear Harbor-specific niche. Voice is correctly third person.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations' — matching the multi-action anchor rather than the single-domain score-2 example.	3 / 3
Completeness	Explicitly states both what ('Add a new service to Harbor — scaffold...') and when ('Use this skill whenever the user wants to add a new service to Harbor... Triggers on phrases like...'), satisfying the explicit-trigger bar.	3 / 3
Trigger Term Quality	Covers natural phrases a user would say: 'add X to Harbor', 'new service', 'integrate Y', 'onboard Z', 'create a service for', plus a GitHub repo link trigger — broad coverage, not jargon.	3 / 3
Distinctiveness Conflict Risk	Harbor-specific niche with distinct triggers tied to the Harbor ecosystem; unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: ed20a18

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.