← ClayCONTENT HISTORY
WHAT CHANGED
Update to Clay
Snapshot Nov 18, 2026 · 06:19 UTC · version 2.38.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clay and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Clay tables — analyze what a table does: reconstruct the column DAG, stage it, and narrate the workflow encoded in its columns. Use when the user asks \"what does this table do?\", \"explain the {table} workflow\", \"walk me through this table\", or \"what's set up here?\".",
"included_files": [],
"name": "tables-analyze",
"skill_md_contents": "---\nname: tables-analyze\ndescription: 'Clay tables — analyze what a table does: reconstruct the column DAG, stage it, and narrate the workflow encoded in its columns. Use when the user asks \"what does this table do?\", \"explain the {table} workflow\", \"walk me through this table\", or \"what''s set up here?\".'\nallowed-tools: Read\n---\n\n# Analyze a table\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\n**Use when:** \"what does this table do?\", \"explain the {table} workflow\", \"walk me through this table\", \"what's set up here?\" — a question about the table's **structure and the workflow encoded in its columns**, not about any single record.\n\nA Clay table is a column DAG: `source` and input `basic` columns are roots; `basic` formula columns and `action` (enrichment) columns depend on the `{{f_xxx}}` tokens in their settings. Analyzing the table = reconstructing that graph, ordering it into stages, and narrating what it does. Cheap and read-only: ~3 commands (metadata + columns + a row sample).\n\n**Finding the table:** resolve it as in the tables entry-point skill (\"Finding a table\").\n\n## 1. Frame the table — `clay tables get`\n\n(The output is discriminated on `type` — shape in `clay tables get --help`.) Read off the frame the workflow sits in:\n\n```bash\nclay tables get <tableId> | jq .\n```\n\n- `type` — `\"archive\"` means this is an archive companion (its `parentTableId` points at the regular table); analyze the parent instead, the archive has no workflow of its own.\n- `rowCount` — current size.\n- `archive` — non-null means processed rows **flow out** to an archive, indexed on `archive.searchableFieldFormula`.\n\nWhere data **enters** and at what scale comes from the columns (step 2): `source` columns carry `sources[]` with each attached source's `numSourceRecords`.\n\n## 2. Build the dependency catalog — `clay tables columns get`\n\nThis is where the graph lives. Run the token-extraction recipe in the tables entry-point skill's `dependency-catalog.md` over `clay tables columns get <tableId>`. It yields one entry per column — `{ id, name, type, role, integration, gate, dependsOn: [names] }` — resolving every `{{f_xxx}}` edge (including those in `formulaWaterfall` and `formulaMap` keys) to a column name. `dependsOn` are the upstream columns; `gate` (when set) is the condition under which an action runs.\n\nFor a known bulk enrichment table, inspect the source entries to determine the origin. If a source includes `audience`, use its `entityType`, `segments[].id`, `isGlobal`, and `entityIdOnly` as the source configuration when rebuilding it as a workflow. `isGlobal: true` represents the global Audience and has no segment resource objects; otherwise use the ids from `segments`. Bulk enrichment tables can have non-Audiences origins, and an `audience-source` on its own does not prove the table is a bulk enrichment table.\n\n## 3. Stage the graph\n\nOrder the catalog into stages by dependency depth — roots first, then columns whose deps are all already placed, and so on:\n\n- **Stage 0 (roots):** `source` columns and `input` basics (empty `dependsOn`). This is the raw data.\n- **Each next stage:** columns whose `dependsOn` are all in earlier stages.\n- `{{f_xxx}}` **never crosses tables**, so the whole graph is self-contained — every edge resolves within this column set. (A token that resolved to a bare `f_id` rather than a name = a deleted/renamed column; note it.)\n\nThis left-to-right order ≈ the column order in the Clay UI and gives you the pipeline.\n\n## 4. Light health read — sample rows\n\n`clay tables rows list … --limit 10` (no separate sample command) for a rough per-column status read — which columns mostly run vs sit idle or error:\n\n```bash\nclay tables rows list <tableId> --limit 10 | jq '{ truncated, columns: ([ .data[].cells | to_entries[] ] | group_by(.key) | map({ col: .[0].key, n: length, statuses: (group_by(.value.status) | map({ (.[0].value.status): length }) | add) })) }'\n```\n\nMap `col` ids to names from the catalog. This is a **sample of ≤10 rows**, so treat it as indicative, not a true rate — say so. Statuses are lowercase (`success`, `empty`, `error`, `queued`/`running`/…). If a stage shows heavy `error`, offer to hand off to `/tables-error-sweep`; it performs a full scan for normal tables and a retained-row sample for bulk enrichment tables. On a query-enabled table, `tables query` group-bys can add exact value distributions to the narrative — statuses still come from the sample (they aren't queryable).\n\nIf `rows list` returns `truncated: true`, it is deliberately limited to one unfiltered, unordered sample of at most 20 currently retained passthrough rows. It neither accepts nor returns a cursor, and completed rows may already have been deleted. The sample can therefore be empty and must never be presented as the source dataset or a complete row listing; the source configuration from step 2 is authoritative for migration.\n\n## 5. Report — narrative + ASCII DAG\n\nLead with the source(s), show the staged DAG with each column's integration and gate, then a one-paragraph plain-English summary. Append the sampled health read.\n\n```\nPeople — 1,543 rows · source: CSV Import (1,543) · archives to t_xyz789 (on Email)\n\nStage 1 Domain (basic, formula) ← Company\nStage 2 Find Email (action: Prospeo) ← Domain\n gated: only runs if {{Domain}} is present\nStage 3 Enrich Person (action: Clearbit) ← Find Email\nStage 4 Push to HubSpot (action: HubSpot) ← Enrich Person\n gated: only runs if {{Find Email}} is present\n\n→ This table takes companies from a CSV, derives each company's domain, finds a\n contact email via Prospeo (when a domain exists), enriches the person via\n Clearbit, and syncs the result to HubSpot when an email was found. Processed\n rows are archived by email. Integrations used: Prospeo, Clearbit, HubSpot.\n\nHealth (sampled, 10 rows): Domain 10/10 success · Find Email 8 success / 2 empty ·\n Enrich Person 7 success / 1 error / 2 empty · Push HubSpot 7 success / 3 empty.\n Indicative only (small sample) — run /tables-error-sweep for a deeper diagnosis.\n```\n\nKeep the narrative honest to the graph: only claim an edge the tokens actually show, and describe a gate exactly as its `conditionalRunFormulaText` reads (don't invent the condition).\n\n## Hand-offs\n\n- A specific value's origin / why one action didn't fire → `/tables-value-trace` (uses the same token extraction, walking one column backward).\n- Heavy errors in a stage → `/tables-error-sweep` (sample-only for bulk enrichment tables).\n- \"Rows aren't being added\" surfaced by metadata → `/tables-capacity`.\n"
}SHA-256 of public snapshot: 77586183a14bba9c4989c2014acbfc0bd3cd13a3466d257673177f61db9abcf8