aiox-master

AIOX Master Orchestrator & Framework Developer (Orion). Use when you need comprehensive expertise across all domains, framework component creation/modification, workflow orchestration, or running tasks that don't require a specialized persona. Triggers: orchestrate, aiox-master, @aiox-master, framework governance, c...

Quality

84%

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

Quality

Content

88%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, executable activation protocol with concrete commands and clear sequencing — strong on conciseness and actionability. The main gaps are absent validation checkpoints in the workflow and reliance on external (non-bundled) file paths for source-of-truth content.

Suggestions

Add an explicit validation step after registration (e.g., verify .aiox/active-agent exists and contains 'aiox-master') so the activation workflow has a checkpoint.

Resolve the push/PR inconsistency between step 1 ('required before git push / PR') and the non-negotiable that only /aiox-devops may push — clarify which agent actually performs the push.

If the referenced sources of truth (.aiox-core, .codex profiles) are essential, consider bundling excerpts into ./references so the skill is self-contained and navigable.

Dimension	Reasoning	Score
Conciseness	The body is lean and protocol-driven: numbered steps, concrete file paths, and starter commands with no padding or re-explanation of concepts Claude already knows.	5 / 5
Actionability	Provides fully executable copy-paste bash (mkdir, printf, export), exact file paths for sources of truth, and a concrete starter-command list — directly runnable with no pseudocode.	5 / 5
Workflow Clarity	A clear 7-step activation sequence exists, but there are no validation/checkpoint steps and a mild inconsistency: step 1 frames registration as 'required before git push / PR' while the non-negotiables say only /aiox-devops may push or open PRs.	4 / 5
Progressive Disclosure	Content is well-sectioned and defers detail to one-level-deep sources of truth (.aiox-core and .codex agent profiles); however these are external repo paths rather than bundle files present in references/scripts/assets, and there is no explicit bundle to navigate.	4 / 5
	Total	18 / 20 Passed

Description

80%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 states what the skill does and when to use it, with explicit trigger terms — its strongest aspect. It is weakened by over-broad claims ('all domains', 'tasks that don't require a specialized persona') that raise conflict risk, and the description text appears truncated mid-word.

Suggestions

Remove or narrow 'comprehensive expertise across all domains' and 'running tasks that don't require a specialized persona' to concrete, scoped capabilities to reduce overlap with other skills.

Add natural-language user phrasings (e.g., 'orchestrate a workflow', 'create a new AIOX agent') alongside the internal trigger tokens so the triggers read like what a user would actually say.

Fix the truncated 'c...' tail of the description so it does not appear cut off mid-token.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('framework component creation/modification, workflow orchestration'), but 'comprehensive expertise across all domains' is broad padding rather than a concrete capability.	4 / 5
Completeness	Explicitly answers both what ('AIOX Master Orchestrator & Framework Developer') and when ('Use when you need comprehensive expertise...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes an explicit 'Use when...' clause plus a 'Triggers:' list ('orchestrate, aiox-master, @aiox-master, framework governance'), giving good keyword coverage, though many terms are internal jargon rather than natural user phrasing.	4 / 5
Distinctiveness Conflict Risk	The persona is named distinctly, but 'comprehensive expertise across all domains' and 'running tasks that don't require a specialized persona' are so broad they could overlap with virtually any other skill.	3 / 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-master/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.