← LandbaseCONTENT HISTORY
WHAT CHANGED
Update to Landbase
Snapshot Nov 19, 2026 · 12:18 UTC · version 0.2.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Landbase 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": "Get a Landbase dataset as a CSV, JSONL or Parquet file through a download link. Use when the user asks to download or export a list, or asks for a file or spreadsheet of a list.",
"included_files": [],
"name": "export-list",
"skill_md_contents": "---\nname: export-list\ndescription: Get a Landbase dataset as a CSV, JSONL or Parquet file through a download link. Use when the user asks to download or export a list, or asks for a file or spreadsheet of a list.\n---\n\n# Export a list\n\nDownloads cost 0 credits. Before the download, remove the rows and columns that\nthe user does not need.\n\n## Steps\n\n1. **Find the correct dataset.** Use the dataset that the user names or\n talked about last, for example \"the qualified list\" or \"the list with\n emails\". If more than one dataset in this conversation can be the correct\n one, for example a sample and a full run, or two segments, and the user does\n not say which one, show those datasets with their row counts and ask. Use\n the latest `output_dataset_id` only when one dataset fits the request. Do\n not export a test sample when the user wants the full list. If the user has\n more than one account, pass the same `account_id` on every call.\n2. **Remove what the user does not need.** Show the row count and the columns\n with `get_dataset`. If the user wants fewer rows or columns, call\n `transform_dataset` with SQL, for example\n `SELECT company_name, website, email FROM input_dataset WHERE email IS NOT NULL`.\n Use its `output_dataset_id`.\n3. **Make the file.** Call `publish_dataset` with `format=\"csv\"` (or `jsonl.gz`\n or `parquet` if the user asks). Call `get_workflow_run` with the\n `workflow_run_id` until the status is `SUCCEEDED`. Use its\n `output_dataset_id`.\n4. **Get approval for the download.** Call `get_download_url` without\n `confirm`. The result is `needs_confirmation` with the row count. Tell the\n user the row count and ask for approval.\n5. **Get the link.** After the user agrees, call `get_download_url` again with\n `confirm=true`. Give the link to the user. The link expires after about 30\n minutes.\n\nIf `get_download_url` returns `PUBLISH_REQUIRED`, do step 3 first.\n\n## Rules\n\n- Use an `output_dataset_id` only when its run status is `SUCCEEDED`.\n `transform_dataset` can return while its run is `RUNNING`. Then call\n `get_workflow_run` with its `workflow_run_id` until the run stops. If the\n status is `FAILED` or `CANCELLED`, stop and tell the user the reason.\n- Do not download without the user's approval.\n- Anyone who has the link can download the file until it expires. Do not put\n the link in a public place.\n"
}SHA-256 of public snapshot: a1785ae81f9222f19bda1ce51e88b2e0953ebc14bba6d07e4fcc670e3b760ec6