CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-analytics

AI-powered analytics with Luzmo - /aiprompt API, the universal agent, saved Agents, Rules, AI context, IQ embed components, and AI logs. Use for natural language data queries, chart or dashboard generation, agentic workflows (agent analyst|item|dashboard|auto, optionally with a saved agent_id), IQ Chat/Answer embedding (luzmo-iq-embed-chat, LuzmoIQChatComponent, agentId), IQ inside an embedded dashboard, published Rules, ai_context / business knowledge, Agent Logs / AILog API, "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 the Luzmo MCP server (use mcp), standard chart embedding (use core for saved dashboards, data-visualization for Flex), or React Native (IQ embed components are web-only).

Quality

97%

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

92%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 well-engineered reference skill: executable API examples, a hard security gate before implementation, destructive-operation safeguards, and a clean one-level reference bundle. Its only weakness is repetition — the embed-token scoping warning and the canonical-doc consultation reminder each recur more often than needed.

Suggestions

Consolidate the token-scoping guidance (Security Checkpoint, 'Auth and scoping', Path G, 'Avoid') into one canonical statement with a single cross-reference, since it currently appears in four places.

State the 'consult createAIPrompt.md before implementing' rule once (e.g., in Doc Retrieval) instead of repeating the URL ~8 times across Paths C, D, and the canonical-sources section.

DimensionReasoningScore

Conciseness

The body is dense and table-driven, assumes Claude's competence (no library/API primers), and pushes detail to references ("all quality guidance lives in references/data-modeling-for-iq.md"). However, token-scoping guidance is repeated in at least four places (Security Checkpoint, "Auth and scoping", Path G, "Avoid"), and "Consult https://developer.luzmo.com/api/createAIPrompt.md" appears ~8 times — trimming opportunities that keep it below the leanest anchor. It is well above the 'some unnecessary explanation' anchor 3.

4 / 5

Actionability

Guidance is copy-paste ready: a complete POST /aiprompt request with headers and JSON body, a full createAuthorization embed-token example with iq.context, per-framework component names in tables, streaming event order, region hosts, a fix table mapping each problem to exact tools (update_dataset_metadata, createFormula), and a legacy-migration table. Concrete examples cover the common cases for every path.

5 / 5

Workflow Clarity

The "Choose the Right Path" routing table sequences decision-making, the [CRITICAL] Security Checkpoint is an explicit pre-implementation checklist with a stop gate ("If ANY checkbox is unchecked, STOP and fix before proceeding"), and destructive operations carry validation warnings ("Read the current AI context before overwriting it", "Confirm before update_formula or delete_formula") with user-visible change review. The Common IQ Issues table provides error→cause→fix feedback loops for recovery.

5 / 5

Progressive Disclosure

All four cited bundle files exist and are one level deep, each introduced with a scope summary ("read only when relevant"); quality guidance and saved-Agent detail are deliberately split out of SKILL.md, and mcp-server.md is transparently labeled a pointer. Reference files cross-link siblings (agentic-integration ↔ saved-agents ↔ data-modeling-for-iq) at the same level, so navigation stays flat and easy.

5 / 5

Total

19

/

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 capability enumeration, natural trigger phrases including failure-mode phrasings ("AI not working", "wrong answers"), explicit positive and negative use guidance, and built-in disambiguation against sibling skills. Third-person/neutral voice throughout with no filler.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "natural language data queries, chart or dashboard generation, agentic workflows (agent analyst|item|dashboard|auto...)", "IQ Chat/Answer embedding (luzmo-iq-embed-chat, LuzmoIQChatComponent, agentId)", "Agent Logs / AILog API", "quality optimization" — with named APIs, components, and agents rather than generic language. Coverage spans the skill's full surface (queries, generation, embedding, agents, rules, context, logs, troubleshooting), matching the comprehensive-coverage anchor; it exceeds the 'several specific actions with minor gaps' anchor 4.

5 / 5

Completeness

The 'what' is explicit ("AI-powered analytics with Luzmo - /aiprompt API, the universal agent, saved Agents, Rules, AI context, IQ embed components, and AI logs") and the 'when' is explicit twice with concrete trigger phrases ("Use for natural language data queries..." and "Use eagerly for any natural-language analytics feature, saved Agent, Rule, or AI-context task"), plus negative scope ("Not for the Luzmo MCP server..."). This clearly matches the anchor requiring both what and when with concrete triggers.

5 / 5

Trigger Term Quality

It includes both natural user phrasings ("AI not working", "wrong answers", "natural language data queries", "business knowledge") and exact technical terms users would paste (luzmo-iq-embed-chat, LuzmoIQChatComponent, agentId, ai_context, AILog, agent_id), plus the synonym pairing "ai_context / business knowledge". This matches the comprehensive anchor including synonyms and specific identifiers; nothing common is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (Luzmo AI/IQ) and actively disambiguates against neighboring skills — "Not for the Luzmo MCP server (use mcp), standard chart embedding (use core for saved dashboards, data-visualization for Flex), or React Native" — minimizing wrong-skill triggering. Conflict risk is minimal, matching the clear-niche anchor.

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.