← Sales MarkerCONTENT HISTORY

Update to Sales Marker

Snapshot Nov 16, 2026 · 06:09 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Sales Marker 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": "Use when the user wants to find Japanese companies that are actively researching a product category, learn why a company is a fit, build and maintain prospect lists, or send approaches by email, web form or phone through Sales Marker.",
  "included_files": [],
  "name": "intent-sales",
  "skill_md_contents": "---\nname: intent-sales\ndescription: Use when the user wants to find Japanese companies that are actively researching a product category, learn why a company is a fit, build and maintain prospect lists, or send approaches by email, web form or phone through Sales Marker.\n---\n\n# Intent sales with Sales Marker\n\nSales Marker detects which Japanese companies are researching a topic right now\n(\"intent\"), and turns that into outreach. The tools cover four stages: find,\nresearch, organise, approach.\n\nEvery tool acts inside the signed-in user's own subscription. Company and\ncontact data is real personal and corporate data about third parties — treat it\naccordingly and never paste it somewhere the user did not ask for.\n\n## Start here\n\nCall `get_current_user` first when you need the user's own subscription, name or\nproduct context. Call `get_products` to see what the user actually sells; most\nintent questions only make sense relative to a product.\n\n## Find companies\n\n- `search_company_v2` is the main entry point. It filters by intent signals,\n  industry, location, company size and more. Ask the user which product they are\n  selling before guessing filters.\n- `get_industries`, `get_prefecture_list` and `get_company_labels` return the\n  valid values for those filters. Use them instead of inventing codes.\n- `search_person_v2` and `search_department_v2` find people and departments at\n  those companies.\n- `get_intent_detection_results` and `get_intent_stats_for_graph` explain *why* a\n  company surfaced — which keywords it researched and when.\n\n## Research a company\n\n- `get_company_approach_results` and `get_product_approach_results` show what has\n  already been tried, so the user does not approach the same company twice.\n- `search_meetings`, `get_meeting_details`, `get_note` and `get_properties` pull\n  meeting history and AI notes. `get_note` and `get_properties` need both\n  `objectID` and `interactionType` (for an online meeting, use\n  `INTERACTION_TYPE_ONLINE_MEETING`).\n- `get_meeting_details` takes `id`, not `meetingId`.\n\n## Organise into lists\n\n- `list_company_lists` / `get_company_list` to read, `create_company_list` and\n  `add_companies_to_company_list` to build. Adding is idempotent, so re-sending\n  the same ids is safe.\n- The same pattern exists for people: `list_person_lists`, `create_person_list`,\n  `add_persons_to_person_list`.\n- `update_company_list`, `remove_companies_from_company_list` and\n  `delete_company_list` change or destroy existing data. Confirm with the user\n  before calling them, and never call `delete_company_list` speculatively — it is\n  irreversible.\n\n## Approach\n\nThese tools contact real people and companies. Call them **only** when the user\nhas explicitly asked to send, and show the user exactly what will go out first.\n\n- `send_emails` sends intent emails to a company list or person list. Requires\n  `senderEmail`, `title` and `content`, and exactly one recipient source.\n- `send_forms` fills and submits companies' own website contact forms.\n- `create_phone_calls` records calls that already happened; it does not dial.\n- Sequences (`create_sequence`, `start_sequence`, `pause_sequence`,\n  `update_sequence`, `delete_sequence`) automate multi-step outreach.\n  `start_sequence` begins approaching real companies — treat it like a send.\n\n## Working well here\n\n- Resolve filter values with the lookup tools before searching; guessed ids\n  return empty results that look like \"no companies match\".\n- Prefer narrowing an existing search over running many broad ones — searches\n  consume the subscription's credit.\n- When a user asks \"who should I contact at X\", combine `search_person_v2` with\n  the company's intent evidence rather than listing every employee.\n- Summarise outreach results (`totalCount`, `skippedCount`) back to the user\n  rather than restating the whole payload.\n"
}

SHA-256 of public snapshot: efbda0b563f9aee0bf15e8a9fa2d095e98c8d1fc28459d74eb112b3446733e1f