phoenix-otel-development

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The body is admirably concise and well-organized, but it delegates all substantive guidance to rule files that are absent from the bundle, leaving it non-actionable in isolation and breaking its progressive-disclosure references.

Suggestions

Ship the referenced rules/ files (global-provider-lifecycle.md, register-api.md, testing.md) or remove the table, since broken references cap progressive_disclosure and actionability.

Add an explicit validation checkpoint in the workflow (e.g., 'run pnpm --filter phoenix-otel test and confirm it passes before finishing') so provider-lifecycle changes have a feedback loop.

Include at least one inline, copy-paste-ready snippet for the core registration/lifecycle step so the skill is actionable without the rule files.

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-line purpose statement, a directive, a compact rule-file table, and a short build/test block — with every token earning its place and no padding of concepts Claude already knows.	3 / 3
Actionability	It offers a concrete build/test command ('pnpm --filter phoenix-otel test') and a directive, but the core registration/lifecycle instructions are delegated to rule files that are not present in the bundle, so the executable guidance in SKILL.md itself is incomplete.	2 / 3
Workflow Clarity	A sequence is implied (read existing code, consult rule files, build/test) but there are no explicit validation checkpoints or feedback loops for the fragile provider-lifecycle operations the rubric calls out.	2 / 3
Progressive Disclosure	The body references three rule files (rules/global-provider-lifecycle.md, rules/register-api.md, rules/testing.md) but no rules/ directory exists in the bundle, so the referenced paths are broken and navigation fails.	1 / 3
	Total	8 / 12 Passed

Description

67%

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 distinct, naming concrete OTel capabilities tied to a named package, but it omits any explicit 'Use when...' trigger guidance and leans on internal jargon over natural user keywords.

Suggestions

Add a 'Use when...' clause naming the natural user triggers (e.g., 'Use when registering OpenTelemetry providers, configuring span processors, or managing provider lifecycle in Phoenix TypeScript packages').

Soften internal jargon with natural terms a user would say, such as 'OpenTelemetry setup', 'tracing configuration', and 'provider mount/detach'.

Dimension	Reasoning	Score
Specificity	It names multiple concrete actions/capabilities — 'OTel registration', 'stack-based global provider management', and 'provider lifecycle' — rather than vague abstractions.	3 / 3
Completeness	It clearly states what the skill covers, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	It includes some relevant natural terms ('OTel registration', 'provider lifecycle'), but relies heavily on internal jargon ('phoenix-otel TypeScript package', 'stack-based global provider management') and lacks common user-facing variations a person would actually say.	2 / 3
Distinctiveness Conflict Risk	The package-specific framing ('phoenix-otel TypeScript package', 'stack-based global provider management') carves out a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: Arize-ai/phoenix
Commit: 27a4ecc

Reviewed: 4 days 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.