← LandbaseCONTENT HISTORY

Update to Landbase

Snapshot Nov 19, 2026 · 12:18 UTC · version 0.2.1

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find work email addresses and phone numbers for the people in a Landbase dataset. Use when the user asks for emails, phone numbers or contact details for a list of people, or asks how to reach the people on a list.",
  "included_files": [],
  "name": "find-contact-info",
  "skill_md_contents": "---\nname: find-contact-info\ndescription: Find work email addresses and phone numbers for the people in a Landbase dataset. Use when the user asks for emails, phone numbers or contact details for a list of people, or asks how to reach the people on a list.\n---\n\n# Find contact information\n\n`enrich_contacts` finds work emails, phone numbers, or both, for each person in\na dataset. It uses the account's existing usage allowance. The tool returns an\noperation-specific usage quote before execution.\n\n## Steps\n\n1. **Find the dataset.** Use a dataset ID from this conversation, or call\n   `list_datasets` and ask the user which one. If the user has more than one\n   account, pass the same `account_id` on every call.\n2. **Make sure that the rows are people.** Call `get_dataset_fields` and\n   `preview_dataset`. Each row must identify one person, for example with a\n   name and a company, or a LinkedIn URL. If the dataset has only companies,\n   ask the user which job titles they want. Then find those people with the\n   `build-prospect-list` skill.\n3. **Ask what to find.** Ask the user if they want emails, phone numbers, or\n   both. Set `enrich_email_address` and `enrich_phone_number` to match.\n4. **Limit the rows.** If the user needs fewer rows than the dataset has, call\n   `transform_dataset` with a `LIMIT` or a `WHERE` clause first. Use its\n   `output_dataset_id`.\n5. **Get a quote.** Call `enrich_contacts` without `confirm`. The result is\n   `needs_confirmation` with the row count and the estimated credits. Show them\n   to the user and ask for approval.\n6. **Run.** After the user agrees, call `enrich_contacts` again with the same\n   arguments and `confirm=true`. Call `get_workflow_run` with the\n   `workflow_run_id` until the status is `SUCCEEDED`. A large list can take a\n   long time. Continue with the same run ID.\n7. **Show the result.** Use the `output_dataset_id`. Call `get_dataset_fields`\n   to find the email and phone columns. Use `preview_dataset` with SQL to count\n   the rows that have an email or a phone number, and show some examples.\n8. **Offer a file.** To give the user a file, use the `export-list` skill.\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 start a paid run without a quote and the user's approval.\n- Keep the `workflow_run_id`. A timeout does not stop the run. Check the status\n  before you start the run again.\n- Do not send messages to the people on the list. This skill only finds contact\n  details.\n"
}

SHA-256 of public snapshot: 25abea77ceb9a971141674b02bc20c8c211cd81e135ec496fb9adac29b6aaa40