From Ringee
Prospects leads in Ringee via Apollo/Prospeo: search candidates, reveal emails/phones, and import as contacts. Enforces credit confirmation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ringee:ringee-prospectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn external prospects into callable Ringee contacts via the connected Ringee
Turn external prospects into callable Ringee contacts via the connected Ringee MCP. Three tools, in order.
search_leads (read)Find candidates via the user's connected provider (Apollo preferred, else
Prospeo). Build filters from what the user said: jobTitles, seniorities,
departments, industries, personCountries, companyDomains, companyNames,
employeeCountRanges, keywords, hasEmail, hasPhone, emailVerified.
jobId and a page of candidates, each with an externalId.emailsAvailable/phonesAvailable only say whether data exists).jobId.reveal_lead (SENSITIVE — spends credits)Unlock email (and optionally phone via revealPhone: true) for one chosen
candidate; also upserts a Ringee contact so it's callable.
revealPhone costs
extra. Reveal only the candidate(s) the user picked.jobId + the candidate's externalId. Returns the new contactId.import_leads_as_contacts (write)Bulk-create contacts from selected candidates (does NOT unlock hidden email/phone
— use reveal_lead first if you need contact info). Skips phone duplicates. For a
large import, confirm the count first. Needs jobId + externalIds.
Never invent jobId/externalId. After converting, continue with a call session
(ringee-session). (Claude Code CLI fallback: ringee leads search|reveal|import.)
npx claudepluginhub ringee-io/ringee-app --plugin ringeeGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.