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.

1.47x

Quality

88%

Does it follow best practices?

Impact

99%

1.47x

Average score across 2 eval scenarios

Securityby

High

Do not use without reviewing

Quality

Content

85%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 highly actionable, well-sequenced design spec with concrete commands, code, and validation-backed workflows. Its main weakness is progressive disclosure: the full specification is inlined in SKILL.md with no referenced detail files.

Suggestions

Move the shared options-type table and exit-code reference into a bundled reference file (e.g. references/options.md, references/exit-codes.md) and link to them from SKILL.md so the main file reads as an overview.

Extract the testing-harness details (MSW setup, testUtils, captureCliOutput) into a references/testing.md linked from the Testing section to reduce inline length.

Trim a few illustrative command examples that duplicate information already conveyed by the verb/options tables to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Dense and mostly efficient — it assumes Claude's competence about Commander.js, RFC 2119, and TypeScript without padding — but a few illustrative examples and tables could be trimmed without losing guidance value.	4 / 5
Actionability	Provides copy-paste-ready commands (`px project create --name foo --format raw`), concrete file paths (`src/exitCodes.ts`, `src/io.ts`, `src/commands/options.ts`), real TypeScript interfaces, and exit-code tables covering the common cases.	5 / 5
Workflow Clarity	The 18-step 'Checklist for Adding a New Resource Command' has explicit validation checkpoints with feedback loops ('Run `pnpm test` — fix any failures before proceeding', 'Run `pnpm build` — fix any type errors before proceeding'), and the migration section adds a second sequenced workflow.	5 / 5
Progressive Disclosure	Well-organized with clear headers and tables, but the entire ~335-line specification lives inline in SKILL.md with no bundle files or one-level-deep references, so content that could be split (options reference, exit codes, testing harness) is not progressively disclosed.	3 / 5
	Total	17 / 20 Passed

Description

92%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 strong, specific description that clearly states what the skill covers and when it should trigger, tied to a distinct tool. Trigger-term coverage is good though slightly developer-oriented rather than exhaustively synonym-rich.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'noun-verb command structure, dual-audience design (humans and coding agents), Commander.js patterns, configuration resolution, output formats, exit codes' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' (a design and implementation guide covering the listed areas) and 'when' via two explicit 'Triggers when...' clauses with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ('adding new commands, modifying existing ones, refactoring command structure, or reviewing CLI code', 'mentions of `px` commands, CLI design') with the tool name `px`, though coverage leans developer-jargon-flavored rather than fully comprehensive synonyms.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific named tool (Phoenix CLI / `px`) with distinct triggers, giving it a clear niche and minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 20 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
Path: js/packages/phoenix-cli/.agents/skills/phoenix-cli-development/SKILL.md
Commit: 8adf337

Reviewed: 1 day 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.