Skip to content
Skills Library
Data & analytics · Analysis

source-survey

/source-survey

Atlan Analytics: survey a warehouse, folder or dashboard: connections, key tables, what a source covers, metric names. Use when asked what data exists, which tables to use, or if a source is usable. Not for building metrics (metrics-generation).

Licence
Apache-2.0
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Atlan Analytics: survey a warehouse, folder or dashboard: connections, key tables, what a source covers, metric names. Use when asked what data exists, which tables to use, or if a source is usable. Not for building metrics (metrics-generation).

Original author description

Atlan Analytics: survey a warehouse, folder or dashboard: connections, key tables, what a source covers, metric names. Use when asked what data exists, which tables to use, or if a source is usable. Not for building metrics (metrics-generation).

How it works

  1. Who is calling
  2. Operations
  3. What comes back
Original SKILL.md headings · 107 lines, 1,112 words
SKILL.md preview
---
name: source-survey
description: "Atlan Analytics: survey a warehouse, folder or dashboard: connections, key tables, what a source covers, metric names. Use when asked what data exists, which tables to use, or if a source is usable. Not for building metrics (metrics-generation)."
---

# Survey a source and check it is ready

A capability. It reads, it never writes to Atlan, and it authors no metric or SQL. A person
can call it directly; `analytics-demo`, `analytics-build` and `analytics-ask` call it as a step.

Read [shared conventions](../analytics-build/references/conventions.md) first: privacy,
read-only SQL and status reporting apply. `PROJECT` means
`python3 "<build-dir>/scripts/project.py" --run-dir "<run-dir>"`, where `<build-dir>` is the
`analytics-build` skill's directory beside this one (`${CLAUDE_PLUGIN_ROOT}/skills/analytics-build`
in Claude Code). Pass separate argv entries; zsh does not split a scalar holding a command.

## Who is calling

- **A flow called it** (demo, build or ask named the operation and the run): ask the person
  nothing. Use the inputs given, write the result into the caller's run, and return. The
  caller decides what the person sees.
- **A person called it**: ask only for a missing source, once. Show the result as below and
  stop: no generation, destination question or publication pitch. If they then want metrics,
  hand to `analytics-build` with the survey already done.

## Operations

| Operation | Does | Procedure |
| --- | --- | --- |
| `connections` | Lists the warehouse connections already configured on this machine, and whether each answers | [Connections, discovery and access](references/discovery.md) |
| `discover` | On a chosen warehouse, for a domain or with none: finds the schemas in use and the tables that matter, reads their columns and returns use cases, each with its tables | [Connections, discovery and access](references/discovery.md) |
| `access` | For sources the person named (a dashboard, a list of tables): whether each opens and can be read, and exactly what cannot | [Connections, discovery and access](references/discovery.md) |
| `inventory` | Reads every supplied source in full (models, dashboards, query history, SQL, local data) and says what they cover and could answer | [Inspect and scope](references/inspect-scope.md), section 1 |
| `plan` | Orders the sources to build from: BI reports and models, then query history, then table definitions | [Inspect and scope](references/inspect-scope.md), section 2 |
| `scope` | Selects pages, measures and query-history tables | [Inspect and scope](references/inspect-scope.md), section 2 |
| `candidates` | Lists candidate metric names and the questions they would answer, ranked by relevance to a stated focus or problem. Names only | Below |
| `readiness` | Says whether work can proceed: source readable, data executable, Atlan reachable, published context present | Below |
| `connect` | Finds and checks the warehouse query tool | [Warehouse discovery](references/connect.md) |

`connections` and `discover` come first when a warehouse is the starting point. Run
`inventory` on a supplied file or folder before `plan`, `scope` and `candidates`; `readiness` and
`connect` can run alone. Query history follows
[query history](references/warehouses/query-history.md); a warehouse's dialect and statements
are in [warehouses](references/warehouses.md), only the section for that warehouse. Reuse a
supplied source and the selected run; never resume another project silently.

### `inventory`

1. Resolve the run with `PROJECT location --workspace "<working-directory>"`, unless a run
   directory was supplied. The resolver creates nothing.
2. Inspect: `PROJECT survey "<absolute-path>"` for a folder or file, a clone for a repository
   link (never run its setup scripts), and the authorized host tools for a report link.

### `candidates`: names and questions before metrics

The person commits to names, so a wrong focus costs one question and not a generation run.

1. Take names from the inventory only: declared measures in models and dashboards, and
   measures that recur in query history. Never invent a name the sources do not show.
2. Rank by relevance to the focus or problem the caller passed. With none, rank by how many
   sources show the measure.
3. Return at most ten, each with its name, one line of plain meaning, and where it came from
   (the dashboard tile, the model measure, or the count of past queries). When the caller
   source is a report, cover every page: group them by page with a count per page, the
   focus's page first, and do not cut the report to ten.
4. Add two or three questions the names would answer, phrased as things to learn and worded
   from the sources. No period, cause or number the sources do not hold.
5. Label every one as discovered, with SQL not generated and checks not run. Do not preview
   SQL, run the engine or install its runtime for this operation.

### `readiness`: one of three answers

| Answer | Means | Next step to name |
| --- | --- | --- |
| `ready` | Sources are readable and, for answers, released context or an executor exists | None |
| `partial` | Some coverage is held: a missing export, an untested executor, a sign-in not yet done | The one thing that unblocks the held part |
| `none` | No readable source and no published context | Offer `analytics-demo` |

Check only what the caller's goal needs: source access from the inventory; data execution
through `connect` only when live numbers are needed; Atlan access only for saving or
answering, with a failed read following
[connection recovery](../analytics-build/references/auth-recovery.md).

**Buildable is part of readiness, and it is settled before any question.** A report can be
built from only when the tables it reads exist somewhere a rule can run: a reachable
warehouse, or a bound local database. A report whose data is packed inside the file (an
extract or an embedded sheet) with no table behind it is `none` for building: say that, and
the one way round it (name the warehouse table that holds the same data). A caller never
asks a use-case question about a source that cannot be built.

## What comes back

The saved run holds the survey; `PROJECT journey status` and `PROJECT checklist` read it.
Return to the caller, or show the person:

- the source types found and their subject, in two or three sentences, and how they
  complement each other;
- two or three analyses the sources could support, phrased as things to learn;
- for `connections`, the list; for `discover`, one line of what was found, then two to
  four use cases, each with one line of what it answers and the tables that power it;
- for `candidates`, the ranked names and questions; for `readiness`, the answer and its one
  next step.

Counts alone do not show understanding. Use the inspector's actual count and noun: 110 history
records are not 110 metrics. Keep file names and diagnostics in details. Distinguish sample,
available, needs review, held and scan-limited inputs. Never invent tables, measures, user
behaviour or findings.

Before sending: the first sentence is the result; one next step, not a menu; no apology, no
closing offer; commas and full stops, no em dashes or exclamation marks.
Files in this package (9)
  • SKILL.md 7 KB
  • agents/openai.yaml 1 KB
  • references/connect.md 7 KB
  • references/discovery.md 10 KB
  • references/inspect-scope.md 9 KB
  • references/warehouses.md 10 KB
  • references/warehouses/add-server.md 1 KB
  • references/warehouses/cli.md 1 KB
  • references/warehouses/query-history.md 8 KB

Versions

The database has no other skills named source-survey.

Database snapshot: 13.11.2026 · package version d62c00b2ee7d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100analytics
    Chart GrowthBook product data, build Analytics dashboards, manage the metric catalog, or query the warehouse directly — run Product Analytics explorations, save charts together on a dashboard, search metrics and fact tables, create fact metrics and their fact tables, or fall…
  • 90analytics-build
    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).
  • 90analytics-demo
    Guided Atlan Analytics demo on made-up data: pick a demo, build its metrics, save them, ask a question and design a dashboard. Use when someone wants to try, see or learn Atlan Analytics. Not for their own data (analytics-build).
  • 90dashboard-builder
    Build an interactive HTML dashboard from any data source — a CSV file, a folder of files, a spreadsheet, or pasted numbers. The dashboard shows KPIs, charts, and lets the user filter and explore. Use this whenever the user says 'build a dashboard,' 'visualize this data,' 'turn…
  • 95metrics-dashboard
    Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.
  • 100metrics-dashboard
    Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.