Skip to main content
Preview Ask an agent “What was revenue last quarter?” and it writes its own SQL, so two people asking the same question can get two different numbers. The Analytics plugin fixes that inside the coding agent you already use. It reads the dashboards and queries your team already trusts, turns them into metrics and saved queries, checks each one on your data, and then answers questions from those definitions, showing which one it used. Your chat is the talk-to-data agent. The plugin doesn’t deploy or score a separate agent.

​
What you can do with it

  • Try it on made-up data. A guided demo builds context for a small firm from its dashboard, answers a question, and designs a dashboard, in about 15 minutes.
  • Set it up on your own data. Point it at a dashboard, a folder, a BI export, or your warehouse’s query history. It asks what you want to analyse, builds the metrics that matter for that, and checks them.
  • Ask your data questions. Answers come from metrics released in Atlan Trident, with the definition used. When no metric covers a question, it says so instead of guessing.
  • Fix or propose a metric. Change a metric you own, or send a proposed fix or new metric to its owners in Metric Studio.

​
Before you begin

  • A coding agent with plugins: Claude Code, Codex, or Cursor.
  • Python 3: The plugin runs bundled Python helpers. The first build sets up its own isolated environment with pinned dependencies, after you allow it.
  • Git: The demo downloads its sample data from atlanai/analytics-agent-accelerator.
  • To save metrics to Atlan Trident: Metric Studio installed for your organization, and Builder or Admin in the workspace you save to. See Install and manage apps. Keeping the work on your computer needs neither, and no sign-in.
  • To check metrics on your own data (optional): A read-only connection to Snowflake, Databricks, or another SQL warehouse, through Atlan Trident or a warehouse connector in your agent. Without one, the plugin still builds metrics and marks their SQL as untested.

​
Install

The Analytics plugin, atlanai-analytics, builds on the atlanai plugin and comes from the same marketplace, atlanai/atlan-plugins. Then sign in to Atlan Trident as Install the Atlan plugin describes. You can skip sign-in until you want to save to Atlan Trident or ask questions of released metrics.

​
Try demo

In your project folder, ask your agent:
In Claude Code, /atlanai-analytics:analytics-demo does the same. Pick a demo: The demo shows six steps as it goes: load the demo data, choose what to build from, build and check metrics, keep them local or save them to Atlan Trident, ask a question, and build a dashboard. The demo’s data loads into a local database, so every check runs on real rows. When it ends, choose Continue building on real data to start on your own sources.

​
Set up on your own data

1

Start setup

In your project folder, give your agent a source and, if you have one, the problem you’re working on:
In Claude Code, /atlanai-analytics:analytics-build does the same. A source can be a dashboard link, a local folder, a Power BI or Tableau export, data models, SQL files, or your warehouse’s query history. The plugin shows seven steps and keeps them up to date as it works.
2

Review survey

The plugin reads every source in full and explains what it covers and what it could help you analyse. It changes nothing in Atlan Trident.
3

Say what you want to analyse

Answer two questions: the business area to focus on, and what you want to do with it. Then pick the metric names to build from the list the survey found.
4

Confirm scope

Confirm the dashboard pages, measures, and query-history tables those metrics need.
5

Review metrics

The plugin builds each metric and saved query, with the whole survey as context, and runs it on your data. For each one, it shows the rule in plain words, the population it counts, its source, and its check status: passed, untested, or held. A held definition failed a check and won’t be published until it’s fixed.
6

Keep local or save

Choose Keep on this machine to leave everything in your project folder, or save to a workspace in Atlan Trident. Before saving, the plugin shows the plan with its counts, to publish, held, and kept local, and publishes only after you approve that plan.
7

Ask question

The plugin suggests questions your new metrics can answer. Pick one, or ask your own.
8

Build dashboard

Optionally, design a small dashboard from the same metrics. The plugin proposes a layout first. In Claude, it builds the dashboard as an Artifact; in other agents, as one HTML file in your project folder. It doesn’t publish it anywhere.
You can narrow the scope, ask for details, keep the work local, or pause at any step. Run the same request again in that folder to resume where you stopped.

​
Ask questions

After metrics are released, ask in plain English:
In Claude Code, /atlanai-analytics:analytics-ask does the same. The plugin searches released metrics across every workspace you can read, keeps the one that measures what you asked, and runs read-only SQL through your warehouse connection. The answer names the metric it used and links to it in Atlan Trident. When no released metric measures what you asked, the answer says so and names the near misses it set aside. It then offers to build the missing metric, starting from your question.

​
Change or propose metric

Ask your agent to change a metric, for example “Count refunded orders out of order count”. What happens depends on who owns it: Owners see proposals in the Metric Studio catalog. See Review and apply what agents suggest. In Claude Code, /atlanai-analytics:metrics-generation propose files a proposal directly.

​
Skills

Your agent picks a skill from your request. You can also run one by name. The plugin keeps each run in your project folder, under .atlan-analytics/<project>/. Add that folder to .gitignore if you don’t want it committed.

​
If you used /atlan-analytics

Earlier versions had a single atlan-analytics skill. In current versions:
  • /atlan-analytics is now /atlanai-analytics:analytics-build, and asking questions moved to /atlanai-analytics:analytics-ask.
  • /atlan-analytics metrics is now /atlanai-analytics:analytics-build metrics, which hands off to metrics-generation.
  • /atlan-analytics propose is now /atlanai-analytics:metrics-generation propose.
  • The build, improve, and eval modes, which registered and scored a separate analytics agent, are gone. To score an agent you run yourself, see Evals.