aiox-analyst

Activate Atlas (analyst) for Business Analyst. Use for market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies, industry trends analysis, project discov...

1.87x

Quality

55%

Does it follow best practices?

Impact

92%

1.87x

Average score across 2 eval scenarios

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/AIOX/agents/analyst/SKILL.md

Quality

Content

38%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 content is a monolithic, heavily-padded agent-persona definition: a large inline YAML block stuffed with persona flavor, redundant directives, and references to unbundled external files, with concrete activation steps but no bundled execution detail for the actual analysis work.

Suggestions

Move the large inline YAML agent definition into a separate bundled reference file and keep SKILL.md as a lean overview with a clear pointer to it.

Trim persona padding (zodiac, Portuguese vocabulary, multiple greeting levels) and consolidate the repeated "do not load other agent files" directives into a single statement.

Either bundle the referenced task/template files (facilitate-brainstorming-session.md, etc.) under references/ or replace the dangling .aiox-core/ references with self-contained, actionable guidance.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: a ~194-line inline YAML block carries persona fluff Claude does not need (zodiac "♏ Scorpio", Portuguese vocabulary lists, multiple greeting levels) and several capitalized directives ("CRITICAL", "MANDATORY", "DO NOT", "IMPORTANT") repeat the same idea (do not load other agent files) multiple times.	2 / 5
Actionability	Activation greeting steps and the command list are concrete, but the substantive analysis work delegates to external task/template files (e.g., facilitate-brainstorming-session.md, create-deep-research-prompt.md) that are not bundled with the skill, leaving key execution details unavailable.	3 / 5
Workflow Clarity	Activation is clearly sequenced (STEP 1-5 with a HALT checkpoint and a greenfield guard), but the "Typical Workflow" is a shallow four-step list with no validation or verification checkpoints; the work is non-destructive so the hard cap does not apply, but checkpoints remain implicit.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), yet the body inlines a large YAML agent-definition block that clearly belongs in separate files, and its dependency references point to an external .aiox-core/ tree that is not part of this skill bundle, so navigation leads nowhere.	2 / 5
	Total	10 / 20 Passed

Description

71%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 gives strong trigger guidance and a broad list of analyst use-cases, but it is literally truncated mid-word, states the "what" only indirectly via persona-activation phrasing, and lacks the boundary clauses needed to distinguish it from sibling PM/PO/SM skills.

Suggestions

Complete the truncated description (it ends at "project discov...") so the full capability and trigger list is present.

Lead with a crisp third-person capability statement (e.g., "Conducts market research, competitive analysis, and structured brainstorming facilitation") before the "Use for ..." triggers.

Add a brief "NOT for ..." boundary clause (PRD creation, architecture, story planning) directly in the description to reduce overlap with PM/architect/SM skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete analyst activities ("market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies, industry trends analysis"), but they are use-case domains rather than verb-form actions and the description is truncated ("project discov..."), leaving minor coverage gaps that keep it below a 5.	4 / 5
Completeness	An explicit "Use for ..." clause provides concrete trigger guidance (so not capped at 3), and the use-for list conveys what the skill does; however the "what" is indirect persona-activation phrasing ("Activate Atlas (analyst) for Business Analyst") rather than a crisp capability statement, and the truncation weakens it slightly.	4 / 5
Trigger Term Quality	Includes natural phrases a user would say ("market research", "competitive analysis", "brainstorm", "feasibility studies") with good coverage, though a few synonyms and variations are missing and the truncated tail drops coverage below 5.	4 / 5
Distinctiveness Conflict Risk	The research/analyst niche is somewhat specific, but the description omits the boundary ("NOT for") clauses that appear only in the body, leaving real overlap risk with the related PM/PO/SM skills the file itself routes to.	3 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

Reviewed: 4 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.