CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-artifacts

Manage Harness Artifact Registry (AR) via MCP. Configure private registries for Docker, Helm, Maven, npm, and PyPI artifacts, set up upstream proxies for caching public images, configure RBAC and cross-region replication, and define security scanning policies with CVE thresholds and license compliance checks. Use when asked to set up an artifact registry, configure Docker or Helm repositories, manage artifact security scanning, or set up replication. Do NOT use for creating connectors to external registries (use create-connector instead). Trigger phrases: artifact registry, docker registry, helm repository, artifact security, image scanning, private registry, artifact replication, CVE threshold, license compliance, SBOM.

Quality

83%

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

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

The body is concise, well-sectioned, and free of padding, but its core weakness is executability: the main configuration workflows are described rather than prescribed, with the only substantive tool-call example reduced to placeholder comments, and no validation checkpoints after configuration steps. Progressive disclosure is also underdeveloped — everything lives inline with no reference files.

Suggestions

Replace the placeholder comments in the harness_create pipeline example ('# vulnerability scanning step', '# block if thresholds exceeded') with the actual step definitions and parameters, and add the concrete harness MCP calls for creating repositories and applying scanning policies.

Add validation checkpoints after each configuration step (e.g., list the created repository or verify the policy attached before proceeding), turning the Troubleshooting content into an inline fix-and-retry feedback loop.

Split the format-specific configuration details (Docker/Helm/Maven/npm/PyPI), Performance Notes, and Troubleshooting into one-level-deep reference files (e.g., references/formats.md, references/troubleshooting.md) linked from the body.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven and assumes Claude's competence — it never explains what Docker, Helm, or CVEs are, and every section (instructions, examples, performance notes, troubleshooting) carries operational information. It matches the level-5 anchor ('lean and efficient; assumes Claude's competence; every token earns its place'); even level 4 would require identifiable over-explanation to trim, and there is essentially none.

5 / 5

Actionability

There are two MCP tool-call blocks, but the first (harness_list) is trivial and the second is skeletal pseudocode — the pipeline body contains placeholder comments like '# vulnerability scanning step' and '# block if thresholds exceeded' with no actual steps. The bulk of the configuration guidance ('Configure scanning policies: ...', 'Gather from the user: ...') describes what to do without the concrete tool calls to do it, matching the level-3 anchor (some concrete guidance but incomplete; pseudocode instead of executable code). It is above level 2 because real tool names, parameters, and a worked pipeline skeleton are present, but below level 4 because the core configuration actions lack executable detail.

3 / 5

Workflow Clarity

Steps 1-4 establish a coherent sequence (scope, identify task, configure, scanning policy), but there are no validation checkpoints — nothing verifies the repository was created or the policy applied before proceeding, and the Troubleshooting section is a separate reference rather than an inline feedback loop. This matches the level-3 anchor (steps listed but validation gaps; checkpoints missing or implicit); it is above level 2 because the sequence is well-defined and task-branched, and below level 4 because verification is entirely implicit.

3 / 5

Progressive Disclosure

The body has clear section headers but is a single ~123-line file with no bundle files (references/, scripts/, assets/ do not exist); format-specific configuration details, performance notes, and troubleshooting are all inlined where a larger skill would split them into one-level-deep references. This matches the level-3 anchor (some structure but could be better organized; content that should be separate is inline); it is above level 2 because sections are well-labeled and navigable, and below level 4 because there is no reference structure at all for content that is outgrowing a single file.

3 / 5

Total

14

/

20

Passed

Description

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

An exemplary description: third-person voice, concrete and comprehensive capabilities, explicit 'Use when' guidance, a rich trigger-phrase list, and explicit disambiguation against a neighboring skill. The only gap is a handful of missing natural synonyms (e.g., 'vulnerability scanning', 'container registry').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: 'Configure private registries for Docker, Helm, Maven, npm, and PyPI artifacts, set up upstream proxies for caching public images, configure RBAC and cross-region replication, and define security scanning policies with CVE thresholds and license compliance checks.' It matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage) and is a clear step above level 4, which allows minor coverage gaps; no capability here is vague.

5 / 5

Completeness

Both questions are answered explicitly: 'what' via the detailed action list, and 'when' via 'Use when asked to set up an artifact registry, configure Docker or Helm repositories, manage artifact security scanning, or set up replication' plus a dedicated trigger-phrase list. This matches the level-5 anchor exactly; level 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Explicit trigger phrases provide good coverage: 'artifact registry, docker registry, helm repository, artifact security, image scanning, private registry, artifact replication, CVE threshold, license compliance, SBOM.' This fits the level-4 anchor (good keyword coverage, a few natural terms missing) rather than 5 because common variations like 'vulnerability scanning', 'container registry', or 'package registry/repository' are absent; it is well above level 3 since many natural user phrasings are present.

4 / 5

Distinctiveness Conflict Risk

It names a clear niche (Harness Artifact Registry via MCP) with distinct triggers and even negative guidance: 'Do NOT use for creating connectors to external registries (use create-connector instead).' This is the level-5 anchor (clear niche, distinct triggers, minimal conflict risk); level 4's 'minor overlap risk with closely related skills' is outperformed by the explicit disambiguation.

5 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

harness/harness-ai

Path

plugins/claude/skills/manage-artifacts/SKILL.md

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.