merge-unified

Plugin merge-unified from marketplace merge-unified-skills in merge-api/merge-unified-skills. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• implementing-link

  Guide an AI coding agent through the full Merge Link implementation flow — context loading, database setup, backend API endpoints, and frontend UI. Use when starting a Merge integration, implementing Merge Link in a new project, setting up linked_accounts, or building the connect button or app marke

• implementing-post-connection

  Guide an AI coding agent through the full post-connection experience — settings page, sync status visibility, relinking, integration configuration, custom fields, and category-specific data scope filtering. Use after completing Merge Link setup to build the ongoing integration management experience

• implementing-sync

  Guide an AI coding agent through implementing Merge sync triggers — initial sync detection and subsequent incremental sync. Webhooks are the recommended primary approach; polling acts as a development starting point and a production fallback. Use after completing Merge Link setup when you need to fe

• integration-validator

  Validate a Merge Unified API integration end-to-end. Use when a developer says "validate my Merge integration", "test my Merge setup", "is my Merge connection working", "debug my Merge API call", "verify my Linked Account", "check my Merge scopes", "my Merge API returns empty", "Merge sync not worki

• link-implement-backend

  Implement the four Merge Link backend API endpoints: link token creation, public token exchange, relinking, and deletion. Use as Step 3 of Merge Link implementation.

• link-implement-frontend-connect

  Add a single "Connect" button that opens the Merge Link modal. Use as Step 4a of Merge Link implementation after backend endpoints are complete.

• link-implement-frontend-marketplace

  Implement the App Center/Marketplace UI pattern for Merge Link — a browsable integration catalog where users select and connect specific integrations. Use as Step 4b of Merge Link implementation when users should discover and connect multiple integrations.

• link-setup-database

  Create the linked_accounts database table required for Merge Link. Use as Step 2 of Merge Link implementation after loading context.

• onboarding

  Step-by-step onboarding for the Merge Unified API. Use when a developer says "set up Merge", "integrate Merge", "Merge Unified API", "create a Linked Account", "Merge Link", "generate a link token", "exchange account token", "pull HRIS data", "sync employee data", "sync candidate data", "sync CRM co

• post-connection-build-settings-page

  Build the dedicated integration settings page that lets end users manage their connected integrations — view connection health, reconnect/relink, configure per-integration settings (sync scope, field mappings, data filters, writeback behavior), and track setup completeness. Use as Step 2 of post-con

• post-connection-data-scope-filtering

  Establish a data-scope filtering strategy (pre-storage or post-storage) before syncing data from Merge. Customers rarely want every record their connected system has — they want a scoped subset (active employees in HRIS, candidates in a specific stage in ATS, accounts of a certain type in CRM, ticke

• post-connection-enable-custom-fields

  Build a settings UI that lets customers select and enable custom fields from their connected system using Merge's Field Mapping API. Use as Step 5 of post-connection implementation when customers need access to fields beyond Merge's common models.

• post-connection-implement-relinking

  Implement relinking as a first-class in-product flow and surface detailed, actionable error messages that clarify who must act and how. Use as Step 4 of post-connection implementation to eliminate integration support tickets.

• post-connection-surface-sync-status

  Implement sync status visibility and user-facing messaging for the initial sync timeline. Use as Step 3 of post-connection implementation to prevent user confusion while Merge syncs data in the background.

• sync-implement-polling

  Implement Merge sync detection via a scheduled polling job. Use this as a development starting point (no public webhook endpoint required) and as a production fallback alongside `sync-implement-webhooks` to catch missed or delayed webhook deliveries. A single job covers both initial sync detection (

• sync-implement-webhooks

  Implement Merge sync detection via webhooks — the PRIMARY production-recommended approach. A single endpoint handles both initial sync detection (first connection) and subsequent incremental syncs (ongoing data updates), with HMAC verification and a bounded `modified_after` / `modified_before` fetch