CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

phoenix-harbor

Configure and interpret the Phoenix plugin for Harbor agent evaluations. Use when adding `arize-phoenix` to Harbor jobs, choosing ATIF tracing, mapping Harbor tasks and rewards to Phoenix experiments, comparing agents or models, resuming jobs, or troubleshooting Harbor records in Phoenix.

Quality

93%

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

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 reference for a complex integration: exact commands, kwargs, and interpretation tables, with thorough failure and resume semantics. The main improvements are removing duplication between inline constraints and the 'Current boundaries' section, and splitting the ATIF conversion minutiae into a reference file so SKILL.md stays a lean overview.

Suggestions

State each operational constraint (regrade/derived jobs, multi-dataset jobs, deferred live OTLP) once — in 'Current boundaries' — instead of repeating it in the trace-mode and dataset sections, trimming roughly 10-15 lines.

Add an explicit post-run verification step to the main workflow, e.g. open the experiment in Phoenix and confirm the expected run count and trace linkage before reporting success to the user.

Move the ATIF converter edge-case rules (source_call_id pairing, unmatched step observations, token-detail attribute mapping, v1.8 limitations) into a references/ file linked from 'Interpret ATIF traces', keeping only the span hierarchy and key interpretation caveats in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense with plugin-specific facts Claude cannot know (record mappings, fail-stop semantics, exact kwargs) and explains no general concepts, but it is not fully lean: the regrade/derived-job, multi-dataset, and deferred-OTLP constraints each appear inline and again in 'Current boundaries', and version-sensitive facts ('converter supports ATIF v1.0 through v1.7', 'Phoenix server 15.0 or newer') are not isolated in a deprecation/compatibility section. This sits at 'efficient with minor instances that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is copy-paste ready throughout: 'uv pip install "arize-phoenix-client[harbor]"', PHOENIX_COLLECTOR_ENDPOINT/PHOENIX_API_KEY exports, a complete 'harbor run ... --plugin arize-phoenix' example, exact '--plugin-kwarg' flags for every option, a task.toml reference-output snippet, and two interpretation tables. It fully matches the anchor for executable commands covering the common cases.

5 / 5

Workflow Clarity

The sections form a coherent sequence (requirements, trace mode, destination, add plugin, predict records, interpret, failures/resume) with explicit failure semantics ('Setup failures stop the job before trials run') and a numbered 4-step comparison checklist. It falls short of anchor 5 because there is no explicit post-run verification checkpoint for confirming ingestion in Phoenix, though the documented fail-stop behavior keeps it above the batch-validation cap of 3.

4 / 5

Progressive Disclosure

No bundle files exist, and the single file is organized into twelve scannable sections with clearly signaled external documentation links at the end. It is not anchor 5 because the file is long (~240 lines) and deep reference material — the ATIF converter edge-case rules (source_call_id pairing, unmatched observations, token-attribute mapping) — is inlined rather than split into a one-level-deep reference file.

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.

An exemplary description: it states a clear capability, enumerates concrete trigger scenarios in the user's natural vocabulary, and is tightly scoped to a named integration so mis-triggering is unlikely. Both 'what' and 'when' are answered explicitly and concretely.

DimensionReasoningScore

Specificity

The description enumerates six concrete actions ('adding `arize-phoenix` to Harbor jobs', 'choosing ATIF tracing', 'mapping Harbor tasks and rewards to Phoenix experiments', 'comparing agents or models', 'resuming jobs', 'troubleshooting Harbor records in Phoenix') with comprehensive coverage of the skill's domain. It exceeds anchor 4 because there are no minor gaps — every supported use case is named.

5 / 5

Completeness

It clearly answers 'what' ('Configure and interpret the Phoenix plugin for Harbor agent evaluations') and 'when' via an explicit 'Use when...' clause with concrete trigger phrases. It is not score 4 territory because the 'when' is fully explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Natural terms a user would actually say are covered: the plugin name 'arize-phoenix', 'Phoenix', 'Harbor', 'ATIF tracing', 'comparing agents or models', and 'troubleshooting'. This matches the comprehensive-synonyms anchor rather than anchor 4, since no common variation for this niche is missing.

5 / 5

Distinctiveness Conflict Risk

The description names a highly specific integration (the arize-phoenix plugin bridging Harbor and Phoenix), giving it a clear niche with distinct triggers and minimal conflict risk with any other skill. It uses third-person/declarative voice with no person violations.

5 / 5

Total

20

/

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

Arize-ai/phoenix

Path

plugins/codex/arize-phoenix/skills/phoenix-harbor/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.