Leooooooow Analytics Hub
What this skill solves
Route the request to the right analytics path before doing the work.
Use when
- The user asks for ecommerce analytics but the exact analysis type is unclear
- The user wants a single entry point for multiple data questions
- The user needs help choosing between sales, creator, product, customer, logistics, or financial analysis
Do not use when
- The request already clearly matches a specialized analytics skill
- The user only wants a one-off raw file read
- The task is unrelated to ecommerce data
Inputs to ask for
Ask only for the minimum needed:
- What they want to know
- Time period
- Any focus area, if they already have one
Workflow
- Clarify the business question.
- Identify the best matching sub-skill.
- Pull the relevant source files.
- Run the specialized analysis.
- Return a concise decision summary.
Output requirements
Always include:
- The selected analysis path
- The core result
- The most important supporting metrics
- The recommended next action
Quality standards
- Choose the narrowest useful analysis path
- Avoid duplicate reporting across skills
- Keep the routing decision obvious
Safety / constraints
- Do not force the user through unnecessary clarifying steps
- Do not invent a sub-skill result if the analysis was not run