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

88%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 highly actionable, well-sequenced skill body: every step has executable commands or templates, validation checkpoints are explicit, and error recovery is addressed both per-step and in a final checklist. The main improvement areas are token efficiency and moving the long inline doc template and sidecar patterns into separate reference files.

Suggestions

Move the full documentation markdown template (Step 6) into a reference file (e.g. references/doc-template.md) and keep only the required-sections summary plus a pointer inline, tightening both conciseness and progressive disclosure.

Trim the sidecar section's narrative detail (the '~24s' timing anecdote and per-option rationale) to a terse rule — 'install tools at build time via dockerfile_inline or a Dockerfile.bootstrap, never apk add in the entrypoint' — with the two YAML patterns.

Drop or repurpose the 'Subagent instruction' blockquote at the top; it is meta-harness text that spends context without teaching the task.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence — no explanations of Docker or compose basics — but the ~45-line inline documentation template and the sidecar narrative with the empirical '~24s on each harbor up' anecdote are padding that could be trimmed or moved to a reference. Efficient overall, so above anchor 3, but not 'every token earns its place'.	4 / 5
Actionability	Fully executable throughout: copy-paste bash validation commands in Step 1, concrete scaffold/compose/env-var/metadata commands, a full compose example, and a specific port-allocation procedure. No pseudocode; common cases are covered with ready-to-run snippets.	5 / 5
Workflow Clarity	A clear 10-step sequence with an explicit gate ('Do not advance until the current step passes'), per-step validation, a final 15-item verification checklist, and a Common Pitfalls section for error recovery — matching the validate → fix → retry anchor including feedback loops for batch file-creation operations.	5 / 5
Progressive Disclosure	Good structure: the detailed technical reference is properly delegated ('The detailed technical reference lives in .github/copilot-new-service.md') and sections are clearly headed. However, no bundle files exist and the full documentation template plus the sidecar Dockerfile patterns are inlined content that would fit better in reference files, leaving minor placement gaps relative to anchor 5.	4 / 5
	Total	18 / 20 Passed

Description

96%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: it states concrete capabilities, includes an explicit 'Use this skill whenever...' clause with multiple natural trigger phrasings, and stays firmly in third-person imperative voice. The only weakness is that several of its standalone trigger phrases are generic and could match non-Harbor service-creation requests.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations' — with comprehensive coverage of the skill's scope. Anchor 4 would require minor coverage gaps, which are absent.	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 to Harbor, integrate a new tool/app/model server...'). Matches the anchor-5 example structure.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases: 'add X to Harbor', 'new service', 'integrate Y', 'onboard Z', 'create a service for', plus the GitHub repo link expectation. Few natural phrasings a user would say are missing.	5 / 5
Distinctiveness Conflict Risk	The Harbor niche is clear and dominant, minimizing conflict risk, but several listed trigger phrases ('new service', 'integrate Y', 'onboard Z') are generic without Harbor in the phrase, leaving minor overlap risk with generic Docker/service-creation skills. Not a 5 for that reason; clearly above anchor 3.	4 / 5
	Total	19 / 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: e38ae4c

Reviewed: 1 day 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.