CtrlK
BlogDocsLog inGet started
Tessl Logo

phoenix-observability

Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.

70

Quality

86%

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

72%

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

A comprehensive, highly actionable reference with executable examples and clean progressive disclosure into two real one-level reference files. Its main weaknesses are duplicated instrumentation examples that hurt token efficiency and the absence of explicit validation checkpoints in the deployment/evaluation workflows.

Suggestions

Remove the duplicated OpenAI instrumentation example in the Framework instrumentation section (it already appears in Basic tracing) or collapse the four near-identical framework blocks into one parameterized pattern plus a short per-framework table.

Add an explicit validation checkpoint after launching the server (e.g., curl the /v1/traces endpoint or check session.url) and after running evaluations (verify eval_results is non-empty before client.log_evaluations).

Tighten minor explanatory prose such as 'A trace represents a complete execution flow...' and 'All OpenAI calls are now traced' that restates concepts Claude already knows.

DimensionReasoningScore

Conciseness

Mostly efficient code-focused content, but the OpenAI instrumentation block is duplicated (Quick start vs Framework instrumentation) and the register+instrument three-line pattern repeats verbatim across four frameworks, so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready executable code throughout — pip installs, phoenix serve/docker commands, OTel registration, evaluators, datasets, and experiments — with specific, complete examples.

3 / 3

Workflow Clarity

Sections follow a sensible topical sequence (install → launch → trace → evaluate → deploy) but lack explicit validation checkpoints or feedback loops; the Common issues section offers ad-hoc recovery rather than a sequenced validate-then-proceed flow.

2 / 3

Progressive Disclosure

SKILL.md is a well-organized overview with two clearly signaled, one-level-deep references (advanced-usage.md, troubleshooting.md) that both exist as real files and do not nest further; content is appropriately split.

3 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that concisely names concrete capabilities and provides explicit 'Use when' triggers covering debugging, evaluation, and monitoring scenarios. It matches the top anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'LLM tracing, evaluation, and monitoring', 'debugging LLM applications with detailed traces', 'running evaluations on datasets', 'monitoring production AI systems' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly states what it does (observability platform for tracing/evaluation/monitoring) and when to use it via a clear 'Use when...' clause with three concrete triggers.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('debugging LLM applications', 'running evaluations on datasets', 'monitoring production AI systems', 'LLM tracing') with good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (open-source AI/LLM observability) with distinct triggers unlikely to collide with general-purpose skills; written in third person.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
synthetic-sciences/openscience
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.