analytics-build
/analytics-build
Prowadzi konfigurację Atlan Analytics na własnych danych: wybór hurtowni, odkrywanie przypadków użycia, dashboardy i nazwy tabel.
- Autor
- atlanai ↗
- Repozytorium
- atlan-plugins ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 63
- Skrypty
- 42
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 42 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/acquisition.py, scripts/analytics_case.py, scripts/analytics_eval.py, scripts/analytics_flow.py, scripts/analytics_transcript.py, scripts/auth_recovery.py, scripts/checklist.py, scripts/context_contracts.py, scripts/context_state.py, scripts/dashboard.py, scripts/dashboard_errors.py, scripts/dashboard_preflight.py, scripts/dashboard_publish.py, scripts/dashboard_run.py, scripts/dashboard_r
Co robi i kiedy
Prowadzi konfigurację Atlan Analytics na własnych danych: wybór hurtowni, odkrywanie przypadków użycia, dashboardy i nazwy tabel.
Oryginalny opis (EN)
Atlan Analytics setup on your own data: pick a warehouse, then discover use cases, share a dashboard or name tables, and build. Use when setting up, resuming or handing off a run, its details, or workspace access. Not for a demo (analytics-demo).
Jak działa
- Opening
- The seven steps
- Explicit arguments
- Hand-offs
- MCP resources
Podgląd SKILL.md
---
name: analytics-build
description: Atlan Analytics setup on your own data: pick a warehouse, then discover use cases, share a dashboard or name tables, and build. Use when setting up, resuming or handing off a run, its details, or workspace access. Not for a demo (analytics-demo).
---
# Atlan Analytics on your own data: seven guided steps
An orchestrator. It owns the conversation, intent, the tracker and approvals, and takes a
person's own dashboards, folders, BI exports and query history to checked metrics they can
question here. It calls the capability skills without letting them ask the person anything:
`source-survey`, `metrics-generation` and `analytics-ask`. Before the first helper call, and
on every resume, read [shared setup](references/setup.md): it defines `PROJECT`, the stage
files and the review rule. This file sets their order and what the person sees.
Read plugin files with the Read tool, one file per call. In a shell, never print a separator such as
`echo =====`: zsh reads a word that starts with `=` as a command, fails and skips the rest of the line.
For workspace access or creation questions, follow [workspace help](references/setup/workspace-access.md)
and return. This includes explanation-only requests; do not start source inspection or publication.
Then read [shared conventions](references/conventions.md): audit sessions, task
authorization, privacy and status reporting. Reads of the selected source, packaged-runtime
initialization and generated-file reads are ordinary task steps. Once a publication
destination is chosen, show the checked plan and publish only after the person approves that
concrete plan. Respect explicit draft or review requests.
## Opening
[The interview](references/setup/intent.md) has every question and its options. Its shape:
1. **Card 1**, two questions in one card where the host allows it: which warehouse (those
already connected are labelled so), and what the person wants to do.
2. **One of three branches**, by that answer:
| They chose | Then |
| --- | --- |
| Let discovery decide | `source-survey` `discover`, then "Which should I build?" over up to three use cases with their tables plus "I have a dashboard", then at most two clarifying questions if something is unsettled. After the build, one offer to add a dashboard |
| Make my dashboard agentic | One card for the dashboard: files in the folder as options, a link or path as free text. A link is opened with that tool's sign-in started when needed, then `source-survey` `access` on it and its tables |
| I have a use case and know my tables | One card asking for the use case and tables as free text, with a skip to discovery, then `source-survey` `access` on them |
3. **Confirm and trigger**, the same in every branch: one line of what will be built and
from what, then "Build it?". Nothing is built before the yes.
A question the request already answers is not asked. Before card 1, look silently at what is
already connected (`source-survey` `connections`) and at BI file names in the working folder
(`PROJECT discover`). Say nothing about that look or where the options came from (at most
"Getting set up."), and read no data before the answers. The person's first sight is the card, whose own text is the
opening:
"Atlan Analytics turns your dashboards and the queries your team already runs into context:
what your numbers mean and how they are worked out. With that context, you can ask your data
questions in plain English and see what each answer is based on.
First, let me understand your tools and your domain."
The interview is this skill's own: `source-survey` never asks the person anything. Honor
existing choices. Survey-only requests stop after the survey. On resume, read
`PROJECT journey status`, name the saved result and the next step, and rebuild the tracker.
Detail-only requests get only the requested evidence.
## The seven steps
Show [the checklist](references/setup/checklist.md) in the host's task list from the first
action, and in chat with each step's result line, never inside a question's text. Follow
[one presentation flow](references/setup/presentation.md): read each moment's file when
reached and never replace a moment with a status line.
1. **Clarify your use case.** [The interview](references/setup/intent.md)'s card 1, and the
branch's own ask. Skip what the request already said.
2. **Survey your sources.** By branch: `source-survey` `discover` through
[discovery](../source-survey/references/discovery.md), or `access` on the dashboard and
tables the person named.
3. **Select tables and dashboards.** In the discovery branch,
[the use cases](references/setup/names.md) and any clarification. In every branch, the
interview's confirmation, "Build it?". A report is built whole.
4. **Generate and check metrics.** `metrics-generation` `generate` and `check` with the selection
and the whole survey, through [build and check](references/setup/build-check.md). Then
review the completed collection with actual counts and one representative metric.
5. **Keep local or save to Atlan Trident.** Read
[context built and where to keep it](references/setup/save.md) and
[preview and publish](references/setup/preview-publish.md); `metrics-generation` `save`.
6. **Ask a question.** Read [ready for questions](references/setup/ready.md). Answer only the
question the person picks, through `analytics-ask`, then `PROJECT journey asked`.
7. **Build a dashboard.** Read [the dashboard](../analytics-ask/references/dashboard.md).
Keep execution, source review, holds and releases separate, with factual check labels and
the tracker's step headings. Total definitions = metrics + queries. Attribute saved checks
to the earlier run. After publication, answers retrieve definitions before SQL runs. Cloning
a repository the person asks to set up is an ordinary step; repository names or layouts never
select a special workflow.
Use this host and its Atlan MCP connection. This chat with Atlan is the talk-to-data agent;
this add-on does not deploy or evaluate a separate agent, and says so in one line when asked.
If Registry tools are missing or sign-in is required, follow
[connection recovery](references/auth-recovery.md) inside this task and resume the saved
stage. Never infer a missing coding-host plugin from a generic app-directory search.
## Explicit arguments
These routes are reached only by name; the guided flow never offers them.
- `metrics`: load the `metrics-generation` skill and follow it with the remaining arguments
as scope. Metrics Studio sends `/atlanai-analytics:analytics-build metrics`, so this
hand-off stays. If the first argument is exactly `metrics`, no guided step runs.
- `dashboard` or `propose`: load the `metrics-generation` skill with that argument.
- `connect`: load the `source-survey` skill with that argument.
- `ask`, or a data question with no setup work: load the `analytics-ask` skill. When this
folder holds a run, pass its directory, so the answer uses the run's own rules.
In Claude Code, load a sibling skill with the Skill tool as `atlanai-analytics:<name>`. The
Registry marketplace bundles these skills in `atlanai`; use its installed namespace instead,
and do not install this add-on beside that bundle.
## Hand-offs
| From | To | Carries |
| --- | --- | --- |
| `analytics-demo` ("Continue building on real data") | here | Nothing but the connection. A demo run never becomes a build |
| here | `analytics-ask` | The run, so answers read its context |
| `analytics-ask` (no metric covers a question) | here | The question, as the subject for the discovery branch |
| here, when the survey finds no readable source | `analytics-demo` | Nothing |
## MCP resources
Installed paths resolve under `${CLAUDE_PLUGIN_ROOT}/skills/analytics-build/`; the sibling
skills sit beside it. With MCP only, read `atlan://defaults/skills/analytics-build/SKILL.md`
and cited relative references at that base. Fetch needed scripts locally with their relative
layout before execution; MCP does not expand plugin-local includes.
Never expose credentials or identifying query literals.
Pliki w paczce (63)
- SKILL.md 8 KB
- agents/openai.yaml 1 KB
- references/auth-recovery.md 12 KB
- references/conventions.md 10 KB
- references/project-conventions.md 8 KB
- references/project.md 16 KB
- references/setup.md 7 KB
- references/setup/build-check.md 8 KB
- references/setup/checklist.md 4 KB
- references/setup/intent.md 15 KB
- references/setup/names.md 5 KB
- references/setup/presentation.md 5 KB
- references/setup/preview-publish.md 8 KB
- references/setup/progress.md 3 KB
- references/setup/ready.md 8 KB
- references/setup/render.md 1 KB
- references/setup/save.md 7 KB
- references/setup/workbench.md 7 KB
- references/setup/workspace-access.md 2 KB
- scripts/acquisition.py 3 KB
- scripts/analytics_case.py 10 KB
- scripts/analytics_eval.py 125 KB
- scripts/analytics_flow.py 4 KB
- scripts/analytics_transcript.py 2 KB
- scripts/auth_recovery.py 10 KB
- scripts/checklist.py 7 KB
- scripts/context_contracts.py 72 KB
- scripts/context_state.py 3 KB
- scripts/dashboard.py 8 KB
- scripts/dashboard_errors.py 9 KB
- scripts/dashboard_preflight.py 4 KB
- scripts/dashboard_publish.py 11 KB
- scripts/dashboard_run.py 12 KB
- scripts/experience.py 42 KB
- scripts/experience_workbench.py 5 KB
- scripts/journey.py 11 KB
- scripts/local_data.py 20 KB
- scripts/local_prepare.py 9 KB
- scripts/metric_preview.py 12 KB
- scripts/page_scope.py 7 KB
- scripts/progress.py 4 KB
- scripts/project.py 44 KB
- scripts/publication_batches.py 7 KB
- scripts/publication_followup.py 8 KB
- scripts/publication_receipts.py 10 KB
- scripts/reconciliation.py 6 KB
- scripts/registry_contract.py 4 KB
- scripts/registry_inspection.py 6 KB
- scripts/retrieval.py 6 KB
- scripts/source_inventory.py 5 KB
- scripts/dashboard_runtime/dependencies/pbixray.in 1 KB
- scripts/dashboard_runtime/dependencies/pbixray.lock 26 KB
- scripts/dashboard_runtime/scripts/inspect_powerbi.py 13 KB
- scripts/dashboard_runtime/scripts/setup_pbixray.py 1 KB
- scripts/dashboard_runtime/trident/__init__.py 1 KB
- scripts/dashboard_runtime/trident/contracts.py 12 KB
- scripts/dashboard_runtime/trident/core.py 28 KB
- scripts/dashboard_runtime/trident/dax_syntax.py 4 KB
- scripts/dashboard_runtime/trident/evaluation.py 10 KB
- scripts/dashboard_runtime/trident/metric_contract.py 13 KB
- scripts/dashboard_runtime/trident/powerbi_file.py 6 KB
- scripts/dashboard_runtime/trident/snowflake_cli.py 11 KB
- scripts/dashboard_runtime/trident/snowflake_discovery.py 7 KB
Wersje
W bazie nie ma innych skilli o nazwie analytics-build.
Migawka bazy z 13.11.2026 · wersja paczki bb60be87cc09 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90analytics-demo
Prowadzi po demo Atlan Analytics na zmyślonych danych: metryki, zapis, pytanie i projekt dashboardu. - 81atlan-author-knowledge
Tworzy i edytuje pakiety wiedzy w Atlan, np. glosariusz, opisy tabel i runbooki, które czytają agenty. - 100atlan-search
Pomaga znaleźć dane w katalogu Atlan: który z narzędzi MCP (semantic_search, search_assets, get_assets, traverse_lineage) użyć i jakie filtry dają właściwy wynik przy pytaniach o tabele, dashboardy i tagi. - 100analytics
Rysuje wykresy danych produktu w GrowthBook, buduje dashboardy analityczne, zarządza katalogiem metryk i odpytuje hurtownię danych bezpośrednio. - 100hr-analytics
Pomaga w analityce HR: analizuje dane pracowników, buduje wskaźniki i dashboardy, bada rotację, tworzy raporty i modele predykcyjne oraz strategię zarządzania danymi. - 100accelerator-readiness
Sprawdza gotowość laptopa do akceleratora analityki agentowej: agentów kodujących, połączenie z hurtownią i narzędzia BI, potem pisze raport.