From Ringee
Logs call outcomes and schedules follow-up callbacks or meetings in Ringee via its MCP tools. Use after a call to record results and book next touch.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ringee:ringee-followupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Record results and schedule the next touch through the connected Ringee MCP.
Record results and schedule the next touch through the connected Ringee MCP.
log_call_outcome needs a real callId. Outcomes:
meeting_booked, sale, interested, follow_up, callback_scheduled, not_interested,
no_answer, voicemail, wrong_number, gatekeeper. Add an outcomeNote if useful.create_callback with contactId
and a future ISO-8601 datetime with offset (e.g. 2026-06-02T15:00:00-04:00).schedule_meeting with contactId + datetime; optional title,
duration (default 30), location, attendeeEmail (sends an invite when a
calendar is connected), callId (sets that call's outcome to meeting_booked).Datetimes are absolute and must include a timezone offset. Resolve any
contactId/callId from prior tool output — never invent ids. Claude Code CLI
fallback: ringee outcomes log · ringee callbacks create · ringee meetings schedule.
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.