aiox-analyst

Business Analyst (Atlas). Use for market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies, industry trends analysis, project discovery (br... Triggers: market research, competitive analysis, brainstorm, analyst, @analyst, feasibilit...

Quality

82%

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

76%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 concise, well-structured activation skill with executable registration code and clear delegation to external persona/task files. Its main gap is the absence of validation checkpoints for the state-file writes in the registration workflow.

Suggestions

Add an explicit validation checkpoint after the registration writes (e.g. verify .aiox/active-agent contains 'analyst' and .aiox/active-agent.json parses) before proceeding to load the persona.

Inline one or two concrete examples of the analyst workflows (e.g. a minimal *perform-market-research outline) so the skill is actionable without requiring the external task files to be present.

Confirm the referenced external paths (.aiox-core/development/agents/analyst.md, .grok/agents/aiox-analyst.md) exist in the bundle or note that they are environment-supplied, to keep the one-level-deep references trustworthy.

Dimension	Reasoning	Score
Conciseness	A lean activation protocol with terse numbered steps, a compact starter-command list, and an authority snapshot; no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Step 1 provides fully executable copy-paste bash (mkdir, printf with date, export) and starter commands are concrete, but the substantive analyst workflows are delegated to external task files rather than shown inline.	4 / 5
Workflow Clarity	The register → load → adopt → greet → stay sequence is clear, but the registration step writes three state files with no validation checkpoint confirming the writes succeeded, capping clarity at 3.	3 / 5
Progressive Disclosure	Well-organized sections with one-level-deep references to external sources of truth (agent profile, task files) and a stated fallback; content is appropriately split, though references are repo paths rather than a bundled reference set.	4 / 5
	Total	16 / 20 Passed

Description

88%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 strong, concrete description that clearly states capabilities and explicit trigger guidance with natural keywords. Minor room to broaden trigger synonyms, but it cleanly answers what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete analyst actions — market research, competitive analysis, user research, brainstorm facilitation, structured ideation workshops, feasibility studies, industry trends analysis, project discovery — giving comprehensive domain coverage.	5 / 5
Completeness	Explicitly answers both 'what' (Business Analyst for the listed analyses) and 'when' ('Use for...', 'Triggers:...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms are present (market research, competitive analysis, brainstorm, analyst, @analyst, feasibility, project brief) including the @analyst invocation, but common synonyms and variations are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	The Business Analyst niche with specific triggers (brainstorm facilitation, feasibility studies) is mostly distinct from sibling dev/data/devops agents, with only minor overlap risk against generic research skills.	4 / 5
	Total	18 / 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-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.