Update to Pluggzy

{
  "description": "Use when the user wants to find people on LinkedIn, look up or research a LinkedIn profile, compare professional backgrounds, or draft an introduction from profile information. Research does not authorize sending messages or connection requests.",
  "included_files": [],
  "name": "linkedin-research",
  "skill_md_contents": "---\nname: linkedin-research\ndescription: Use when the user wants to find people on LinkedIn, look up or research a LinkedIn profile, compare professional backgrounds, or draft an introduction from profile information. Research does not authorize sending messages or connection requests.\n---\n\n# LinkedIn research\n\nRead [account access and limits](../../references/account-and-limits.md) before using tools.\n\nUse `linkedin_search_people` with `keywords` or a LinkedIn people-search `url` supplied by the user. A search URL preserves its filters. Use `network_distance` when the user specifies connections or degree. Each page costs a search; request at most 25 results per page and follow `next_cursor` only as needed.\n\nSearch and profile lookups use the first LinkedIn account and its network unless `account` names another one. Pass `account` when the user asks about a specific account's network or limits.\n\nUse returned `person_id` values for later calls. Retrieve selected profiles with `linkedin_get_profile`, passing the ID or the public identifier after `linkedin.com/in/` as `person`. A profile lookup counts as a profile view.\n\nWhen names match more than one person, use employer, role, location, and profile URL to resolve identity before preparing outreach. Keep unresolved matches explicit.\n\nSummarize the fields relevant to the user's question. Link returned profile URLs. Distinguish observed information from inferred fit or interests. Missing fields are unknown. Summaries, experience, education, and skills may be truncated, so do not describe them as a complete history.\n\nFor ChatGPT research requests that require the compatibility tools, `search` accepts `query` and returns record IDs such as `person:<id>`. `fetch` accepts `id`. It can retrieve a person record or a conversation identified by `chat:<id>` when that chat ID is already known. `search` searches people and does not search inbox messages. Prefer the specific LinkedIn tools for inbox triage and profile comparisons.\n\nDraft introductions from verified professional context. Research does not authorize invitations or messages. For sending, use [LinkedIn outreach](../linkedin-outreach/SKILL.md).\n"
}