aiox-po

Activate Pax (po) for Product Owner. Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions

Quality

65%

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 ./.claude/skills/AIOX/agents/po/SKILL.md

Quality

Content

56%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 body delivers actionable, well-sequenced PO guidance via named commands and a lifecycle workflow, but it is padded by an inlined persona YAML and duplicated command listings that hurt token efficiency and structure. Pulling the agent definition into a referenced file and de-duplicating the command list would lift both conciseness and progressive disclosure.

Suggestions

Move the inlined YAML agent definition (persona_profile, greeting_levels, vocabulary, zodiac) into a referenced config file and keep SKILL.md as a lean overview, removing the duplicated command listings across Quick Commands, Handoff Protocol, and the Guide.

Trim persona ceremony (zodiac, vocabulary, multiple greeting levels, GREENFIELD GUARD substeps) that does not earn tokens for actual capability.

Surface dependency file references (tasks/templates/checklists under .aiox-core/development/) as clearly signaled one-level-deep links in the overview instead of burying them inside the YAML block.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: an inlined ~200-line YAML agent definition carries persona fluff (zodiac, vocabulary, multiple greeting levels) and the command list is duplicated across the YAML, Quick Commands, Handoff Protocol, and the Guide sections.	2 / 5
Actionability	Commands are concrete and executable with prefixes and arguments (e.g., "backlog-prioritize {item} {priority}", "validate-story-draft {story}", "*sync-story {story-id}") and the Typical Workflow maps them into a runnable sequence, with only minor gaps where some commands lack args.	4 / 5
Workflow Clarity	The 7-step Typical Workflow is clearly sequenced with explicit START/END lifecycle checkpoints (validate-story-draft at start, close-story at end); no batch/destructive feedback-loop cap applies, though mid-process validation is only implicit.	4 / 5
Progressive Disclosure	Section headers provide some structure, but a large generated YAML agent definition (marked "Source: .aiox-core/development/agents/po.md") is inlined into SKILL.md and dependency file references are buried inside that YAML rather than clearly signaled in the overview.	3 / 5
	Total	13 / 20 Passed

Description

75%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 solid third-person description that names the PO domain and several concrete capabilities with an explicit "Use for" trigger clause. It would reach the top anchor by converting the artifact term into an action and adding common synonyms like "user stories".

Dimension	Reasoning	Score
Specificity	Lists several concrete PO activities — "backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions" — though "acceptance criteria" is an artifact rather than an action, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	Answers both what ("Activate Pax (po) for Product Owner") and when ("Use for backlog management...") with concrete trigger activities, but the "what" leans on the brand/persona name rather than crisply stating capability, so it is not a full 5.	4 / 5
Trigger Term Quality	Natural PO terms ("backlog management", "story refinement", "sprint planning", "prioritization") give good keyword coverage, but common synonyms like "user stories", "backlog grooming", or "writing stories" are absent.	4 / 5
Distinctiveness Conflict Risk	The Product Owner niche (backlog, acceptance criteria, sprint planning, prioritization) is mostly distinct, though the skill itself documents overlap/delegation to @sm and @pm, indicating minor conflict risk with closely related role skills.	4 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: SynkraAI/aiox-core
Path: .claude/skills/AIOX/agents/po/SKILL.md
Commit: 4ef6530

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