CtrlK
BlogDocsLog inGet started
Tessl Logo

aiox-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...

41

Quality

42%

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

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body functions as a verbose agent-configuration dump rather than a focused skill: it is heavy with persona flavor and an inline YAML block, offers command listings but few executable examples, and keeps most material inline instead of progressively disclosed.

Suggestions

Move the persona profile, commands, and dependencies YAML into a separate reference file and keep SKILL.md as a concise overview with one-level-deep links.

Cut non-instructional fluff (zodiac, Portuguese vocabulary, emoji frequency, archetypal greetings) that does not change Claude's behavior.

Add concrete, copy-paste-ready examples for the top operations (e.g., a sample `*create agent` invocation and the resulting file) instead of relying solely on command names.

DimensionReasoningScore

Conciseness

The ~500-line body is padded with content Claude does not need — persona zodiac ('♌ Leo'), Portuguese vocabulary, 'emoji_frequency', archetypal greeting strings, and a large inline YAML config block — far from lean.

1 / 3

Actionability

Commands are enumerated with names and descriptions and the activation steps give some concrete guidance, but there is no executable code or copy-paste examples for the core framework operations; real execution is deferred to unloaded dependency files.

2 / 3

Workflow Clarity

A 'Typical Workflow' section and numbered activation steps provide a sequence, but destructive/meta operations (component modify, deprecate) lack explicit validate-then-proceed checkpoints, and IDS hooks are advisory only.

2 / 3

Progressive Disclosure

Sections (Quick Commands, Agent Collaboration, Guide) give some structure, but the bulk of the content is a monolithic inline YAML config block that should live in separate files; no references/scripts/assets bundle exists to offload it.

2 / 3

Total

7

/

12

Passed

Description

50%

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 identifies a clear persona/domain and includes a 'Use when' trigger, but it is truncated mid-sentence and padded with generic phrasing ('across all domains') that weakens both completeness and distinctiveness.

Suggestions

Complete the truncated 'Use when' clause so the trigger guidance is explicit rather than ending in '...'.

Replace 'comprehensive expertise across all domains' with the concrete trigger terms users would actually say (e.g., 'create or modify AIOX agents, tasks, or workflows', 'orchestrate multi-agent workflows').

Tighten the 'what' statement to lead with the concrete capabilities instead of 'Activate Orion'.

DimensionReasoningScore

Specificity

Names the domain ('AIOX Master Orchestrator & Framework Developer') and some concrete actions ('framework component creation/modification', 'workflow orchestration'), but the clause 'comprehensive expertise across all domains' is vague and the final action is truncated ('running tasks that don't...').

2 / 3

Completeness

Both 'what' (activate the AIOX Master persona) and 'when' (Use when...) are present, but the 'when' clause is cut off mid-sentence with '...' so the trigger guidance is incomplete rather than fully explicit.

2 / 3

Trigger Term Quality

Includes 'Use when you need... framework component creation/modification, workflow orchestration' which are somewhat natural, but leans on jargon (AIOX, orchestration) and 'comprehensive expertise across all domains' is overly generic, missing common variations.

2 / 3

Distinctiveness Conflict Risk

'AIOX Master Orchestrator' and 'framework component creation/modification' carve a niche, but 'comprehensive expertise across all domains' is generic enough to overlap with other broad skills.

2 / 3

Total

8

/

12

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

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.