Plaid Fintech

← Back to skills

Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices.

Category: AI & Intelligent Agents
Repo: antigravity-awesome-skills
Path: skills/plaid-fintech/SKILL.md
Updated: 10/11/2026, 8:00:18 PM

AI Summary

Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. It is useful for LLM applications, agent orchestration, RAG pipelines, AI evaluation, and multi-agent workflows. Source: antigravity-awesome-skills (skills/plaid-fintech/SKILL.md).

Plaid Fintech

Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

  • User mentions or implies: plaid
  • User mentions or implies: bank account linking
  • User mentions or implies: bank connection
  • User mentions or implies: ach
  • User mentions or implies: account aggregation
  • User mentions or implies: bank transactions
  • User mentions or implies: open banking
  • User mentions or implies: fintech
  • User mentions or implies: identity verification banking

Example

User request:

Use @plaid-fintech for this task: Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Related skills