phoenix-cli-development

Design and implementation guide for the Phoenix CLI (`px`). Covers the noun-verb command structure, dual-audience design (humans and coding agents), Commander.js patterns, configuration resolution, output formats, exit codes, and conventions for adding or modifying commands. Triggers when working on phoenix-cli commands — adding new commands, modifying existing ones, refactoring command structure, or reviewing CLI code. Also triggers on mentions of `px` commands, CLI design, or adding a new resource to the CLI.

2.25x

Quality

—

Does it follow best practices?

Impact

99%

2.25x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

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

The body is highly actionable with concrete code, a sequenced validation-backed checklist, and clear workflow structure. Its weaknesses are token efficiency (re-explains basic TS/pnpm concepts) and progressive disclosure (a long monolithic file with no reference files to split out detail).

Suggestions

Trim the Naming Conventions and Build and Run sections to assume Claude's knowledge of standard TypeScript casing and pnpm scripts, keeping only Phoenix-specific deviations.

Move the full verb table, exit-code reference, and StructuredError shape into a separate reference file (e.g. references/conventions.md) and link to it from SKILL.md so the main body stays a concise overview.

Collapse the migration/backward-compatibility detail into a short pointer unless a migration is actively in progress, to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and instructional, but re-explains concepts Claude already knows — e.g. the "Naming Conventions" section restates standard camelCase/PascalCase/SCREAMING_SNAKE_CASE rules, and "Build and Run" glosses `pnpm build`/`pnpm dev` basics — so it could be tightened rather than earning the lean score-3 anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance: concrete `px ...` commands, TypeScript interfaces (CommonOptions, InteractiveCommandOptions, StructuredError), the exit-code table, and an 18-step implementation checklist with specific file paths.	3 / 3
Workflow Clarity	The checklist is a clearly sequenced process with explicit validation checkpoints and feedback loops ("Run `pnpm test` — fix any failures before proceeding", "Run `pnpm build` — fix any type errors before proceeding", manual verification with `--format raw --no-input`), matching the score-3 anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headings, but the ~295-line body is a single monolithic file with no bundle/reference files to offload detail; content that could be split (e.g. the full verb table, naming conventions) is inline rather than in one-level-deep reference files.	2 / 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.

The description clearly states what the skill covers and gives explicit, natural-language triggers tied to a distinct, named tool. Voice is appropriately third person with no first/second-person phrasing to penalize.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete areas — "noun-verb command structure, dual-audience design (humans and coding agents), Commander.js patterns, configuration resolution, output formats, exit codes, and conventions for adding or modifying commands" — matching the score-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Design and implementation guide for the Phoenix CLI (`px`). Covers...") and when ("Triggers when working on phoenix-cli commands... Also triggers on mentions of `px` commands..."), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — "adding new commands, modifying existing ones, refactoring command structure, or reviewing CLI code" plus "`px` commands, CLI design, or adding a new resource" — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Targets a specific named tool ("Phoenix CLI (`px`)") with distinct, tool-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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.