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 finta-pack
Diagnoses and fixes common Finta CRM issues including email sync, deal rooms, CSV imports, and payment collection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/finta-pack:finta-common-errorsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fix**: Go to Settings > Integrations, disconnect and reconnect Gmail/Outlook OAuth.
Fix: Go to Settings > Integrations, disconnect and reconnect Gmail/Outlook OAuth.
Fix: Verify correct calendar is selected. Finta only syncs the primary calendar by default.
Fix: Check if the link expired or access was revoked. Generate a new shareable link.
Fix: Download the Finta CSV template and match column headers exactly. Ensure dates use YYYY-MM-DD format.
Fix: Complete all company profile fields (sector, stage, location, raise amount). Aurora needs sufficient context.
Fix: Check Settings > Automation rules. Verify email sync is active and tracking the correct inbox.
Fix: Verify Stripe integration is connected. Check that the payment link amount matches the commitment.
For diagnostics, see finta-debug-bundle.
npx claudepluginhub ia23a-lachnita/claude-code-plugins-plus-fix-skills --plugin finta-pack2plugins reuse this skill
First indexed Jul 17, 2026
Diagnose and fix common Finta CRM issues with email sync, deal rooms, and pipeline. Trigger with phrases like "finta error", "finta not working", "fix finta".
Guides 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.