CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-analytics

AI-powered analytics with Luzmo - /aiprompt API, saved Agents, Rules, AI context, and IQ embed components. Use for natural language data queries, chart or dashboard generation, agentic workflows (agent analyst|item|dashboard, or a saved agent_id), IQ Chat/Answer embedding (luzmo-iq-embed-chat, LuzmoIQChatComponent), published Rules, ai_context / business knowledge, "AI not working", wrong answers, quality optimization. Requires AI/IQ addon license. Use eagerly for any natural-language analytics feature, saved Agent, Rule, or AI-context task. Not for standard chart embedding (use core for saved dashboards, data-visualization for Flex) or React Native (IQ embed components are web-only).

75

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 strong router-style skill body: concrete request shapes, explicit security validation, clean path-based navigation, and verified one-level-deep references. Its main weakness is redundancy — component tables, the React Native warning, dataset-scoping advice, and doc URL lists are each repeated several times, inflating token cost without adding information.

Suggestions

State the IQ component names once (the Core Principles table) and have Path A/B reference it, or keep the tables only in the paths and drop the duplicate — currently the same table appears three times.

Mention the React Native limitation and the theme_id-not-applied caveat once each (e.g., in Core Principles/Avoid) instead of repeating them across four sections.

Drop the per-path doc URL blocks in favor of the consolidated Canonical Sources section (or vice versa) — most URLs currently appear twice in the file.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining known concepts, but it repeats the same facts many times: the IQ component-names table appears three times (Core Principles, Path A, Path B), the React Native limitation four times, the 'scope to 5–10 datasets' rule about four times, the theme_id-not-applied note four times, and the Canonical Sources section re-lists most per-path doc URLs. This fits the 'mostly efficient but could be tightened' anchor; the duplication is more than the 'minor instances' of the anchor at 4.

3 / 5

Actionability

Fully actionable: an executable /aiprompt request body, exact endpoints and regional hosts, per-framework component names, an agent×task matrix, streaming event order, and a troubleshooting table mapping each symptom to a concrete fix. Deferring full payload shapes to the canonical API doc is a deliberate, signaled disclosure choice, not a gap.

5 / 5

Workflow Clarity

The 'Choose the Right Path' table routes every goal to a concrete path, the [CRITICAL] Security Checkpoint is an explicit validation checklist with a 'STOP and fix before proceeding' gate, Path D gives numbered steps, and the Common IQ Issues table supplies error→fix feedback loops. Multi-step work is clearly sequenced with real checkpoints.

5 / 5

Progressive Disclosure

A Bundled References section summarizes each reference file in one line, every path points to its own reference (saved-agents, data-modeling-for-iq, agentic-integration, mcp-server), and all four reference files exist, are substantive (100–180 lines each), and are exactly one level deep. Structure matches the clear-overview anchor.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete capabilities with exact API and component identifiers, explicit use/eager-use triggers including user-voiced failure phrases, a clear license prerequisite, and explicit boundary guidance against neighboring skills. Voice is consistent with the third-person convention and there is no padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'natural language data queries, chart or dashboard generation, agentic workflows', 'IQ Chat/Answer embedding' — anchored by exact API and component names ('/aiprompt API', 'luzmo-iq-embed-chat', 'LuzmoIQChatComponent', 'agent_id'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Both what ('AI-powered analytics with Luzmo - /aiprompt API, saved Agents, Rules, AI context, and IQ embed components') and when ('Use for natural language data queries... Use eagerly for any natural-language analytics feature, saved Agent, Rule, or AI-context task') are explicitly and concretely stated, with an explicit not-for clause as well.

5 / 5

Trigger Term Quality

It covers natural user phrasings comprehensively, including error-state triggers users would actually say ('"AI not working"', 'wrong answers'), synonyms ('ai_context / business knowledge'), and specific technical identifiers. No common variation of how a user would request this skill is missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear Luzmo-specific niche and preempts conflicts with sibling skills via explicit exclusions ('Not for standard chart embedding (use core for saved dashboards, data-visualization for Flex) or React Native'), so mis-triggering risk is minimal.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

luzmo-official/agent-skills

Path

skills/ai-analytics/SKILL.md

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.