Update to Yadulink

{
  "description": "Preview a LinkedIn prospect search in Yadulink, then import a clean list only after the user confirms. Use for ICP searches, shortlists, and list creation.",
  "included_files": [],
  "name": "find-prospects",
  "skill_md_contents": "---\nname: find-prospects\ndescription: Preview a LinkedIn prospect search in Yadulink, then import a clean list only after the user confirms. Use for ICP searches, shortlists, and list creation.\n---\n\n# Find prospects\n\nTurn an ICP description into a previewed Yadulink search. Import only after the user confirms the plan.\n\n## When to use\n\nThe user wants to find people, build a list, import prospects, or search by role, industry, or location.\n\n## Workflow\n\n1. Clarify audience, geography, language, and exclusions if they are missing.\n2. Call `preview_outreach_search` first. Never skip preview.\n3. Summarize the resolved filters, estimated volume, risks, and exact `credits.total_cost` quote.\n4. Ask the user to approve that exact import cost.\n5. After confirmation, call `execute_outreach_search` once with the returned `execution_requirements.max_credits` and a new idempotency key. The tool itself creates the named list.\n6. Offer `clean_and_score_contact_list` if the imported list looks noisy.\n\n## Rules\n\n- Prefer fewer relevant profiles over a large weak list.\n- Do not launch a sequence from this skill unless the user explicitly asks after seeing the list.\n- Never reuse an idempotency key after changing the query, count, or list name.\n- Keep Yadulink safety limits visible: this is controlled outreach, not unlimited sending.\n- If the user mentions another workspace account, pass `target_account` only when they named it.\n\n## Output\n\nShow:\n\n- the search plan in plain language\n- who would be included and excluded\n- the confirmation needed before import\n- the list name to use if import proceeds\n"
}