CtrlK
BlogDocsLog inGet started
Tessl Logo

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

52

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

27%

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

The body is verbose and monolithic: a large embedded persona/config YAML plus three redundant command listings crowd the SKILL.md, and there are no external bundle files to offload detail. Actionability and workflow sequencing are present but weakened by abstract protocol language and placeholder logic.

Suggestions

Collapse the redundant command listings into one source of truth and move the full persona/config YAML into a referenced file under references/ so SKILL.md stays a lean overview.

Replace abstract activation directives ('adopt the persona', 'display greeting') with concrete, copy-paste-ready instructions or examples.

Trim the branching placeholder logic in the activation protocol to the essential sequenced steps, and add explicit validation checkpoints where any command has side effects.

DimensionReasoningScore

Conciseness

The body is padded with a large inline persona/config YAML block and triple-redundant command listings (Star Commands table, YAML commands, Quick Commands), restating things Claude already knows.

1 / 3

Actionability

Named commands with `*` prefixes, args, and a typical-workflow section give some concrete guidance, but much of the activation protocol is abstract ('adopt the persona', 'display greeting') with placeholders rather than executable instruction.

2 / 3

Workflow Clarity

Activation steps are numbered and sequenced, but the multi-step activation is over-specified with branching placeholder logic and lacks explicit validation checkpoints for the operations it drives.

2 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the entire agent configuration is inlined as one monolithic YAML block, so content that should be split into referenced files is instead inline.

1 / 3

Total

6

/

12

Passed

Description

85%

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 is specific and complete, clearly routing to the analyst persona with explicit trigger conditions and 'not for' guidance. The only weak spot is the slightly unnatural trigger phrasing ('asks to analyst') and limited natural keyword variation.

Suggestions

Reword 'asks to analyst' into natural phrasing such as 'asks for analyst help' or 'asks to do market research / competitor analysis' to broaden natural keyword coverage.

Add a few more concrete trigger verbs users would say (e.g. 'analyze the market', 'brainstorm ideas', 'research competitors') to lift trigger term quality to the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies', matching the highest anchor.

3 / 3

Completeness

Explicitly answers both what it does and when to use it via 'Use for ...', 'NOT for ...', and an explicit 'Trigger when ...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

Includes some natural triggers ('activate analyst', 'switch to analyst', '@analyst') but the phrase 'asks to analyst' is awkward and coverage of common natural variations is thin, so it is not the level above.

2 / 3

Distinctiveness Conflict Risk

A clear business-analyst/research niche is set off by a 'NOT for' routing clause and the distinct '@analyst' trigger, making conflicts unlikely.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.