CtrlK
BlogDocsLog inGet started
Tessl Logo

phoenix-rest-api

REST API development for Phoenix. Use when adding, modifying, or reviewing endpoints in src/phoenix/server/api/routers/v1/.

73

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An efficient, well-structured skill body: concise overview, actionable checklist with validation steps, and one-level-deep references that all resolve to real files. Exemplifies progressive disclosure for a multi-step workflow.

DimensionReasoningScore

Conciseness

Lean ~19-line overview with no conceptual padding; it assumes Claude's competence and defers detail to references, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Provides concrete executable commands ('make openapi', 'make lint-python') and exact helper names plus path-format conventions, giving copy-paste-ready guidance rather than abstract direction.

3 / 3

Workflow Clarity

A numbered pre-commit checklist with explicit sequence and verification checkpoints (regenerate via 'make openapi', then 'make lint-python'), matching the anchor for clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

Clear overview with a well-signaled one-level-deep reference table; all three referenced files (endpoint-patterns.md, openapi-codegen.md, testing-patterns.md) exist and are appropriately split from the overview.

3 / 3

Total

12

/

12

Passed

Description

85%

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 tight, well-scoped description that pairs concrete actions with an explicit 'Use when' trigger and a disambiguating path. Slightly narrower trigger-term coverage keeps it just short of perfect.

DimensionReasoningScore

Specificity

Names concrete actions — 'adding, modifying, or reviewing endpoints' — within a specific domain (REST API development for Phoenix), matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('REST API development for Phoenix') and when ('Use when adding, modifying, or reviewing endpoints'), satisfying the anchor for clearly answering both with explicit triggers.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('endpoints', 'REST API', 'adding, modifying, or reviewing') but lacks broader common variations a user might say, so it sits at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

Scoped to a concrete path 'src/phoenix/server/api/routers/v1/', giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Arize-ai/phoenix
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.