phoenix-otel-development

Guide for the phoenix-otel TypeScript package — OTel registration, stack-based global provider management, and provider lifecycle.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./js/packages/phoenix-otel/.agents/skills/phoenix-otel-development/SKILL.md

Quality

Content

68%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 exceptionally concise and well-structured as an overview-to-rules router, but its main development guidance lives in rule files that are missing from the bundle, limiting actionability and leaving the workflow without explicit checkpoints.

Suggestions

Ship the referenced rules/*.md files (global-provider-lifecycle.md, register-api.md, testing.md) so the one-level-deep references resolve.

Add a short explicit workflow sequence with a validation checkpoint, e.g. 'After changes, run `pnpm --filter phoenix-otel test` and fix failures before committing.'

Inline one minimal concrete example (e.g. a register() call) so the skill is actionable even before a rule file is opened.

Dimension	Reasoning	Score
Conciseness	The body is lean — ~20 lines of overview, a rule-file table, and a single build command — with no padding and no explanation of concepts Claude already knows, matching the "lean and efficient; every token earns its place" anchor.	5 / 5
Actionability	It provides one concrete executable command ("pnpm --filter phoenix-otel test") and clear navigational guidance, but the core OTel development instructions are deferred to rules/*.md files that are not present in the bundle, leaving the primary task with incomplete actionable detail.	3 / 5
Workflow Clarity	A rough implicit sequence exists (read existing code → consult the relevant rule file → build/test), but there are no explicit validation checkpoints or feedback loops, fitting the "sequence present but checkpoints missing or implicit" anchor.	3 / 5
Progressive Disclosure	Structure is exemplary — a concise overview plus a well-signaled one-level-deep rule-file table with a 'When to read' column — but the referenced rules/*.md files do not exist in the bundle, so the references are partly dangling, which is more than a minor gap and blocks a 5.	4 / 5
	Total	15 / 20 Passed

Description

70%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 specific and well-targeted to a clear niche, but it lacks an explicit "Use when..." trigger clause, which caps completeness at 3. Adding concrete trigger phrases would raise the completeness and trigger-term dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when registering OpenTelemetry providers or managing provider lifecycle in phoenix-otel.'

Spell out 'OpenTelemetry' alongside the 'OTel' abbreviation to broaden natural trigger-term coverage.

Lead with concrete verbs (e.g. 'Registers', 'Manages', 'Coordinates') instead of the passive 'Guide for' to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("phoenix-otel TypeScript package") and lists several concrete capability areas — "OTel registration, stack-based global provider management, and provider lifecycle" — with only minor coverage gaps, fitting the "lists several specific actions" anchor rather than the 1-2 actions of score 3.	4 / 5
Completeness	It has a clear "what" but no "Use when..." trigger clause, so per the rubric's missing-trigger cap it cannot exceed 3; the "when" is only weakly implied from the package name.	3 / 5
Trigger Term Quality	Includes natural developer terms like "OTel registration", "provider lifecycle", and "TypeScript" that users would actually say, but omits the spelled-out "OpenTelemetry" synonym and common variations, landing at good-but-not-comprehensive coverage rather than 5.	4 / 5
Distinctiveness Conflict Risk	It targets a single named package (phoenix-otel) with a distinct OTel/provider niche, giving minimal overlap with other skills — a clear niche as the score-5 anchor describes.	5 / 5
	Total	16 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: Arize-ai/phoenix
Path: js/packages/phoenix-otel/.agents/skills/phoenix-otel-development/SKILL.md
Commit: 8adf337

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.