CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-po

Product Owner (Pax). Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions Triggers: validate story, backlog, acceptance criteria, close story, po, @po, prioritize, story draft. Use when the user runs /aiox-po or @po.

66

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, operational activation skill that respects token budget and gives concrete executable steps. The main gaps are a missing explicit success-checkpoint after registration and a slightly confusing split between the persona-load path and the source-of-truth path.

Suggestions

Add an explicit validation step after registration (e.g., confirm .aiox/active-agent contains 'po' before proceeding).

Reconcile the persona-load path (.grok/agents/aiox-po.md) with the source-of-truth path (.aiox-core/development/agents/po.md) so it is clear which is canonical and which is fallback.

DimensionReasoningScore

Conciseness

Lean ~50-line body with no concept explanations; every line is operational and assumes Claude's competence, including a justified executable bash registration block.

5 / 5

Actionability

Provides an executable copy-paste bash registration block and concrete named starter commands, but persona-adoption and greeting steps remain descriptive rather than fully executable (greeting script is optional).

4 / 5

Workflow Clarity

A clear 7-step numbered Protocol sequence for non-destructive activation; no explicit checkpoint confirming registration succeeded, though the simple-skill exception means that gap is minor.

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep pointers to source-of-truth files; scored 4 rather than 5 because the persona path (.grok/agents/aiox-po.md) and source-of-truth path (.aiox-core/development/agents/po.md) diverge, and no local bundle files exist to verify references.

4 / 5

Total

17

/

20

Passed

Description

78%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, trigger-rich description that explicitly covers both capabilities and when-to-use conditions. The main weakness is voice: it uses imperative/second-person phrasing ('Use for...', 'Use when the user runs...') instead of the third-person voice the rubric expects.

Suggestions

Rewrite in third person to match the expected voice (e.g., 'Manages backlog, refines stories, drafts acceptance criteria...' instead of 'Use for backlog management...').

Expand trigger terms with a few more natural user phrasings (e.g., 'write acceptance criteria', 'groom the backlog', 'plan the sprint').

DimensionReasoningScore

Specificity

Lists several concrete PO actions ('backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions') but uses imperative 'Use for...' second-person voice rather than third person, triggering the rubric's -1 voice penalty from 4 to 3.

3 / 5

Completeness

Clearly answers both 'what' (the PO actions) and explicit 'when' with concrete triggers ('Triggers:' list plus 'Use when the user runs /aiox-po or @po').

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms and synonyms ('validate story, backlog, acceptance criteria, close story, po, @po, prioritize, story draft') plus slash-command triggers; a few natural phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Clear Product Owner niche with distinct triggers (@po, /aiox-po, close-story); mostly distinct with only minor overlap risk against other agile-related skills.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
SynkraAI/aiox-core
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.