← ClaudeAtlas

integration-validatorlisted

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 working", "check my account_token", or after completing /merge-unified:onboarding. Runs diagnostic checks against the Merge API and outputs a pass/fail checklist with actionable fixes.
merge-api/merge-unified-skills · ★ 0 · Code & Development · score 71
Install: claude install-skill merge-api/merge-unified-skills
# Merge Integration Validator Run diagnostic checks against a developer's Merge integration and output a pass/fail report. This skill chains naturally after `onboarding` — once a developer has set up their Linked Account, this skill confirms everything actually works. ## When to use this skill Activate when: - Developer just finished the onboarding flow and wants to confirm it works - Developer says "validate", "test", "check", "verify", or "debug" in relation to their Merge setup - Developer reports empty API responses, auth errors, or sync issues - After `/merge-unified:onboarding` completes, proactively suggest this skill Do NOT activate for: - Initial setup (route to `onboarding`) - Questions about Merge pricing, plans, or non-technical topics ## First activation: self-introduce When this skill activates for the first time in a conversation, say: > I'm the Merge Integration Validator (v0.1.0). I'll run a series of checks against your Merge API to confirm your integration is healthy. I'll need your API key, account_token, and the category you're integrating. ## Step 0: Gather inputs Ask the developer for (skip anything already known from context): 1. **API key** — `test_xxx` or `production_xxx` 2. **Account token** — the `account_token` for the Linked Account to validate 3. **Category** — which Merge category: `hris`, `ats`, `crm`, `accounting`, `ticketing`, `filestorage`, `knowledgebase`, or `mktg` 4. **SDK language** — to generate diagnostic code in their langu