> ## Documentation Index > Fetch the complete documentation index at: https://docs.levios.app/llms.txt > Use this file to discover all available pages before exploring further. # Find strategic contacts > Find existing contacts by follower count and context without hiding missing data or partial coverage. ## Use this agent skill Copy the instructions below into a `SKILL.md` file in a folder named `levios-strategic-contacts` and add it through your client’s supported skill mechanism. If it does not load skill files, provide this content to the agent as task instructions. This does not install anything or enable tools on its own. The skill uses English for one shared instruction set and asks the agent to answer in your language. ```markdown theme={null} --- name: levios-strategic-contacts description: Find and assess strategic contacts already stored in levios, including people above 10k followers or a named Instagram contact. Use for account-scoped shortlists, follower thresholds, incomplete enrichment and authorized tagging. This is contact analysis, not Instagram-wide search or outbound messaging. --- # Find strategic contacts Answer in the user's language. Read `get_automation_guide` topic `contacts`. Resolve the account and the actual available `contacts:read_pii` permission. Do not run the automation-creation questionnaire for a contact lookup. ## Build an honest shortlist 1. Clarify the requested segment or purpose only if unclear. For a named person, use `list_contacts` with its exact `instagram_username` filter. 2. For a segment, paginate `list_contacts` using the returned cursor unchanged and a valid limit up to 50. There is no follower-range, tag or sort filter: apply the requested condition locally to returned records. "Above 10k" means `followers_count > 10000`; "at least 10k" means `>= 10000`. 3. Treat `followers_count=null` as unknown, not zero. Include enrichment state and `last_enriched_at`; reading a record does not refresh Instagram data. 4. Report the account, records examined, matches, unknown/stale data and whether a cursor remains. Claim complete coverage only after exhausting all pages. For a large scan, agree a practical batch budget and retain the remaining cursor; make partial coverage visible. Changing data is not a snapshot. 5. Show username, count, data freshness, relevant tags and profile link. Explain audience fit only from available biography/context as an inference. Follower count is a reach signal, not proof of engagement, fit or purchase intent. Do not expose unrelated email or phone fields. 6. Use `get_contact` only for selected people needing more detail. Timeline events are not guaranteed full conversation transcripts. ## Organize only when requested Use existing tag tools with real account-scoped IDs for authorized selections. A tag does not create a trigger or send campaign. `send_instagram_dm_url` opens Instagram; it is not an MCP send tool or proof of an open messaging window. Contact presence is not consent. Respect opt-out/blocked state and do not send messages just because analysis was requested. For a missing choice, use a native selector only if exposed and usable, following the pending-question lifecycle in topic `start`; otherwise ask concisely in chat. Do not invent followers-minimum trigger filters from this analysis capability. [Thresholds, coverage and result guidance](https://docs.levios.app/mcp/strategic-contacts). ``` ## Reference and examples You can ask: “Show me contacts with more than 10,000 followers who might be relevant partners.” The agent analyzes people already recorded in the selected levios account. This is not a search of everyone on Instagram or an export of the account's entire follower list. ## Define the shortlist Choose the account, threshold, and reason for the search. Follower count can help prioritize reach, but it does not prove engagement, audience fit, or buying intent. Use available biography and interaction context to explain why a candidate might fit, and identify that judgment as an inference. `list_contacts` requires `contacts:read_pii`. It supports an exact `instagram_username` filter. It does not accept a minimum-followers parameter, a tag filter, or a sort order. The agent paginates and filters returned records. ## Handle thresholds and missing information For “above 10k,” use `followers_count > 10000`. For “at least 10k,” use `followers_count >= 10000`. A `null` value is unknown, not zero. Check `enrichment_status` and `last_enriched_at`. Separate stale, failed, pending, and missing data from usable counts. Reading a contact does not force a profile refresh, and stored follower counts are not a live measurement. ## Be explicit about coverage Pass each returned `next_cursor` unchanged into the next `cursor`. A page can contain up to 50 records. Do not conclude that there are no matches after checking only the first page. For a large list, agree on a manageable batch and retain the remaining cursor. Report records examined, matches, unknown counts, stale records, and whether more pages remain. Only claim an exhausted scan when the cursor ends. Even a complete scan over changing data is not a frozen snapshot. A useful result says: “I examined 200 contacts; 12 have a recorded count above 10,000, 30 have unknown counts, and more pages remain.” These numbers are an illustration, not account data. ## Review and organize the results Show the username, recorded follower count, freshness, relevant context, and `instagram_profile_url`. Do not include unrelated email or phone details. Use `get_contact` for selected candidates needing tags, attributes, or activity. Its timeline is not a guaranteed full conversation transcript. If you ask to organize the list, the agent can use `list_contact_tags`, `create_contact_tag`, and `attach_contact_tag` with `contacts:write`. A tag organizes the contact; it does not launch a campaign. `send_instagram_dm_url` opens Instagram. It is not an MCP message-sending tool or evidence that a messaging window is open. An analysis request does not instruct the agent to contact anyone. Respect `opt_out` and `blocked` when recommending outreach. When available, `get_automation_guide` topic `contacts` gives the agent these steps. See [Instagram limits](/mcp/instagram-limits) for messaging boundaries. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.