{"id":103308,"plugin_id":"plugin_asdk_app_6aecf5792cf48191b788d39e9924766e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-18T06:19:17.675Z","digest":"8dbca2581d1e3f2a9ce7baacdf7f43848c4b3327a6c40dadef179a86d7d377af","against":null,"payload":{"description":"Prepare reviewed Follow Up Boss changes to contacts, notes, tasks, appointments, deals, assignment, call logs, saved email drafts or action-plan pauses, and verify the confirmed outcome.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":116}],"name":"fub-crm-updates","skill_md_contents":"---\nname: fub-crm-updates\ndescription: Prepare reviewed Follow Up Boss changes to contacts, notes, tasks, appointments, deals, assignment, call logs, saved email drafts or action-plan pauses, and verify the confirmed outcome.\n---\n\n# FUB CRM updates\n\nUse the user's requested scope and the live FUB tool definitions. Resolve exact records and account vocabulary first. See [tool contracts](../fub-mcp-tools/references/tool-index.md) for required fields and limits. Never infer a successful write from a prepared review.\n\n## Choose the review workflow\n\n| Requested change | Preparation | Widget-controlled apply |\n| --- | --- | --- |\n| Add one contact | `create_contact` with exactly one row | `apply_create_contact` |\n| Note, stage, profile/contact detail, relationship or new follow-up task | `interaction_update` | `apply_interaction_update` |\n| Meeting summary for one identified person | `draft_meeting_note`, then its official interaction review | `apply_interaction_update` |\n| Complete, reopen or reschedule an existing task | `get_tasks` → `render_task_review` for exactly one ID | `apply_task_update` |\n| Create, edit, cancel or record an appointment outcome | `appointment_update` | `apply_appointment_update` |\n| Create or update one deal | `render_deal_review` | `apply_deal_update` |\n| Owner, co-agent, lender or pond change for one contact | `render_assignment_review` | `apply_contact_assignment` |\n| Log a call already made | `log_call` | `apply_log_call` |\n| Pause one action-plan enrollment | `pause_action_plan` | `apply_pause_action_plan` |\n| Save an email draft | `send_message` | `apply_save_email_draft` |\n| Delete one note, task or deal | `review_delete_record` | `apply_delete_record` |\n\nApply tools are documented for understanding receipts and host integrations. They are app-only: let the rendered widget collect explicit confirmation and submit the frozen proposal. Do not manually obtain tokens, call apply from chat, or set a confirmation boolean on the user's behalf. If the host cannot render or operate the review, explain the blocker and provide the supported FUB handoff.\n\n## Prepare concrete changes\n\n- Select exact IDs from authorized reads. Use `get_account_schema` or relevant metadata readers for account-specific stages, pipelines, users, timeframes and targets. An unreturned field is not evidence it is blank.\n- Contact creation uses one row and stable `rowId`. Exact email/phone duplicates reconcile to existing records; near-name matches need the supported resolution. Do not silently merge or force duplicates.\n- New tasks belong in `interaction_update` with a unique `taskRequestId`, due date/time, and timezone as needed. Existing tasks belong in `render_task_review` with a unique `requestId` and exactly one `taskId` in `taskIds`. Do not replace a task to simulate an update.\n- Deal and assignment reviews also use a unique request ID for the intent. Carry explicit pipeline, stage, owner and target IDs. A projected close date needs a timestamp with an explicit offset resolved in the user's timezone.\n- Contact assignment supports owner, coagent_add, coagent_remove, lender and pond. It does not reassign existing tasks. Preserve collaborator lists through the official proposal; do not simulate routing as a relationship edit.\n- Appointment timestamps require explicit offsets. Resolve ambiguity in contact or appointment selection before another preparation call. Appointment changes do not send invitations; the user sends them from FUB.\n- Call logs describe a call that already happened; they never dial. A refused incoming missed-call outcome must not be rewritten into a different outcome merely to pass validation.\n\n## Confirm and verify\n\nShow the actual rendered target, old/new values and side effects. Let the user confirm each review; one confirmation applies to one contact, task, deal, delete or enrollment where that workflow requires it. User approval of a larger goal does not turn one signed proposal into approval for extra records.\n\nKeep proposal IDs and private confirmation/status tokens in the host's supported flow, never in chat or artifacts. Cancelled or stale reviews must not be applied. Reopen only through the documented mechanism; if a review expired, inspect any prior uncertain outcome before preparing another.\n\nAfter confirmation distinguish verified, failed, partial and uncertain receipts. Read back the exact record when needed. A timeout or lost response is not proof nothing changed: inspect FUB, and do not replay, submit concurrent confirmations, switch write tools, or issue a new request ID to retry an uncertain mutation. Some workflows deduplicate, but there is no blanket exactly-once guarantee.\n\n## Supported boundaries\n\n- A lead source cannot be changed after creation through this API. Do not route that request through another update field.\n- `render_action_plan_start` prepares a FUB handoff; it does not enroll or resume plans. `pause_action_plan` only pauses one confirmed enrollment and may separately report the reason-note outcome.\n- `review_delete_record` hands contact deletion to FUB. Notes/tasks delete permanently; deals become Deleted. Do not describe these as equivalent or infer permission for bulk deletion.\n- `send_message` never sends. Saving an email draft is a separate confirmed write; SMS has no saved draft through this workflow.\n\nUse [feedback guidance](../fub-mcp-tools/references/troubleshooting.md) for a task gap that diagnostics did not already identify. Report only what the receipt and subsequent reads establish.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}