Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Ringee
Drives the Ringee outbound sales flow step-by-step: prospect search, lead reveal, contact creation, call session, outcome logging, and follow-up. Activates when the user states a goal like "book demos with fintech founders in NYC."
How this skill is triggered — by the user, by Claude, or both
Slash command
/ringee:ringee-flowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Drive the outbound flow toward the user's goal using the connected Ringee MCP.
Drive the outbound flow toward the user's goal using the connected Ringee MCP. Advance ONE step at a time and confirm every sensitive/destructive step.
search_leads (candidates, not contacts; keep the jobId).reveal_lead or
import_leads_as_contacts.create_contact / update_contact.create_call_session; share the joinUrl exactly.callId.log_call_outcome.create_callback or schedule_meeting.After each step, summarize the result and state the next recommended step. Stop
and ask whenever required info is missing or a sensitive/destructive action needs
confirmation. For depth on a step, see ringee-prospect, ringee-contacts,
ringee-session, ringee-followup. (Claude Code: the ringee CLI mirrors each step.)
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.