aiox-pm

Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roadmap planning, business case development, go/n... Triggers: PRD, create epic, execute-epic, roadmap, product strategy, pm, @pm, requirements...

Quality

78%

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 ./.grok/skills/aiox-pm/SKILL.md

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.

The body is a tight, well-structured persona-activation protocol with executable registration steps and clear sectioning. Its main weakness is that the actual PM methodology lives in external files, so inline actionability for the substantive work is limited to routing.

Suggestions

Add a brief inline validation step after registration (e.g. `cat .aiox/active-agent` to confirm) to close the workflow-clarity checkpoint gap.

Include a short inline sketch of one core task (e.g. the PRD creation steps or a minimal epic template) so the skill is actionable without immediately jumping to an external file.

Collapse the fallback source-of-truth chain (`.grok` -> `.aiox-core` -> `.codex`) into a single canonical path with a one-line fallback note to reduce navigation ambiguity.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a numbered protocol, a bash block, a starter-command list, and terse authority/non-negotiables sections with no concept padding or over-explanation.	5 / 5
Actionability	Provides copy-paste-ready bash for agent registration and concrete starter commands, but the substantive PM work (PRD/epic authoring) is delegated to external files rather than given inline, leaving a gap in executable guidance for the core task.	4 / 5
Workflow Clarity	A clear 7-step activation sequence is present, but there are no explicit validation checkpoints (e.g. confirming the active-agent files were written); this is acceptable since the operation is non-destructive, so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep references to source-of-truth files (`.aiox-core/development/agents/pm.md`, constitution, tasks dir); the multiple fallback paths slightly complicate navigation but references are clearly signaled.	4 / 5
	Total	17 / 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.

The description clearly establishes a PM persona with concrete capabilities and an explicit trigger list, but it is marred by literal "..." truncations ("go/n...", "requirements...") that cut off the capability and trigger lists mid-phrase. Voice and trigger guidance are otherwise sound.

Suggestions

Complete the truncated capability list (replace "go/n..." with the full phrase, e.g. "go/no-go decisions") and remove the trailing "..." from the Triggers list.

Add common synonyms to the trigger list such as "user story", "spec", "backlog", and "stakeholder requirements" to broaden natural-term coverage.

Add an explicit "Use when..." clause framing the triggers as user-facing scenarios rather than only a bare keyword list.

Dimension	Reasoning	Score
Specificity	Lists several concrete PM actions ("PRD creation (greenfield and brownfield)", "epic creation and management", "feature prioritization (MoSCoW, RICE)", "roadmap planning", "business case development"), but the literal "go/n..." and "requirements..." truncation leaves minor coverage gaps.	4 / 5
Completeness	Answers both what ("Use for PRD creation...") and when (explicit "Triggers:" clause), satisfying the trigger-guidance requirement, but the trailing ellipses make both halves feel cut off rather than fully concrete.	4 / 5
Trigger Term Quality	Good natural keyword coverage in the explicit Triggers list ("PRD, create epic, execute-epic, roadmap, product strategy, pm, @pm, requirements"), though common synonyms like user story, spec, or backlog are missing and the list is truncated.	4 / 5
Distinctiveness Conflict Risk	The Product Manager niche with PRD/epic/roadmap triggers is mostly distinct from other skills, with only minor overlap risk against generic planning or strategy 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
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
Path: .grok/skills/aiox-pm/SKILL.md
Commit: 4ef6530

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