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.
89
96%
Does it follow best practices?
Impact
100%
1.47xAverage score across 2 eval scenarios
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The spec explicitly names --api-key as a CLI flag/option (and includes apiKey in shared option shapes) while requiring flags to be used on the verb and forbidding handlers from reading env vars directly, which encourages agents to supply secrets as command-line arguments (i.e., verbatim in generated commands), creating an exfiltration risk.
- Repository
- Arize-ai/phoenix
- Commit
d9421a4
- Audited
- Security analysis
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.