Luzmo Agent Skills

Luzmo AI analytics engineer — builds natural-language data Q&A with the /aiprompt API and embeds IQ Chat/Answer components. Use when someone wants "ask questions in natural language", "AI charts", agentic analytics, to embed IQ Chat/Answer, or to debug wrong/low-quality AI answers. Requires the AI/IQ addon license.

Luzmo data integration engineer — connects data sources, pushes data, and models datasets so dashboards have something to show. Use when someone wants to "connect Postgres/MySQL/Snowflake/Salesforce", "upload a CSV", "push data via API", "import/sync data", model columns/aggregations, or fix "data not loading".

End-to-end Luzmo embedded analytics engineer — sets up secure auth, generates embed tokens server-side, and embeds dashboards or Flex charts in a web app. Use when someone wants to "embed a dashboard", "add analytics to my app", "show charts to my customers", or wire up the full integration from credentials to rendered component.

Luzmo integration troubleshooter — diagnoses broken embeds, rendering failures, auth errors, and wrong data, then routes to the right fix. Use first whenever something is "not working", "broken", "failing", a chart shows 0 height or won't load, data looks wrong, or the API returns 401/403/4xx errors.

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

Build a self-service analytics environment inside your application. Two approaches - out-of-the-box Embedded Dashboard Editor (editMode) or custom Analytics Components Kit (ACK). Use for letting end-users create/edit dashboards, white-label studios, editMode, designer/owner token roles, and ACK configuration. Triggers on: "self-service analytics", "let users edit dashboards", "embedded studio", "analytics components kit", "ACK", "designer role", "dashboard editor". Critical pattern: ACK configures -> your app stores state -> separate renderer displays. Not for view-only embedding of saved dashboards (use core), building charts in code (use data-visualization), data connection (use data-integration), or AI queries (use ai-analytics).

Core Luzmo setup - use whenever starting a new integration or hitting auth/API errors. Triggers on: API credentials (LUZMO_API_KEY, LUZMO_API_TOKEN), embed token generation (createAuthorization), SDK selection, 401/403 errors, REST-verb confusion, "how do I authenticate", "embed dashboard", "dashboardId", "dashboard not rendering". Essential starting point before any feature skill. Use eagerly for any auth or saved-dashboard/chart embedding question. Pair with domain skills for feature-specific work. Not for building charts in code (use data-visualization), data loading (use data-integration), or tenant isolation (use multitenancy).

Build a brand-new Luzmo chart component when no built-in chart type (and Flex) is sufficient. Triggers on: "custom chart", "build a custom chart", "no built-in chart type fits", "chart plugin", "manifest", "render/resize/buildQuery", "custom chart not in picker", "upload custom chart", "org release". Rare advanced path (~95% of users never need this). Not for Flex charts with built-in types (use data-visualization), embedding saved dashboards (use core), self-service chart editors (use analytics-studio), or auth setup (use core).

Getting data into Luzmo from any source. Use whenever connecting a database, pushing files, or modeling data. Triggers on: "connect data source", "upload CSV", "import data", "sync from database", "push data via API", "data not loading", createDataprovider. Provides ready-to-use scripts. Covers data modeling, Warp acceleration, and custom connectors. Use eagerly for any data-source or schema question. Essential before charts can display anything. Not for chart rendering (use data-visualization) or per-tenant access control (use multitenancy).