docs(plugin): align marketplace package with hosted MCP surface

Tighten the public plugin metadata, submission copy, rules, and skills so the package reads professionally and only promises the current hosted LeadMagic MCP capabilities.

Made-with: Cursor

Author: jesseoue

.cursor-plugin/plugin.json

@@ -2,9 +2,10 @@
 	"name": "leadmagic",
 	"displayName": "LeadMagic",
 	"version": "0.1.0",
-	"description": "Official LeadMagic plugin for Cursor with hosted MCP-powered B2B enrichment, contact discovery, company intelligence, and GTM signal research.",
+	"description": "Official LeadMagic plugin for Cursor with hosted MCP-powered work email validation, email finding, account research, and credit-aware enrichment.",
 	"author": {
-		"name": "LeadMagic"
+		"name": "LeadMagic",
+		"email": "plugins@leadmagic.io"
 	},
 	"homepage": "https://leadmagic.io",
 	"repository": "https://github.com/LeadMagic/leadmagic-cursor-plugin",

CHANGELOG.md

@@ -15,3 +15,6 @@ All notable changes to the LeadMagic Cursor plugin will be documented in this fi
 - Tightened skills and default guidance around company research, job-change checks, hiring signals, and credit-aware workflows
 - Added GitHub pull request and validation scaffolding so the plugin repo matches the OpenAPI repo's baseline maintenance hygiene
 - Expanded README and submission docs with clearer install, validation, troubleshooting, and marketplace submission steps
+- Tightened plugin metadata and marketplace submission copy around the current hosted MCP surface: work email validation, work email finding, account research, and credit-aware enrichment
+- Added the shared plugin contact email to `plugin.json` and `SUBMISSION.md` for a cleaner publisher-facing package
+- Corrected rules and skill guidance so they reference only the currently supported hosted MCP tools instead of older or broader API-only tool names

README.md

@@ -10,10 +10,10 @@ The package includes:
 
 - Hosted LeadMagic MCP connectivity for Cursor
 - The current LeadMagic MCP surface:
-  - 4 tools for credits, work email validation, email finding, and account research
+  - 4 tools for credit checks, work email validation, work email finding, and account research
   - 1 shared docs resource: `leadmagic://docs`
   - 2 built-in prompts: `account_research` and `contact_lookup`
-- Four focused Cursor skills:
+- Four focused Cursor skills aligned to the current hosted MCP surface:
   - contact enrichment
   - account intelligence
   - prospect list QA
@@ -47,7 +47,7 @@ The current hosted MCP surface is strongest for:
 - finding likely work emails with `find_work_email`
 - researching companies with `research_account`
 
-The broader REST API and OpenAPI snapshot include additional surfaces, but this plugin is documented against the current MCP surface only. That keeps the marketplace listing accurate and avoids implying support for endpoints that are not currently exposed through MCP.
+The broader REST API and OpenAPI snapshot include additional surfaces, but this plugin is documented against the current hosted MCP surface only. That keeps the marketplace listing accurate and avoids implying support for endpoints that are not currently exposed through MCP.
 
 ## Quick Start
 

SUBMISSION.md

@@ -14,13 +14,13 @@ leadmagic
 @leadmagic
 
 **Contact email**
-Use a shared public LeadMagic alias for marketplace contact. Avoid individual employee inboxes.
+plugins@leadmagic.io
 
 **Logotype URL**
 https://raw.githubusercontent.com/LeadMagic/leadmagic-cursor-plugin/main/assets/logo.svg
 
 **Description**
-Official LeadMagic plugin for Cursor. Gives agents direct access to LeadMagic's hosted MCP surface for email validation, email finding, profile enrichment, company intelligence, technographics, competitor research, job-change detection, and hiring-signal workflows.
+Official LeadMagic plugin for Cursor. Gives agents direct access to LeadMagic's hosted MCP surface for work email validation, email finding, account research, and credit-aware enrichment workflows.
 
 **GitHub repository**
 https://github.com/LeadMagic/leadmagic-cursor-plugin
@@ -42,15 +42,15 @@ Before submitting:
 
 ## Suggested reviewer note
 
-LeadMagic is an API-first B2B enrichment platform for AI agents and GTM engineers. This plugin packages our current hosted MCP integration into a Cursor-native repo with focused skills, safe default guidance, and a clean environment-variable setup for credit-aware enrichment workflows.
+LeadMagic is an API-first B2B enrichment platform for AI agents and GTM engineers. This plugin packages our current hosted MCP integration into a Cursor-native repo with focused skills, safe default guidance, and a clean environment-variable setup for credit-aware work email validation, email finding, and account research workflows.
 
 ## Short marketplace blurb alternatives
 
 ### Option A
-Official LeadMagic plugin for Cursor. Enrich people and companies, validate emails, find contact paths, and surface GTM signals directly inside Cursor.
+Official LeadMagic plugin for Cursor. Validate work emails, find likely work emails, and research target accounts directly inside Cursor.
 
 ### Option B
-B2B enrichment for Cursor agents: email validation, email finding, profile enrichment, company intelligence, technographics, job-change detection, and buying-signal research through LeadMagic.
+B2B enrichment for Cursor agents: work email validation, email finding, account research, and credit-aware workflows through LeadMagic.
 
 ### Option C
-Connect Cursor to LeadMagic for agent-native prospecting and account research with verified contact data, company intelligence, and workflow-ready enrichment tools.
+Connect Cursor to LeadMagic for agent-native work email lookup and account research with verified contact data and workflow-ready enrichment tools.

rules/leadmagic-usage.mdc

@@ -1,26 +1,26 @@
 ---
-description: Use LeadMagic before fragile web scraping whenever the task involves B2B people, company, job, or ad enrichment. Optimize for credit efficiency and clearly summarize what was found.
+description: Use LeadMagic before fragile web scraping whenever the task involves work email validation, work email discovery, or account research. Optimize for credit efficiency and clearly summarize what was found.
 alwaysApply: true
 ---
 # LeadMagic usage guidance
 
 When this plugin is available:
 
-1. Prefer LeadMagic tools for B2B enrichment and validation tasks before suggesting manual research.
+1. Prefer LeadMagic tools for work email validation, work email discovery, and account research before suggesting manual research.
 2. Minimize unnecessary credit spend:
-   - For bulk or credit-sensitive work, check balance first with `check_credits`.
-   - If the user already has an email, validate it before trying to find another one.
-   - If the user already has a profile URL, use profile-based tools before broader searches.
-   - If a company domain or professional social profile URL is known, use those as primary identifiers.
+   - For bulk or credit-sensitive work, check balance first with `check_credit_balance`.
+   - If the user already has an email, validate it with `validate_work_email` before trying to find another one.
+   - If the user wants a work email and only has a person plus company context, use `find_work_email`.
+   - If the user wants company context, run `research_account` once and reuse the results instead of repeating similar lookups.
 3. Chain tools deliberately:
-   - Person workflow: `validate_email` -> `email_to_b2b_profile` / `search_profile` -> `social_to_email` / `find_personal_email` / `find_mobile`.
-   - Company workflow: `search_company` -> `get_company_funding` / `get_technographics` / `find_competitors`.
-   - Signal workflow: `detect_job_change` for contact movement and `find_jobs` after company identity is confirmed.
+   - Person workflow: `check_credit_balance` -> `validate_work_email` -> `find_work_email` if validation fails or no email is available.
+   - Company workflow: `check_credit_balance` -> `research_account`.
+   - Mixed workflow: validate the known email first, then use `research_account` only if the user also needs account context.
 4. Do not repeat the same lookup unless the user asks for a retry or changes the inputs.
 5. In the final answer, state:
    - which LeadMagic tools were used,
    - the key results,
    - any important null, not-found, or unknown outcomes,
    - and any obvious next best step.
-6. If parameter requirements or pricing are unclear, consult the shared MCP docs resource `leadmagic://docs` before guessing.
+6. If parameter requirements, supported inputs, or pricing are unclear, consult the shared MCP docs resource `leadmagic://docs` before guessing.
 7. If the API key is missing or authentication fails, tell the user they need to set `LEADMAGIC_API_KEY`.

skills/account-intelligence/SKILL.md

@@ -1,32 +1,27 @@
 ---
 name: account-intelligence
-description: Enrich a company with LeadMagic company intelligence, then expand into funding, competitors, technographics, employees, and roles. Use for account research and ICP qualification.
+description: Research a target company with the current hosted LeadMagic MCP surface. Use for account research, ICP qualification, and quick account briefs.
 ---
 # Account intelligence
 
 ## Trigger
-Use when the user wants company research, ICP fit, funding context, hiring signals, or a target account brief.
+Use when the user wants company research, ICP fit, or a target account brief from LeadMagic's hosted MCP tools.
 
 ## Workflow
 1. Resolve the company first with the cleanest identifier available:
-   - domain preferred,
-   - company name,
-   - or company profile URL.
-2. Run the core company lookup to establish the canonical company record.
-3. Expand only into the modules relevant to the user:
-   - `get_company_funding` and `find_competitors` for strategic research,
-   - `get_technographics` for stack-based targeting,
-   - `find_employees` and `find_role` for buying committee discovery.
-4. Keep the work scoped to the current MCP surface. If the user asks for ad intelligence or other API-only surfaces, be explicit that those may exist in the broader API docs but are not part of the current LeadMagic MCP tool set.
-5. Keep the summary operator-friendly:
+   - company domain preferred,
+   - otherwise company name.
+2. Run `research_account` to establish the canonical account record.
+3. Keep the work scoped to the current MCP surface. If the user asks for technographics, competitors, ad intelligence, or other API-only surfaces, be explicit that those may exist in the broader API/docs surface but are not part of the current hosted MCP tool set.
+4. Keep the summary operator-friendly:
    - what the company is,
    - why it matters,
-   - who to target next,
-   - and what signal makes the account timely.
+   - what LeadMagic could confirm,
+   - and what should be researched next outside the current MCP scope.
 
 ## Output
 Return a short account brief with:
 - company basics,
-- buying signals,
-- target personas or departments,
+- the most relevant GTM context available from `research_account`,
+- any important unknowns,
 - and the recommended next LeadMagic lookup if needed.

skills/contact-enrichment/SKILL.md

@@ -1,33 +1,30 @@
 ---
 name: contact-enrichment
-description: Find and verify the best contact path for a B2B prospect using the lowest-cost LeadMagic workflow. Use when the user has a person plus company, profile URL, or existing email and wants validated outreach data.
+description: Find or verify the best work email for a B2B prospect using the current hosted LeadMagic MCP surface. Use when the user has a person plus company or an existing email and wants validated outreach data.
 ---
 # Contact enrichment
 
 ## Trigger
-Use when the user needs a work email, personal email, mobile number, validation result, or profile enrichment for a specific person.
+Use when the user needs a validated work email or wants LeadMagic to find the likely work email for a specific person.
 
 ## Workflow
 1. Start from the strongest identifier the user already has.
-   - Existing email: validate it first.
-   - Profile URL: use profile-based lookups first.
-   - Full name + company: use email finder or role/profile searches.
+   - Existing work email: validate it first with `validate_work_email`.
+   - Full name + company or domain: use `find_work_email`.
 2. Prefer the cheapest path that can answer the question.
-3. Chain tools only when it improves confidence or unlocks the next field.
+3. If the user already has an email, do not jump straight to finding another one.
 4. Avoid duplicate requests for the same person and company combination.
 5. Report both the result and what was not found.
 
 ## Recommended tool chains
-- Existing email -> `validate_email`
-- Existing email + wants profile -> `email_to_b2b_profile` -> `search_profile`
-- Profile URL + wants work email -> `social_to_email`
-- Profile URL + wants mobile -> `find_mobile`
-- Name + company + wants work email -> `find_email`
-- Profile URL + wants personal email -> `find_personal_email`
+- Existing email -> `validate_work_email`
+- Existing email fails validation or no email exists -> `find_work_email`
+- Name + company + wants work email -> `find_work_email`
+- Person + company + wants confidence before spending more credits -> `check_credit_balance` -> `find_work_email`
 
 ## Output
 Return:
 - best contact field found,
 - validation status when available,
-- supporting profile or company context,
+- the exact input used,
 - and a concise next action.

skills/prospect-list-qc/SKILL.md

@@ -1,35 +1,31 @@
 ---
 name: prospect-list-qc
-description: Clean and enrich prospect lists with a credit-aware workflow using LeadMagic. Use when the user is preparing outbound lists, CRM imports, or enrichment jobs and wants the best sequence of validation and enrichment.
+description: Clean and enrich prospect lists with a credit-aware workflow using the current LeadMagic MCP tools. Use when the user is preparing outbound lists, CRM imports, or enrichment jobs and wants the best validation-first sequence.
 ---
 # Prospect list QA and enrichment
 
 ## Trigger
-Use when the user has many prospects and wants the highest-confidence sequence for enrichment or data cleanup.
+Use when the user has many prospects and wants the highest-confidence sequence for work email validation, work email discovery, or company research.
 
 ## Workflow
-1. For large or credit-sensitive lists, start with `check_credits` so the user knows the budget envelope.
+1. For large or credit-sensitive lists, start with `check_credit_balance` so the user knows the budget envelope.
 2. Prioritize validation before expensive enrichment whenever emails already exist.
 3. Separate records into buckets:
-   - already have email -> validate,
-   - have profile URL but no email -> profile-based enrichment,
-   - have name + company only -> `find_email`,
-   - company-only records -> `search_company`, `find_employees`, and `find_role`.
+   - already have work email -> `validate_work_email`,
+   - have name + company only -> `find_work_email`,
+   - company-only records -> `research_account`.
 4. Remove duplicates before enrichment.
 5. Preserve null and unknown outcomes instead of forcing guesses.
 6. Recommend the cheapest sensible order of operations before bulk runs.
 
 ## Default order
-1. `validate_email`
-2. `find_email`
-3. `search_profile` or `search_company`
-4. `social_to_email` or `find_personal_email`
-5. `find_mobile`
-6. `find_role` or `find_employees`
-7. `detect_job_change`, `find_jobs`, competitors, funding, or technographics only for priority accounts
+1. `check_credit_balance`
+2. `validate_work_email`
+3. `find_work_email`
+4. `research_account` only for priority accounts that also need account context
 
 ## Output
 Provide:
 - a suggested enrichment pipeline,
 - likely credit-sensitive decision points,
-- and an example record flow from raw input to final output.
+- and an example record flow from raw input to final output using only the currently supported MCP tools.

skills/signal-research/SKILL.md

@@ -1,27 +1,22 @@
 ---
 name: signal-research
-description: Use LeadMagic jobs, competitors, funding, and technographics tools to find buying signals and GTM timing opportunities. Use for account prioritization, market mapping, and outbound angle creation.
+description: Use LeadMagic account research to find the strongest currently supported account context and GTM timing clues. Use for account prioritization, market mapping, and outbound angle creation within the hosted MCP surface.
 ---
 # Signal research
 
 ## Trigger
-Use when the user wants evidence that an account is active, growing, spending, hiring, or entering a new category.
+Use when the user wants evidence that an account is relevant now and needs a concise LeadMagic-backed research summary.
 
 ## Workflow
 1. Confirm the company identity first.
-2. Choose the lightest signal path that fits the question:
-   - hiring motion -> `find_jobs`,
-   - contact movement -> `detect_job_change`,
-   - market landscape -> `find_competitors`,
-   - financial posture -> `get_company_funding`,
-   - stack fit -> `get_technographics`.
-3. Synthesize signals into GTM implications, not just raw data.
-4. Highlight uncertainty when signals are partial.
-5. Stay within the current MCP surface. If the user asks for ad intelligence, call out that it belongs to the wider API/docs surface rather than the current MCP tool set.
+2. Use `research_account` to collect the strongest current account context LeadMagic can provide through MCP.
+3. Synthesize the results into GTM implications, not just raw data.
+4. Highlight uncertainty when signals are partial or the hosted MCP surface does not expose the exact field the user wants.
+5. Stay within the current MCP surface. If the user asks for jobs, competitors, funding, technographics, or ad intelligence, call out that those may belong to the wider API/docs surface rather than the current hosted MCP tool set.
 
 ## Output
 Return:
-- top signals found,
+- top account signals or context found,
 - what they likely mean for GTM timing,
 - a recommended outreach angle or research follow-up,
 - and any missing data the user may still want.