phoenix-rest-api

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

Quality

80%

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 ./.agents/skills/phoenix-rest-api/SKILL.md

Quality

Content

93%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 content is an exemplar of lean, actionable skill writing: concrete commands, exact identifiers, and a clear pre-commit checklist with well-signaled references. The only gap is the absence of an explicit test-run step in the commit checklist.

Suggestions

Add an explicit 'run the integration tests' step (e.g. the relevant make target) to the pre-commit checklist so endpoint changes are validated before commit, not just linted.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no preamble explaining Phoenix or REST, every line is a concrete directive, and detail is appropriately pushed to references.	5 / 5
Actionability	It gives exact commands ('make openapi', 'make lint-python'), precise file paths and identifier names (_COMMON_RESOURCE_ENDPOINTS, _VIEWER_BLOCKED_WRITE_OPERATIONS), and concrete path-param conventions (fake-id-{}, test-tag), all of which are copy-paste ready.	5 / 5
Workflow Clarity	The numbered pre-commit checklist is a clear sequence and includes a lint validation checkpoint, but it omits an explicit run-the-tests step for endpoint changes, leaving a minor validation gap below the 5 anchor.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to three one-level-deep references via a clean Reference\|When table, all of which are real files in references/, so navigation is easy and content is appropriately split.	5 / 5
	Total	19 / 20 Passed

Description

66%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 concise, third-person, and clearly answers when to use it with concrete triggers and a scoping path. Its main weakness is a generic 'what' statement and a lack of common synonym trigger terms like 'routes' or 'router'.

Suggestions

Make the 'what' concrete by naming specific capabilities, e.g. 'Designs, implements, and reviews REST endpoints in the Phoenix v1 router.'

Add natural synonyms a user might say, such as 'routes', 'router', or 'API handlers', alongside 'endpoints'.

Consider noting the OpenAPI codegen and integration-test coverage tasks in the description so the skill's full scope is discoverable from the frontmatter alone.

Dimension	Reasoning	Score
Specificity	It names the domain ('REST API development for Phoenix') and three concrete actions ('adding, modifying, or reviewing endpoints'), but the actions are all variations of endpoint work rather than a comprehensive set of distinct capabilities, so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	It has both a 'what' and an explicit 'when' clause with concrete trigger phrases and even a path, but the 'what' ('REST API development') is a generic category rather than a concrete capability list, keeping it below the 5 anchor.	4 / 5
Trigger Term Quality	It includes relevant natural keywords ('endpoints', 'REST API', 'Phoenix') tied to clear action verbs, but misses common Phoenix-ecosystem synonyms a user might say such as 'routes', 'router', or 'controllers'.	3 / 5
Distinctiveness Conflict Risk	The Phoenix scope plus the explicit path 'src/phoenix/server/api/routers/v1/' carves out a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .agents/skills/phoenix-rest-api/SKILL.md
Commit: e127482

Reviewed: 6 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.