CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-master

Activate Orion (aiox-master) for AIOX Master Orchestrator & Framework Developer. Use when you need comprehensive expertise across all domains, framework component creation/modification, workflow orchestration, or running tasks that don't...

40

Quality

40%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/AIOX/agents/aiox-master/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

25%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 skill body is a monolithic inlined agent configuration plus a thin guide, with heavy verbosity, no executable guidance, and poor separation of concerns. It functions as a configuration dump rather than an overview pointing to well-organized supporting materials.

Suggestions

Move the full agent YAML, dependency lists, and command catalog into reference files (e.g., references/agent-config.yaml, references/commands.md) and keep SKILL.md a concise overview with one-level-deep links.

Add concrete, executable examples for the key operations (e.g., a sample `*create agent` invocation and the expected file path it produces).

Add explicit validation checkpoints to the framework-modification workflow (e.g., 'run *validate-component after *modify') so destructive/batch operations have feedback loops.

DimensionReasoningScore

Conciseness

The body inlines an entire ~370-line YAML agent configuration (persona, vocabulary, commands, dependencies, security) that explains concepts and config Claude does not need restated; this is noticeably verbose and padded.

2 / 5

Actionability

Guidance is high-level and declarative (command names, persona rules, 'validate all generated code') with no executable code or concrete steps; it describes behavior rather than instructing how to execute it.

2 / 5

Workflow Clarity

The activation steps are sequenced, but the command catalog and task/delegation workflows lack checkpoints and validation for operations that modify framework components, and the greenfield/branch logic is buried rather than clearly gated.

2 / 5

Progressive Disclosure

Content that clearly belongs in separate files (full agent YAML, dependency listings, command catalog) is inlined into SKILL.md; no bundle files exist in references/scripts/assets, and references to external paths like .aiox-core are not navigable from the skill.

2 / 5

Total

8

/

20

Passed

Description

55%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 includes the required 'what' and 'Use when' structure but leans on vague superlatives ('comprehensive expertise across all domains') and abstract triggers rather than concrete, distinctive capabilities. It is truncated, which weakens both trigger quality and completeness.

Suggestions

Replace 'comprehensive expertise across all domains' with concrete capabilities (e.g., 'create and modify AIOX agents, tasks, and workflows; orchestrate multi-agent workflows').

Add natural user-facing trigger phrases such as 'create an agent', 'modify a workflow', 'orchestrate a multi-agent task', and 'check the IDS registry'.

Narrow the scope so it does not claim to cover 'all domains' — this overlaps with every specialized agent and risks triggering for the wrong skill.

DimensionReasoningScore

Specificity

Names the domain ('AIOX Master Orchestrator & Framework Developer') and 1-2 concrete actions ('framework component creation/modification', 'workflow orchestration'), but 'comprehensive expertise across all domains' is generic filler that pads rather than specifies.

3 / 5

Completeness

It has both a 'what' (Orchestrator & Framework Developer persona) and an explicit 'Use when...' trigger clause, though the when-clause is somewhat broad and the sentence is truncated.

4 / 5

Trigger Term Quality

'framework component creation/modification' and 'workflow orchestration' are relevant but abstract; it lacks the natural, concrete phrases or synonyms a user would actually say, and 'running tasks that don't...' is cut off.

3 / 5

Distinctiveness Conflict Risk

'comprehensive expertise across all domains' is extremely broad and would overlap with virtually any specialized agent, creating high conflict risk despite the niche-sounding title.

2 / 5

Total

12

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (514 lines); consider splitting into references/ and linking

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.