← LeadbaseCONTENT HISTORY

Update to Leadbase

Snapshot Nov 3, 2026 · 00:13 UTC · version 1.0.2

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-started

Full description — Now says: Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Leadbase and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 1, 2026 · 18:11 UTC

Connect Leadbase, verify workspace access without paid research, and help the user choose a first company, people or web research task.

After

Nov 3, 2026 · 00:13 UTC

Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task.

Skill instructions

Before

Nov 1, 2026 · 18:11 UTC

Connect Leadbase, verify workspace access without paid research, and help the user choose a first company, people or web research task. Verify access using open_workspace or sheets_list.

After

Nov 3, 2026 · 00:13 UTC

Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task. For signup, resumable authorization, CLI device codes and recovery, ...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,11 +1,13 @@
 ---
 name: get-started
-description: Connect Leadbase, verify workspace access without paid research, and help the user choose a first company, people or web research task.
+description: Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task.
 ---
 
 Use the installed Leadbase MCP connection. Never ask for API keys or passwords in chat. If disconnected, use the host's connection flow; do not invent success or edit unrelated client settings.
 
-Verify access using open_workspace or sheets_list. This is read-only and does not authorize paid work. Explain, in the user's language, that Leadbase can find companies and professional contacts, research existing rows, or collect products and public posts in an editable sheet. Offer at most three concrete examples relevant to their stated work.
+For signup, resumable authorization, CLI device codes and recovery, read the canonical guide at https://www.leadbase.io/docs/settings/mcp.md before guiding setup. A new user can choose Google or verify their business email without a password, then create or select a workspace. The user verifies email and explicitly approves access. Never request their email link or accept permissions yourself. Client registration does not create a user account. Keep native host OAuth; do not add another account system.
+
+Verify access using billing_get. This is read-only and does not authorize paid work. Explain, in the user's language, that Leadbase can find companies and professional contacts, research existing rows, or collect products and public posts in an editable sheet. Offer at most three concrete examples relevant to their stated work.
 
 If the user has already requested research, skip the introduction and execute that scope. Otherwise ask which result they need. Account connection or available credits alone is not permission to start research. Do not send outreach, buy products, purchase credits, or promise complete coverage.
 
Full technical diff · 2 changed fields

changed /description

BEFORE
"Connect Leadbase, verify workspace access without paid research, and help the user choose a first company, people or web research task."
AFTER
"Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task."

changed /skill_md_contents

BEFORE
"---\nname: get-started\ndescription: Connect Leadbase, verify workspace access without paid research, and help the user choose a first company, people or web research task.\n---\n\nUse the installed Leadbase MCP connection. Never ask for API keys or passwords in chat. If disconnected, use the host's connection flow; do not invent success or edit unrelated client settings.\n\nVerify access using open_workspace or sheets_list. This is read-only and does not authorize paid work. Explain, in the user's language, that Leadbase can find companies and professional contacts, research existing rows, or collect products and public posts in an editable sheet. Offer at most three concrete examples relevant to their stated work.\n\nIf the user has already requested research, skip the introduction and execute that scope. Otherwise ask which result they need. Account connection or available credits alone is not permission to start research. Do not send outreach, buy products, purchase credits, or promise complete coverage.\n\nUse the real MCP app to display sheets when the host supports it. The Leadbase sidebar app opens the accessible sheet library; its sheet editor supports live updates, search, filters and editing according to the account's permissions. Text-only clients receive structured results and a Leadbase link instead. Do not claim a UI rendered merely because a tool returned successfully.\n"
AFTER
"---\nname: get-started\ndescription: Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task.\n---\n\nUse the installed Leadbase MCP connection. Never ask for API keys or passwords in chat. If disconnected, use the host's connection flow; do not invent success or edit unrelated client settings.\n\nFor signup, resumable authorization, CLI device codes and recovery, read the canonical guide at https://www.leadbase.io/docs/settings/mcp.md before guiding setup. A new user can choose Google or verify their business email without a password, then create or select a workspace. The user verifies email and explicitly approves access. Never request their email link or accept permissions yourself. Client registration does not create a user account. Keep native host OAuth; do not add another account system.\n\nVerify access using billing_get. This is read-only and does not authorize paid work. Explain, in the user's language, that Leadbase can find companies and professional contacts, research existing rows, or collect products and public posts in an editable sheet. Offer at most three concrete examples relevant to their stated work.\n\nIf the user has already requested research, skip the introduction and execute that scope. Otherwise ask which result they need. Account connection or available credits alone is not permission to start research. Do not send outreach, buy products, purchase credits, or promise complete coverage.\n\nUse the real MCP app to display sheets when the host supports it. The Leadbase sidebar app opens the accessible sheet library; its sheet editor supports live updates, search, filters and editing according to the account's permissions. Text-only clients receive structured results and a Leadbase link instead. Do not claim a UI rendered merely because a tool returned successfully.\n"
Full snapshot data
{
  "description": "Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Use when connecting Leadbase, checking workspace or credit access, opening the workspace, or choosing a first B2B lead generation, company research or prospecting task.\n---\n\nUse the installed Leadbase MCP connection. Never ask for API keys or passwords in chat. If disconnected, use the host's connection flow; do not invent success or edit unrelated client settings.\n\nFor signup, resumable authorization, CLI device codes and recovery, read the canonical guide at https://www.leadbase.io/docs/settings/mcp.md before guiding setup. A new user can choose Google or verify their business email without a password, then create or select a workspace. The user verifies email and explicitly approves access. Never request their email link or accept permissions yourself. Client registration does not create a user account. Keep native host OAuth; do not add another account system.\n\nVerify access using billing_get. This is read-only and does not authorize paid work. Explain, in the user's language, that Leadbase can find companies and professional contacts, research existing rows, or collect products and public posts in an editable sheet. Offer at most three concrete examples relevant to their stated work.\n\nIf the user has already requested research, skip the introduction and execute that scope. Otherwise ask which result they need. Account connection or available credits alone is not permission to start research. Do not send outreach, buy products, purchase credits, or promise complete coverage.\n\nUse the real MCP app to display sheets when the host supports it. The Leadbase sidebar app opens the accessible sheet library; its sheet editor supports live updates, search, filters and editing according to the account's permissions. Text-only clients receive structured results and a Leadbase link instead. Do not claim a UI rendered merely because a tool returned successfully.\n"
}

SHA-256 of public snapshot: 22ec749004b372d9ce103753b765c0e12bf9ea2453647d62f836ecb93c91bb99