aiox-analyst

Business Analyst (Atlas). Use for market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies, i...

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 ./.codex/skills/aiox-analyst/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.

A lean, well-structured persona-activator body that provides concrete activation commands and a clear starter command list while pushing detail to a source-of-truth file. It is maximally concise and reasonably actionable, with only minor gaps in workflow checkpoints and unverifiable external references.

Suggestions

Add a one-line validation/confirmation checkpoint after the greeting step (e.g. "Confirm the persona is active before accepting commands") to strengthen the workflow.

Verify the referenced paths (`.aiox-core/development/agents/analyst.md`, `.aiox-core/constitution.md`) exist and resolve relative to the skill location, or ship them as bundle files so progressive disclosure is self-contained.

Complete the truncated "When To Use" line (ending in "documentati...") so the trigger list is not cut off.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept-explaining padding — it jumps straight to activation steps, a command list, and constraints, assuming Claude's competence with every token earning its place.	5 / 5
Actionability	It gives concrete executable guidance ("node .aiox-core/development/scripts/generate-greeting.js analyst", file paths to load, and a starter command list), but the per-command workflows live in the referenced agent file rather than here, leaving minor gaps.	4 / 5
Workflow Clarity	The Activation Protocol is a clear numbered 4-step sequence with a concrete command, and no validation is required for this non-destructive persona switch, but there are no explicit checkpoints or feedback loops.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (When To Use, Activation Protocol, Starter Commands, Non-Negotiables) and signals a one-level-deep source-of-truth (analyst.md), though the referenced detail lives in external project files rather than bundle files and cannot be verified.	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.

A solid description with an explicit "Use for ..." trigger clause and a broad list of concrete analyst activities, but it relies on a role label for the "what" rather than enumerating capabilities and the text appears truncated ("i..."). The result is a consistent level-4 across dimensions.

Suggestions

Replace the "Business Analyst (Atlas)" role label with a concrete capability statement (e.g. "Conducts market research, competitive analyses, and structured brainstorming workshops") so the "what" is as explicit as the "when".

Complete the truncated description (ending in "i...") and add common synonyms such as "competitor analysis" and "ideation" to broaden trigger coverage.

Tighten distinctiveness by scoping triggers that might collide with UX-research or general ideation skills (e.g. "business-facing user research").

Dimension	Reasoning	Score
Specificity	Lists several concrete activities ("market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies") rather than vague language, though these read more as use-case domains than crisp technical actions, leaving minor gaps.	4 / 5
Completeness	It answers "what" ("Business Analyst (Atlas)") and "when" ("Use for ...") with concrete trigger phrases, but the "what" is a role label rather than a concrete capability list, so it stops short of the level-5 anchor.	4 / 5
Trigger Term Quality	Phrases like "market research", "competitive analysis", "user research", and "brainstorming" are natural terms users would say, giving good coverage, though a few synonyms (e.g. competitor analysis) are missing.	4 / 5
Distinctiveness Conflict Risk	The business-analysis niche with these triggers is mostly distinct, though "user research" and "brainstorming" could overlap with UX or general ideation skills, creating minor conflict risk.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SynkraAI/aiox-core
Path: .codex/skills/aiox-analyst/SKILL.md
Commit: 4ef6530

Reviewed: 1 day 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.