Agent skill · data analytics · aiskillstore
plan-prospecting
Build a sourced retirement-plan prospecting brief with PlanProvider.Pro MCP data. Use when a user wants to research target employers, identify their current retirement-plan providers, or prioritize outreach based on Form 5500-derived plan signals.
Why this skill is useful
Provides domain-specific knowledge on retirement-plan prospecting using Form 5500 data and the PlanProvider.Pro MCP.
What it needs
Requires planprovider.pro account access. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Prospect retirement-plan accounts with PlanProvider.Pro Use the PlanProvider.Pro MCP to enrich a user-supplied target list with Form 5500-derived plan and provider context. The MCP is a research tool: it does not replace a CRM, a current contact database, or legal and fiduciary advice. Connect Add this remote MCP server in the client's MCP connections or integrations settings: https://swhejpcukgzywbwacfdv.supabase.co/functions/v1/mcp Complete the PlanProvider.Pro OAuth flow when prompted. The endpoint is public by design; account tier controls the accessible Form 5500 rows and fields. MCP tools lookupcompanyplan: search indexed Form 5500 plan records by company or sponsor name. searchproviders: find auditors, advisors, administrators, insurers, and ERISA attorneys by name, provider type, or state. getprovider: retrieve a provider profile after a provider slug is known. Recommended workflow 1. Clarify the target market: geography, industry, plan type, approximate participants or assets, and the provider service being sold. 2. Start with the user's target employers or a narrow, named candidate list. The MCP does not provide an unrestricted bulk company export, so do not claim to have searched every employer in a market. 3. Call lookupcompanyplan for each target sponsor name. Try the legal name, operating name, and a likely alternate name when the first lookup is empty. 4. Confirm the match using the returned sponsor, plan name, EIN, plan number, participants, assets, filing year, and canonical PlanProvider.Pro URL. 5. Identify current plan providers from the linked plan record. Use searchproviders or getprovider when the user needs provider context, credentials, geography, or a profile link. 6. Prioritize outreach using explicit, filing-derived signals such as plan size, plan type complexity, recent provider changes shown on the source record, and a provider-service gap. Label every inference as an inference. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/plan-prospecting