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/.

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/phoenix-rest-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A tight, well-structured skill body that delivers executable commands, a validation-backed workflow, and clean one-level-deep references. Only minor actionability polish (an example test line) would push it higher.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; every line (commands, file paths, path-param formats, reference table) earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides concrete executable commands ('make openapi', 'make lint-python') with specific file paths and path-param conventions; minor gap is the absence of an example test fixture line.

4 / 5

Workflow Clarity

Clear numbered sequence with an explicit validation checkpoint ('make lint-python' — fix errors before committing) and feedback guidance for the endpoint-list categorization step.

5 / 5

Progressive Disclosure

Overview body is concise and points to three well-signaled, one-level-deep references via a clear 'When' table; all referenced files (endpoint-patterns.md, openapi-codegen.md, testing-patterns.md) exist.

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.

A focused, third-person description with a clear 'Use when' trigger and a precise path that sharply distinguishes it from other skills. It is slightly light on natural trigger-term variations and comprehensive action coverage.

Suggestions

Add common natural trigger terms users would say, e.g. 'routes', 'API handlers', or 'controllers', to broaden match likelihood.

Expand the action list slightly to be more comprehensive (e.g. mention schema generation or versioning alongside adding/modifying/reviewing).

DimensionReasoningScore

Specificity

Names the domain (Phoenix REST API) and concrete actions ('adding, modifying, or reviewing endpoints'), but the action list is narrow and not comprehensive.

3 / 5

Completeness

Explicitly states both what ('REST API development for Phoenix') and when ('Use when adding, modifying, or reviewing endpoints in ...'), though the 'when' could be more specific about non-endpoint triggers.

4 / 5

Trigger Term Quality

'REST API development' and 'endpoints' are relevant terms, but common natural variations users might say (e.g., 'routes', 'API handlers', 'controllers') are missing.

3 / 5

Distinctiveness Conflict Risk

The exact path 'src/phoenix/server/api/routers/v1/' pins it to a clear niche with minimal risk of triggering for unrelated skills.

5 / 5

Total

15

/

20

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.